Wednesday 23 December 2009 11:23:38 am - 6 replies
Sometimes, during a web application development, you need to interface with your client's software(s) and/or websites in order to keep a common and coherent session within its applicative environment. To do this, it is often useful to use a special tool : SSO (Single Sign On). This article illustrates one way of integrating an eZ Publish based web application into an existing SSO architecture
Tuesday 06 July 2010 10:40:15 am
Thanks for this tutorial, I have implemented a SSO and it works fine. But it seems the SSOHandler is called everytime a page is loaded. I am wondering if I am doing something wrong, as I think the call is need only when the current user is Anonymous.
Is there a way to stop the SSOHandler call when a user is already logged in ?
Or should I put this "logic" in the SSOHandler::handleSSOLogin() method?
Thanks for the answer.
Tuesday 06 July 2010 12:15:18 pm
SSOHandler will be called every time a page is loaded if your user is not logged in, as SSO is handled in eZUser::instance() method.
Once your user is logged in, it won't be called any more. So maybe you should add some logic in your SSOHandler::handleSSOLogin() in order not to call your login webservice (or other SSO stuffs) if you are not logging in.
Wednesday 09 February 2011 6:30:14 pm
I could learn from this forum that you're successful in implementing SSO. That isn't my case. I would greatly appreciate if you can post me the code you implemented. I used the SPNEGO projet but I'm still unable to get it working as designed for.
Thanking you in advance.
Modified on Wednesday 09 February 2011 6:31:19 pm by Hamadou BABA
You must be logged in to post messages in this topic!