Affects Version/s: 5.5.1, 6.0.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206
Sprint:AM Sustaining Sprint 52, AM Sustaining Sprint 53
Support Ticket IDs:
Needs QA verification:Yes
Introspection of access token fails when the wrong case of realm is used in the first request
#1. Setup two openAMs , AM1 and AM2 ( embedded with replication )
#2. Create a DEMO realm in uppercase
#3. Create an oauth agent in the DEMO realm
#4. Run the following script.
It will create an access token in AM1 and introspect in AM2.
Notice that the "first" introspect request is in the lower case for "demo" realm
All subsequent introspect requests will fails in AM2 until you restart the server, AM2
Ensure that the introspect request matches the case sensitivity of the realm.
A single server test alternative is
1. Access URL as /DEMO and get the access token
2. Stop the AM
3. Start AM and access introspect using /demo URL with the previous access token in #1.
NOTE: But see also