Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement a ParticipantAuthenticationService #218

Closed
Tracked by #214
paullatzelsperger opened this issue Jan 15, 2024 · 0 comments · Fixed by #238
Closed
Tracked by #214

Implement a ParticipantAuthenticationService #218

paullatzelsperger opened this issue Jan 15, 2024 · 0 comments · Fixed by #238
Labels
api breaking-change Will require manual intervention for version update enhancement New feature or request

Comments

@paullatzelsperger
Copy link
Member

paullatzelsperger commented Jan 15, 2024

implement a new AuthenticationService, that authenticates/authorizes a request depending on a participantId and an apiToken. If the given combination is not found, reject with HTTP 401.

The following headers are to be used:

  • x-api-key -> contains api token
  • x-participant-id -> contains participant ID.

This authentication service is to be registered for all management API, except those that require super-user access.

@paullatzelsperger paullatzelsperger changed the title implement a new AuthenticationService, that secures all management APIs based on a participant's API token Implement a ParticipantAuthenticationService Jan 15, 2024
@paullatzelsperger paullatzelsperger added enhancement New feature or request api breaking-change Will require manual intervention for version update labels Jan 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api breaking-change Will require manual intervention for version update enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant