Add authentication Types for authenticators. #5901
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Task issue:
With above feature, we will introduce an authentication adapter that extends the
AbstractApplicationAuthenticator
and implements theFederatedApplicationAuthenticator
class. This adapter will support to authenticated both LOCAL and FEDERATED users and user type will be defined at runtime. The authentication flow will need to accommodate both types. To achieve this, the following improvements will introduced with this PR:getAuthenticatorType()
to theApplicationAuthenticator
interface, with SYSTEM as the default return value.getAuthenticatorType()
method to return their CUSTOM type.instanceof FederatedApplicationAuthenticator
check, which ideally should be based on the authenticated user (isFedUser()
) of the corresponding step. Those will be updated.