Issue Details (XML | Word | Printable)

Key: OPENSSO-6184
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: quitefire
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
opensso

Login issue with 2 OpenAM instances using the OpenAM java SDK API

Created: 05/Jul/12 08:19 AM   Updated: 05/Jul/12 08:19 AM
Component/s: authentication, Identity SDK
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Original Estimate: 2 days
Original Estimate - 2 days
Remaining Estimate: 2 days
Remaining Estimate - 2 days
Time Spent: Not Specified
Time Spent - Not Specified

File Attachments: 1. Text File client-stacktrace.txt (5 kB) 05/Jul/12 08:19 AM - quitefire
2. Zip Archive openam_debug_log.zip (6 kB) 05/Jul/12 08:19 AM - quitefire


Tags:
Participants: quitefire


 Description  « Hide

We have 2 OpenAM instances deployed on 2 JBoss servers (jboss-5.1.0.GA), and 1 desktop app client (using OpenAM Java SDK) connecting to these servers. The current issue that we are facing is as following:
+ step 1: from the client, connect to the 1st server -> successfully
+ step 2: logout the server, but do not close the client app
+ step 3: continue to use this client to login to the 2nd server
==> problem here: authentication phase is done successfully, however we cannot retrieve the SSO token via AuthContext object
(Note that we would still be able to login and retrieve token on the 1st server at this time)

    • Our sample code to retrieve SSO token:
      ......
      if (status.equals(AuthContext.Status.SUCCESS)) { String ssoToken = authenContext.getSSOToken().getTokenID().toString(); return new SsoResult(status, ssoToken, this); }

NOTE: If after each logging out of a server, we completely close the desktop app client and then re-open it to access another server, problem will not happen.

We also attached here the stacktrace for your reference.

Thank you!



There are no comments yet on this issue.