Problem with SSO since Update

(8 posts) (2 voices)

Tags:

  1. Adrian, Member

    Since the last update 4.4.0 SSO isn't working correctly.

    The first site call always fails with error-message:
    Status 302 - Moved Temporarily

    We have to refresh the site (F5) three oder four times. After that everything is ok and the login works.

    Any suggestions?

  2. myDBR Team, Key Master

    Adrian,
    There are no changes in SSO that would cause this.

    The 302 error would indicate change in the SSO server side. Could you check what is URL that is causing the 302 error from the server?

    --
    myDBR Team

  3. Adrian, Member

    have a look at my firebug.

    First call - Ends after 21 Calls

    after 3-4 "F5"

  4. myDBR Team, Key Master

    Could you check why the server responds with "302 Moved Temporarily"?

    --
    myDBR Team

  5. Adrian, Member

    The question is how ;-)

  6. myDBR Team, Key Master

    Do you have acess to the server? Your server admin should be able to anwer to you.

    --
    myDBR Team

  7. Adrian, Member

    Yes I have access to the php scripts and server logs. Currently we don't know why 302 appears.
    It seems to be a redirect/timeout problem.
    We've implemented SSO close to your guide and as I've mentioned before it worked well in 4.0.0.

  8. myDBR Team, Key Master

    Adrian,
    based on the Firebug log, it looks like the SSO login is unsuccessful i.e the hash calculation for some reson does not match. Therefore, myDBR tries to redirect user back to SSO server for another login, hence the loop.

    Please contact the support email so we can help to take a look what might be causing your problem.

    --
    myDBR Team


Reply

You must log in to post.