Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-5419

Update TokenExpired exception message to be consistent

    Details

    • 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

        Attachments

          Activity

            People

            • Assignee:
              jonthomas Jonathan Thomas
              Reporter:
              jonthomas Jonathan Thomas
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: