You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All (internal) REST APIs, i.e. the DataMgmt API, the DataPlane API, ControlPlane API(?), should implement a consistent (possibly shared) use of tokens with regards to creation, refreshing, revoking.
Each API should have its own Jetty Context, but they should use the same AuthenticationService. Currently there is only the TokenBasedAuthenticationService, which may need to get adapted.
Currently, only the control-API is unsecured, so we need to make sure that users have a way to supply an AuthenticationService for it.
The text was updated successfully, but these errors were encountered:
paullatzelsperger
changed the title
API Security: create pattern for token handling for (internal) REST APIs
API Security: enable authentication for (internal) REST APIs
Aug 2, 2023
All (internal) REST APIs, i.e. the DataMgmt API, the DataPlane API, ControlPlane API(?), should implement a consistent (possibly shared) use of tokens with regards to creation, refreshing, revoking.Each API should have its own Jetty Context, but they should use the sameAuthenticationService
. Currently there is only theTokenBasedAuthenticationService
, which may need to get adapted.Currently, only the
control-API
is unsecured, so we need to make sure that users have a way to supply anAuthenticationService
for it.The text was updated successfully, but these errors were encountered: