I found the method org.jboss.seam.contexts.Lifecycle.beginCall();. After calling that I have access to the needed Context objects, eg. Identity. But the question still is: is that the preferred approach for implementing SSO? Keeping the Login page / Login form described above is not longer a must if that simplifies the whole thing.
Any hint is highly appreciated :-)
For anyone who wants to know: I implemented the SSO funcionality by an Authenticator and used some navigation rules.
Facing the same SSO issues pretty much.
Thank you for the above details, I am still testing various scenarios. I have success with good logins, having to deal with bad logins is becoming more difficult.
1. where is the initial call made to
identity.loginin your setup?
2. how do you handle failed authentication, (pages.xml call to send to the logout page) without causing the automated login to kick in again, and start a loop?
3. are you still using filter (like above)?, interceptor? overrides?
Thanks for any additional insight.
can u please explain more how did u call the org.jboss.seam.contexts.Lifecycle.beginCall(); function? coz i'm having the same issue here. and also if possible the changes in the web.xml and pages.xml if any.
thanks in advance
never mind i figured out how to use the beginCall method but i'm stuck with how to bypass the following navigation rule in the login.page.xml:
Hey guys, it's two years later and I am running into the same problem. Can someone please share with me what navigation rules I need to implement to get the SSO capability to work? I have my authenticator already working for a single user login.