- Only show me content:
- Unfiltered files: dynamically added content
- Filtered files: dynamically added content
- Clear filters
|Participant||Role||Time Spent||Comments||Latest Comment|
|Author & Moderator||1h||1||Completely agree but from what I have seen of the server ...|
|Reviewer - Complete||16m||1||it feels a bit odd that idToServerTable has the original ...|
|Reviewer - Complete||13m||1||So as far as I can see there's 3 calls using getServerFro...|
|Reviewer - Complete||1m||1||lgtm|
|Reviewer - Complete||16m||1||LGTM|
SystemConfigurationUtil maintains a list if server IDs to server URLs and is used when Federation calls need to be made to the original server.
The URLs being stored assume that the deployment context is always lowercase so a lookup of a server ID always returns a lowercase version of the URL. If the deployment context is not all lower case, the request fails with a 404.
For example, a set of servers made up of:
These are stored in the list as http://openam1.example.com/sso and http://openam2.example.com/sso so a request meant for 2 that hits 1 is sent to http://openam2.example.com/sso which fails with a 404.
Example problem case can be seen in IDPArtifactResolution.onMessage()
So a request that should go to http://openam1.example.com/SSO/ArtifactResolver/metaAlias/idp ends up going to http://openam1.example.com/sso/ArtifactResolver/metaAlias/idp
The fix ensures that the server URL is kept in its original case and is returned as the result of a server ID lookup, which is then used in real cross-talk Federation calls.
Issues Raised From Comments