[OPENAM-5419] Update TokenExpired exception message to be consistent Created: 15/Jan/15  Updated: 20/Nov/16  Resolved: 08/Apr/15

Status: Resolved
Project: OpenAM
Component/s: rest
Affects Version/s: 10.0.2, 11.0.0, 11.0.2
Fix Version/s: 10.0.3, 11.0.4, 12.0.1, 13.0.0

Type: Improvement Priority: Minor
Reporter: Jonathan Thomas Assignee: Jonathan Thomas
Resolution: Fixed Votes: 0
Labels: EDISON, release-notes
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Target Version/s:
Support Ticket IDs:

 Description   

The TokenExpired exception thrown in IdentityServicesImpl does not not produce a consistent error message.

Customer reports that this may cause issues when used in the rest service.

Steps to reproduce:

  • Enable session failover in openam and have a multi-site deployment
  • Call the rest identity/attributes interface with an expired token.

e.g # curl.i386 http://localhost/openam/identity/attributes?subjectid=AQIC5wM2LY4SfcxQuZOO9ZB2Q69258s%2FnYn7WiacGEK%2Firw%3D%40AAJTSQACMjAAAlNLABQtODgyNzYwMzMxNTYxMDY4NDMyMAACUzEAAjAz%23

1. Call to OpenAM instance that is the authoritative server returns:
exception.name=com.sun.identity.idsvcs.TokenExpired
message:=Session was not obtained.

2. Call to OpenAM instance in the same site returns:

exception.name=com.sun.identity.idsvcs.TokenExpired
message=AQIC5wM2LY4SfcxQuZOO9ZB2Q69258s/nYn7WiacGEK/irw=@AAJTSQACMjAAAlNLABQtODgyNzYwMzMxNTYxMDY4NDMyMAACUzEAAjAz# Session was not obtained.

3. Call to an OpenAM instance in different site returns:
exception.name=com.sun.identity.idsvcs.TokenExpired java.lang.NullPointerException



 Comments   
Comment by Jonathan Thomas [ 08/Apr/15 ]

Fixed with r13336 12.0.x r13337 11.0.x r13338 10.0.x

Generated at Tue Oct 27 04:04:59 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.