OpenAM Authorization-failed error when timed-out cookie present in the browser

Tagged: 

This topic contains 2 replies, has 2 voices, and was last updated by  kpattana 2 weeks, 6 days ago.

  • Author
    Posts
  • #19416
     kpattana 
    Participant

    We are getting “Authorization Failed” error from OpenAM after successful authentication, when
    – browser has a timed-out (stale) cookie.
    – and more than one OpenAM servers are UP in the cluster.

    We do not see this issue when one OpenAM server is running.

    How to Reproduce: –
    (1) Successfully authenticate to the protected app (https://myapp.abc.com),
    (2) wait for 15-minute idle session time out. close the browser, do not clear the cache or cookie.
    (3) Open the same browser and access the protected-app.
    (4) After successful authentication, We see Authorization failed page.

    Anybody has seen this issue ? We are using OpenAM 13.5 .

    Thanks,
    Kabi

    #19435
     Scott Heger 
    Participant

    Is the Authorization failed page from OpenAM or from your App?

    #19708
     kpattana 
    Participant

    Thank you Scott .

    The problem is resolved now. This was caused by random connection failure between OpenAM and UserStore.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.

©2017 ForgeRock - we provide an identity and access platform to secure every online relationship for the enterprise market, educational sector and even entire countries. Click to view our privacy policy and terms of use.

Log in with your credentials

Forgot your details?