[Fix] avoid to encode the realm when generating the authenticate url #485
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.