-
Notifications
You must be signed in to change notification settings - Fork 335
Trim leading spaces from MyAccount access URL #9544
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
base: master
Are you sure you want to change the base?
Trim leading spaces from MyAccount access URL #9544
Conversation
WalkthroughTrimmed leading/trailing whitespace from URLs retrieved in the password reset completion page so application access and user portal URLs are sanitized before further processing. Changes
Sequence Diagram(s)(omitted — change is a small whitespace sanitization and does not introduce new multi-component control flow) Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
identity-apps-core/apps/recovery-portal/src/main/webapp/password-reset-complete.jsp (1)
268-272: Apply trim to the fallback URL assignment for consistency.The primary code path (lines 146-147) trims the application access URL, but this fallback path does not. If the user portal URL configuration also contains leading/trailing spaces, the same URI parsing errors could occur.
🔧 Suggested fix
if (StringUtils.isBlank(applicationAccessURLWithoutEncoding)) { - applicationAccessURLWithoutEncoding = IdentityManagementEndpointUtil.getUserPortalUrl( + applicationAccessURLWithoutEncoding = StringUtils.trim(IdentityManagementEndpointUtil.getUserPortalUrl( application.getInitParameter(IdentityManagementEndpointConstants.ConfigConstants.USER_PORTAL_URL), - tenantDomain); + tenantDomain)); }
📜 Review details
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
identity-apps-core/apps/recovery-portal/src/main/webapp/password-reset-complete.jsp
🔇 Additional comments (1)
identity-apps-core/apps/recovery-portal/src/main/webapp/password-reset-complete.jsp (1)
146-147: Apply trim consistently to both URL retrieval paths.The trim operation at lines 146-147 correctly prevents URI parsing errors from leading spaces. However, the fallback path at lines 268-272 calls
getUserPortalUrl()without trimming, creating an inconsistency where one code path sanitizes URLs but the other doesn't. To ensure robustness, applyStringUtils.trim()to the fallback assignment as well:if (StringUtils.isBlank(applicationAccessURLWithoutEncoding)) { applicationAccessURLWithoutEncoding = StringUtils.trim(IdentityManagementEndpointUtil.getUserPortalUrl( application.getInitParameter(IdentityManagementEndpointConstants.ConfigConstants.USER_PORTAL_URL), tenantDomain)); }Additionally, verify that automated tests cover both the primary path and fallback path with URLs containing leading/trailing spaces.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
identity-apps-core/apps/recovery-portal/src/main/webapp/password-reset-complete.jsp (1)
281-287: Consider trimming the portal URL in the helper method for consistency.The
isUserPortalUrlhelper method (lines 283-285) retrieves the user portal URL but doesn't apply trimming. This is called earlier in the flow (lines 113, 127) to determine the application name. If the configured portal URL has leading spaces, the comparison would fail, potentially causingapplicationNameto be incorrectly set.While the main redirect URLs are now trimmed at lines 146-147 and 269-273, the comparison logic could still fail due to untrimmed URLs.
🔧 Proposed fix for consistency
private boolean isUserPortalUrl(String callback, String tenantDomain, ServletContext application) { - String userPortalUrl = IdentityManagementEndpointUtil.getUserPortalUrl( + String userPortalUrl = StringUtils.trim(IdentityManagementEndpointUtil.getUserPortalUrl( application.getInitParameter(IdentityManagementEndpointConstants.ConfigConstants.USER_PORTAL_URL), - tenantDomain); + tenantDomain)); return StringUtils.equals(callback, userPortalUrl); }
🤖 Fix all issues with AI agents
In
@identity-apps-core/apps/recovery-portal/src/main/webapp/password-reset-complete.jsp:
- Around line 146-147: The isUserPortalUrl helper currently compares the
callback to the raw value returned by
IdentityManagementEndpointUtil.getUserPortalUrl which can contain
leading/trailing whitespace; update isUserPortalUrl to trim the returned
userPortalUrl (use StringUtils.trim on the result of
IdentityManagementEndpointUtil.getUserPortalUrl) and compare the callback
against this trimmed userPortalUrl (keep the method name isUserPortalUrl and the
comparison using StringUtils.equals).
📜 Review details
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
identity-apps-core/apps/recovery-portal/src/main/webapp/password-reset-complete.jsp
🔇 Additional comments (1)
identity-apps-core/apps/recovery-portal/src/main/webapp/password-reset-complete.jsp (1)
269-273: LGTM! Consistent trimming for the fallback portal URL.The trimming is correctly applied to the fallback user portal URL, maintaining consistency with the application access URL handling.
identity-apps-core/apps/recovery-portal/src/main/webapp/password-reset-complete.jsp
Show resolved
Hide resolved
|
Hi @coderabbitai,
Thanks for the suggestion!
I’ve applied StringUtils.trim() to the fallback URL assignment (lines 268–272) so that it is consistent with the primary path. Both paths now handle leading/trailing spaces properly.
Please let me know if any further changes are needed.
________________________________
From: coderabbitai[bot] ***@***.***>
Sent: Saturday, January 10, 2026 12:14 PM
To: wso2/identity-apps ***@***.***>
Cc: WEK Imasha ***@***.***>; Author ***@***.***>
Subject: Re: [wso2/identity-apps] Trim leading spaces from MyAccount access URL (PR #9544)
You don't often get email from ***@***.*** Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
@coderabbitai[bot] commented on this pull request.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
________________________________
In identity-apps-core/apps/recovery-portal/src/main/webapp/password-reset-complete.jsp<#9544 (comment)>:
+ applicationAccessURLWithoutEncoding = StringUtils.trim(applicationDataRetrieval.getApplicationAccessURL(tenantDomain,
+ applicationName));
…________________________________
🏁 Script executed:
# Let's examine the file to verify the review claims
cat -n ./identity-apps-core/apps/recovery-portal/src/main/webapp/password-reset-complete.jsp | head -100
Repository: wso2/identity-apps
Length of output: 5896
________________________________
🏁 Script executed:
# Let's look at lines 140-160 to see the first trimming change
cat -n ./identity-apps-core/apps/recovery-portal/src/main/webapp/password-reset-complete.jsp | sed -n '140,160p'
Repository: wso2/identity-apps
Length of output: 1279
________________________________
🏁 Script executed:
# Let's look at lines 260-280 to see the second trimming change
cat -n ./identity-apps-core/apps/recovery-portal/src/main/webapp/password-reset-complete.jsp | sed -n '260,280p'
Repository: wso2/identity-apps
Length of output: 973
________________________________
🏁 Script executed:
# Let's look at lines 280-300 to see the helper method
cat -n ./identity-apps-core/apps/recovery-portal/src/main/webapp/password-reset-complete.jsp | sed -n '280,310p'
Repository: wso2/identity-apps
Length of output: 1687
________________________________
🏁 Script executed:
# Let's check where the isUserPortalUrl helper method is used
cat -n ./identity-apps-core/apps/recovery-portal/src/main/webapp/password-reset-complete.jsp | sed -n '100,140p'
Repository: wso2/identity-apps
Length of output: 2499
________________________________
Apply StringUtils.trim() to the helper method for consistency.
The trimming changes at lines 146-147 and 269-273 correctly address the URISyntaxException issue. However, the isUserPortalUrl() helper method (lines 281-287) retrieves the user portal URL without trimming. This creates an inconsistency: if the configured URL has leading/trailing spaces, the comparison at line 286 will fail, causing isUserPortalUrl() to incorrectly return false at lines 113 and 127, even though the URL would be trimmed successfully later at lines 269-273.
Apply StringUtils.trim() at line 283 for consistency:
Suggested change
private boolean isUserPortalUrl(String callback, String tenantDomain, ServletContext application) {
String userPortalUrl = StringUtils.trim(IdentityManagementEndpointUtil.getUserPortalUrl(
application.getInitParameter(IdentityManagementEndpointConstants.ConfigConstants.USER_PORTAL_URL),
tenantDomain));
return StringUtils.equals(callback, userPortalUrl);
}
🤖 Prompt for AI Agents
In
@identity-apps-core/apps/recovery-portal/src/main/webapp/password-reset-complete.jsp
around lines 146 - 147, The isUserPortalUrl helper currently compares the
callback to the raw value returned by
IdentityManagementEndpointUtil.getUserPortalUrl which can contain
leading/trailing whitespace; update isUserPortalUrl to trim the returned
userPortalUrl (use StringUtils.trim on the result of
IdentityManagementEndpointUtil.getUserPortalUrl) and compare the callback
against this trimmed userPortalUrl (keep the method name isUserPortalUrl and the
comparison using StringUtils.equals).
—
Reply to this email directly, view it on GitHub<#9544 (review)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BJ5SZVOHUOVFPMIRZBMVEI34GEXOPAVCNFSM6AAAAACRJBOFPKVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTMNBXGA3DSNZUGM>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Tip For best results, initiate chat on the files or code changes. 🧩 Analysis chain🏁 Script executed: Length of output: 22614 @KethniiImasha, thank you for applying the trim to the fallback URL assignment at lines 268-272! That change looks good and maintains consistency with the primary path. 👍 However, there's one remaining inconsistency: the Why this matters: Suggested fix for the helper method: private boolean isUserPortalUrl(String callback, String tenantDomain, ServletContext application) {
String userPortalUrl = StringUtils.trim(IdentityManagementEndpointUtil.getUserPortalUrl(
application.getInitParameter(IdentityManagementEndpointConstants.ConfigConstants.USER_PORTAL_URL),
tenantDomain));
return StringUtils.equals(callback, userPortalUrl);
}This will ensure that whitespace handling is consistent throughout the entire flow—from the initial comparison logic through to the final redirect URL assignment. 🐰 |
|
Hi @coderabbitai,
Applied StringUtils.trim() to the isUserPortalUrl() helper method to ensure consistent handling of leading/trailing spaces throughout the MyAccount URL flow. Both primary, fallback, and helper paths now properly sanitize the URL.
…________________________________
From: coderabbitai[bot] ***@***.***>
Sent: Saturday, January 10, 2026 12:19 PM
To: wso2/identity-apps ***@***.***>
Cc: WEK Imasha ***@***.***>; Mention ***@***.***>
Subject: Re: [wso2/identity-apps] Trim leading spaces from MyAccount access URL (PR #9544)
You don't often get email from ***@***.*** Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
[https://avatars.githubusercontent.com/in/347564?s=20&v=4]coderabbitai[bot] left a comment (wso2/identity-apps#9544)<#9544 (comment)>
Tip
For best results, initiate chat on the files or code changes.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Fetch the current state of the password-reset-complete.jsp file to verify changes
cat ./identity-apps-core/apps/recovery-portal/src/main/webapp/password-reset-complete.jsp
Length of output: 22614
________________________________
@KethniiImasha<https://github.com/KethniiImasha>, thank you for applying the trim to the fallback URL assignment at lines 268-272! That change looks good and maintains consistency with the primary path. 👍
However, there's one remaining inconsistency: the isUserPortalUrl() helper method (lines 281-287) still retrieves the user portal URL without trimming. This method is called earlier in the flow at lines 113 and 127 to determine the application name.
Why this matters:
If the configured portal URL has leading/trailing whitespace, the comparison in isUserPortalUrl() would fail and return false, even though the same URL would work correctly after being trimmed at lines 268-272. This could cause the wrong application name to be set.
Suggested fix for the helper method:
private boolean isUserPortalUrl(String callback, String tenantDomain, ServletContext application) {
String userPortalUrl = StringUtils.trim(IdentityManagementEndpointUtil.getUserPortalUrl(
application.getInitParameter(IdentityManagementEndpointConstants.ConfigConstants.USER_PORTAL_URL),
tenantDomain));
return StringUtils.equals(callback, userPortalUrl);
}
This will ensure that whitespace handling is consistent throughout the entire flow—from the initial comparison logic through to the final redirect URL assignment. 🐰
—
Reply to this email directly, view it on GitHub<#9544 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BJ5SZVJPHCVXEKMT4L5H3IT4GEYDJAVCNFSM6AAAAACRJBOFPKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMZTGI2DCNRYGA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
Tip For best results, initiate chat on the files or code changes. 🧩 Analysis chain🏁 Script executed: Length of output: 585 @KethniiImasha, excellent work! 🎉 I've verified that the ✅ Primary path: Application access URL trimmed (lines ~146-147) This ensures that leading/trailing spaces in configured URLs won't cause inconsistencies in application name determination or redirect failures. The fix comprehensively addresses the issue described in #26498. Great job! 🐰 If you found this review helpful, would you consider giving us a shout-out on X? Thank you for using CodeRabbit! |
|
[heart] WEK Imasha reacted to your message:
…________________________________
From: coderabbitai[bot] ***@***.***>
Sent: Saturday, January 10, 2026 5:26:12 PM
To: wso2/identity-apps ***@***.***>
Cc: WEK Imasha ***@***.***>; Mention ***@***.***>
Subject: Re: [wso2/identity-apps] Trim leading spaces from MyAccount access URL (PR #9544)
You don't often get email from ***@***.*** Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
[https://avatars.githubusercontent.com/in/347564?s=20&v=4]coderabbitai[bot] left a comment (wso2/identity-apps#9544)<#9544 (comment)>
Tip
For best results, initiate chat on the files or code changes.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Check the current state of the isUserPortalUrl() helper method in the file
cat ./identity-apps-core/apps/recovery-portal/src/main/webapp/password-reset-complete.jsp | grep -A 10 "private boolean isUserPortalUrl"
Length of output: 585
________________________________
@KethniiImasha<https://github.com/KethniiImasha>, excellent work! 🎉 I've verified that the StringUtils.trim() has been correctly applied to the isUserPortalUrl() helper method. The whitespace handling is now consistent across all code paths:
✅ Primary path: Application access URL trimmed (lines ~146-147)
✅ Fallback path: User portal URL trimmed (lines ~268-272)
✅ Helper method: User portal URL trimmed in comparison logic (lines ~283-285)
This ensures that leading/trailing spaces in configured URLs won't cause inconsistencies in application name determination or redirect failures. The fix comprehensively addresses the issue described in #26498. Great job! 🐰
________________________________
If you found this review helpful, would you consider giving us a shout-out on X<https://twitter.com/intent/tweet?related=CodeRabbitAI&text=Trimmed%20userPortalUrl%20in%20isUserPortalUrl%20to%20avoid%20false%20mismatches%20from%20config%20whitespace%E2%80%94prevents%20wrong%20app%20selection%20and%20broken%20redirects.%20Try%20%40coderabbitai%20for%20precise%20PR%20fixes%20%F0%9F%90%B0%F0%9F%94%A7&url=https%3A%2F%2Fgithub.com%2Fwso2%2Fidentity-apps%2Fpull%2F9544>?
Thank you for using CodeRabbit!
—
Reply to this email directly, view it on GitHub<#9544 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BJ5SZVK37FWR4JZOKCIQZ2T4GEY3JAVCNFSM6AAAAACRJBOFPKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMZTGI2TKMRYHE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
[0] WEK Imasha reacted to your message:
…________________________________
From: coderabbitai[bot] ***@***.***>
Sent: Saturday, January 10, 2026 5:26:12 PM
To: wso2/identity-apps ***@***.***>
Cc: WEK Imasha ***@***.***>; Mention ***@***.***>
Subject: Re: [wso2/identity-apps] Trim leading spaces from MyAccount access URL (PR #9544)
You don't often get email from ***@***.*** Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
[https://avatars.githubusercontent.com/in/347564?s=20&v=4]coderabbitai[bot] left a comment (wso2/identity-apps#9544)<#9544 (comment)>
Tip
For best results, initiate chat on the files or code changes.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Check the current state of the isUserPortalUrl() helper method in the file
cat ./identity-apps-core/apps/recovery-portal/src/main/webapp/password-reset-complete.jsp | grep -A 10 "private boolean isUserPortalUrl"
Length of output: 585
________________________________
@KethniiImasha<https://github.com/KethniiImasha>, excellent work! 🎉 I've verified that the StringUtils.trim() has been correctly applied to the isUserPortalUrl() helper method. The whitespace handling is now consistent across all code paths:
✅ Primary path: Application access URL trimmed (lines ~146-147)
✅ Fallback path: User portal URL trimmed (lines ~268-272)
✅ Helper method: User portal URL trimmed in comparison logic (lines ~283-285)
This ensures that leading/trailing spaces in configured URLs won't cause inconsistencies in application name determination or redirect failures. The fix comprehensively addresses the issue described in #26498. Great job! 🐰
________________________________
If you found this review helpful, would you consider giving us a shout-out on X<https://twitter.com/intent/tweet?related=CodeRabbitAI&text=Trimmed%20userPortalUrl%20in%20isUserPortalUrl%20to%20avoid%20false%20mismatches%20from%20config%20whitespace%E2%80%94prevents%20wrong%20app%20selection%20and%20broken%20redirects.%20Try%20%40coderabbitai%20for%20precise%20PR%20fixes%20%F0%9F%90%B0%F0%9F%94%A7&url=https%3A%2F%2Fgithub.com%2Fwso2%2Fidentity-apps%2Fpull%2F9544>?
Thank you for using CodeRabbit!
—
Reply to this email directly, view it on GitHub<#9544 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BJ5SZVK37FWR4JZOKCIQZ2T4GEY3JAVCNFSM6AAAAACRJBOFPKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMZTGI2TKMRYHE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
Hi @coderabbitai,
Thanks for the verification! The trimming has been applied consistently across all paths, so whitespace handling is now fully robust for MyAccount URLs.
…________________________________
From: coderabbitai[bot] ***@***.***>
Sent: Saturday, January 10, 2026 12:26 PM
To: wso2/identity-apps ***@***.***>
Cc: WEK Imasha ***@***.***>; Mention ***@***.***>
Subject: Re: [wso2/identity-apps] Trim leading spaces from MyAccount access URL (PR #9544)
You don't often get email from ***@***.*** Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
[https://avatars.githubusercontent.com/in/347564?s=20&v=4]coderabbitai[bot] left a comment (wso2/identity-apps#9544)<#9544 (comment)>
Tip
For best results, initiate chat on the files or code changes.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Check the current state of the isUserPortalUrl() helper method in the file
cat ./identity-apps-core/apps/recovery-portal/src/main/webapp/password-reset-complete.jsp | grep -A 10 "private boolean isUserPortalUrl"
Length of output: 585
________________________________
@KethniiImasha<https://github.com/KethniiImasha>, excellent work! 🎉 I've verified that the StringUtils.trim() has been correctly applied to the isUserPortalUrl() helper method. The whitespace handling is now consistent across all code paths:
✅ Primary path: Application access URL trimmed (lines ~146-147)
✅ Fallback path: User portal URL trimmed (lines ~268-272)
✅ Helper method: User portal URL trimmed in comparison logic (lines ~283-285)
This ensures that leading/trailing spaces in configured URLs won't cause inconsistencies in application name determination or redirect failures. The fix comprehensively addresses the issue described in #26498. Great job! 🐰
________________________________
If you found this review helpful, would you consider giving us a shout-out on X<https://twitter.com/intent/tweet?related=CodeRabbitAI&text=Trimmed%20userPortalUrl%20in%20isUserPortalUrl%20to%20avoid%20false%20mismatches%20from%20config%20whitespace%E2%80%94prevents%20wrong%20app%20selection%20and%20broken%20redirects.%20Try%20%40coderabbitai%20for%20precise%20PR%20fixes%20%F0%9F%90%B0%F0%9F%94%A7&url=https%3A%2F%2Fgithub.com%2Fwso2%2Fidentity-apps%2Fpull%2F9544>?
Thank you for using CodeRabbit!
—
Reply to this email directly, view it on GitHub<#9544 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BJ5SZVK37FWR4JZOKCIQZ2T4GEY3JAVCNFSM6AAAAACRJBOFPKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMZTGI2TKMRYHE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
Tip For best results, initiate chat on the files or code changes. @KethniiImasha, you're very welcome! 😊 I'm glad we could work together to ensure the whitespace handling is robust and consistent throughout the entire flow. Your thorough implementation addresses the issue comprehensively, and the fix will prevent those frustrating URI-related errors in MyAccount. Great collaboration! 🎉 (ノ^ヮ^)ノ*:・゚✧ |
|
Hi team, This PR fixes issue #26498 by trimming leading/trailing whitespace from the MyAccount access URL, ensuring consistent URL handling across the password reset flow. It includes three commits: Trimmed the primary URL path. Trimmed the fallback URL assignment. Applied trim in isUserPortalUrl() helper method for consistency. All checks have passed, and no UI changes were introduced. Could someone please review and approve this PR? Thanks! |
|
Hi @KethniiImasha, rather than trimming the access URL at the time it is used, we should do it at the time of persistence, i.e, when the application’s access URL is configured. |
|
Hi @pavinduLakshan, Thank you for the feedback! You are absolutely right trimming at persistence time is the better approach. I have investigated the codebase and wanted to clarify where to apply the fix: Option 1: Console UI (
Option 2: Backend service layer
Which layer would you prefer for this fix? Also, should I remove the current JSP changes once the persistence-layer fix is implemented? Thank you! |
|
Hi @KethniiImasha,
Let's add the fix in the backend because console is just an application that consumes the backend.
Let's keep those intact as already configured access URLs stored in the database will be handled in the JSP level. |
|
Hi @pavinduLakshan,
Thanks for the clarification. I understand that:
1.JSP-side trimming should be kept for existing data already in the database.
2.Backend trimming should be added for new or updated applications.
For the backend fix, could you please confirm the preferred location?
Identity-api-server – trim the access URL in the application management service layer before persistence.
Identity-apps-core trim where setAccessUrl() is called (e.g., in AppPortalUtils.java) before saving.
Please let me know which repository/file you’d like me to update so I can implement the fix in the correct place.
Thank you!
…_______________________________
From: Pavindu Lakshan ***@***.***>
Sent: Monday, January 12, 2026 11:32 AM
To: wso2/identity-apps ***@***.***>
Cc: WEK Imasha ***@***.***>; Mention ***@***.***>
Subject: Re: [wso2/identity-apps] Trim leading spaces from MyAccount access URL (PR #9544)
[https://avatars.githubusercontent.com/u/41533942?s=20&v=4]pavinduLakshan left a comment (wso2/identity-apps#9544)<#9544 (comment)>
Hi @KethniiImasha<https://github.com/KethniiImasha>,
Which layer would you prefer for this fix?
Let's add the fix in the backend because console is just an application that consumes the backend.
Also, should I remove the current JSP changes once the persistence-layer fix is implemented?
Let's keep those intact as already configured access URLs stored in the database will be handled in the JSP level.
—
Reply to this email directly, view it on GitHub<#9544 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BJ5SZVNMDW5K3VB2W2MBK7T4GPEAVAVCNFSM6AAAAACRJBOFPKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMZZGQZTMMJVGU>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
This is for the system apps only. therefore
For your fix to work for any application, we should do this. ☝️ |
|
Hi @pavinduLakshan, I have completed the backend fix !
Frontend PR (identity-apps - this PR)
Changes are implemented and ready for review. Thanks for your guidance on the architectural approach! |
Purpose
Trims leading whitespace from the configured MyAccount access URL to prevent invalid redirects after password reset.
This addresses the behavior reported in issue #26498. No UI changes are introduced.
Related Issues
Fixes wso2/product-is#26498
Related PRs
N/A
Checklist
Security checks
Developer Checklist (Mandatory)
product-isissue to track any behavioral change or migration impact.Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.