Skip to content

Conversation

@SegFault89
Copy link

@SegFault89 SegFault89 commented Jun 5, 2025

This merge request addresses an issue where the authenticate endpoint URL was incorrectly generated, preventing the use of multi-level or nested realm paths (e.g., /my/pathTo/realm).

Previously, the Uri.Builder.appendPath() method was used for the realm segment. This method URL-encodes characters, converting forward slashes (/) into %2F. As a result, ForgeRock Access Management (AM) would interpret root/MyOrganizationLogin as a single literal realm name, instead of a path to a sub-realm, leading to authentication failures for nested realms.

… in order to allow specifying the complete realm path (e.g. '/my/pathTo/realm')
@SegFault89
Copy link
Author

For additional context: we've observed that the ForgeRock iOS SDK (at least version 4.6.0) appears to already correctly handle and accept realm paths

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant