When setting up OAuth authentication with Azure AD (and possibly other OAuth providers) in DreamFactory, the jwt token is not being replaced with the session token correctly. This causes users to be redirected back to the login page instead of being authenticated.
A similar issue has already been handled in SAML authentication within saml-callback.component.ts. However, this logic has not been extended to OAuth connectors, leading to authentication failures.
Steps to Reproduce
1. Set up an Azure AD OAuth connection in DreamFactory.
2. Attempt to log in using the OAuth authentication flow.
3. Observe the network request after authentication:
• The redirect URL contains jwt instead of a valid session token.
• The user is directed back to the login page instead of being logged in.
Actual Behavior
• The jwt placeholder remains in the URL instead of being replaced with a session token.
• Users are redirected back to the login page without a valid session.
Expected Behavior
• The jwt token should be replaced with the correct session token after OAuth authentication.
• The user should be logged in successfully after authentication.
When setting up OAuth authentication with Azure AD (and possibly other OAuth providers) in DreamFactory, the jwt token is not being replaced with the session token correctly. This causes users to be redirected back to the login page instead of being authenticated.
A similar issue has already been handled in SAML authentication within saml-callback.component.ts. However, this logic has not been extended to OAuth connectors, leading to authentication failures.
Steps to Reproduce
1. Set up an Azure AD OAuth connection in DreamFactory.
2. Attempt to log in using the OAuth authentication flow.
3. Observe the network request after authentication:
• The redirect URL contains jwt instead of a valid session token.
• The user is directed back to the login page instead of being logged in.
Actual Behavior
• The jwt placeholder remains in the URL instead of being replaced with a session token.
• Users are redirected back to the login page without a valid session.
Expected Behavior
• The jwt token should be replaced with the correct session token after OAuth authentication.
• The user should be logged in successfully after authentication.