This content has been marked as final.
Show 1 reply
-
1. Re: Why is login not an idempotent operation?
shane.bryzak Oct 31, 2013 2:18 PM (in response to kpiwko)You taught me a new word today Karel!
Anyway, the reason for this is the same as described in the comments of the issue you linked. PicketLink provides session-level tracking of the authenticated user, which is a pretty standard feature of the web. If you don't wish this behaviour, you can provide an alternative login method in a separate bean which performs a logout first - something like this should work:
public class MyLoginBean { @Inject Identity identity; public AuthenticationResult login() { identity.logout(); return identity.login(); } }
You then call MyLoginBean.login() to authenticate instead of Identity.login().