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
Need to fix followings which related to the authentication execution flow with custom authentication extension:
The current DB queries which retrieve user defiend local authenticators and user defined federated authenticators are not considering IDP type. Fixes user defined authentication retrieval DB queries.
UseflowID as the url param to identity the corresponding authentication flow, instead of sessionDataKey.
When the basic authenticator is engaged in the authentication flow, the handleRequest method for the basic authenticator is automatically triggered at the start, setting setCurrentAuthenticator to the basic authenticator. However, when the user provides a username and password, the handleResponse method is initiated, and at line [1], setCurrentAuthenticator is reset to null. Consequently, when selecting the appropriate authenticator, the system iterates through the list of authenticators in the step and checks if currentAuthenticator is null. As a result, the first authenticator in the step always gets selected.
As the UserDefinedAuthenticatorEndpointConfig is not extended Serializable, when trying load the authenticator config from the context cache, there is an error ocurred. This UserDefinedAuthenticatorEndpointConfig does not required in the authentication flow, therefore skip adding that attribute of the localAuthenticator to cache.
Improve custom authentication adapter.
Add unit tests for authentication adapter.
Add diagnostic logs for authentication action execution.
If the authenticator's claim dialect is not the OIDC dialect, it directly checks for claim mapping. However, IdPs using the local claim dialect do not have claim mappings, causing the issue. If idp.isLocalClaimDialect() returns true, the email should retrieved using the WSO2 email claim.
Description
Issue:
Need to fix followings which related to the authentication execution flow with custom authentication extension:
flowID
as the url param to identity the corresponding authentication flow, instead ofsessionDataKey
.[1].
https://github.com/wso2/carbon-identity-framework/blob/5938f4d060ca17fcfecf53346ad0b2556bb52b0b/components/authentication-framework/org.wso2.carbon.identity.application.authentication.framework/src/main/java/org/wso2/carbon/identity/application/authentication/framework/handler/request/impl/DefaultRequestCoordinator.java#L350
[2].
https://github.com/wso2/carbon-identity-framework/blob/5938f4d060ca17fcfecf53346ad0b2556bb52b0b/components/authentication-framework/org.wso2.carbon.identity.application.authentication.framework/src/main/java/org/wso2/carbon/identity/application/authentication/framework/handler/step/impl/DefaultStepHandler.java#L672
Version
No response
The text was updated successfully, but these errors were encountered: