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

Page Refresh Issue in Consent Flow with OBConsentServlet #228

Open
aka4rKO opened this issue Dec 12, 2024 · 0 comments
Open

Page Refresh Issue in Consent Flow with OBConsentServlet #228

aka4rKO opened this issue Dec 12, 2024 · 0 comments

Comments

@aka4rKO
Copy link
Contributor

aka4rKO commented Dec 12, 2024

The oauth2_authz.do page is unable to refresh properly during the consent flow. When navigating through the login and OTP pages, the flow redirects to oauth2_authz.do. Based on the web.xml configuration, it is mapped to the OBConsentServlet:

<servlet-mapping>
    <servlet-name>OBConsentServlet</servlet-name>
    <url-pattern>/oauth2_authz.do</url-pattern>
</servlet-mapping>

The OBConsentServlet determines whether to navigate to ob_cds_profile_selection.jsp or ob_cds_account_selection.jsp based on the preSelectedProfileId. The servlet forwards the request using the following code[1]:
dispatcher.forward(originalRequest, response);
This forward operation occurs server-side, meaning the browser is unaware of the forwarding, and the URL in the browser remains unchanged.

When the page is refreshed, it navigates back to the OBConsentServlet and attempts to validate the authorization using the same key. Since this key has already been used, an error is triggered.

[1]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant