Thanks for your trust ---------------------------------
Frédéric, I remember you get some trouble with CAS OpenId module. I make it work and understand how it works globally. First, I create a web app demo inspired from : http://www.ibm.com/developerworks/java/library/j-openid/. You have to fill the input of a form with your user openid, after validation you are redirected to the OP, after authentication at the OP, you're are redirected to the callback url of the demo webapp and you are authenticated in the web app demo. I make the web app demo works with xxx.myopenid.com and then try to use CAS server as a OP. In CAS server, without configuration, in cas-servlet.xml, you have : <prop key="/openid/*">openIdProviderController</prop>. This controller makes CAS server being recognized as an OP, it responds to authentication requests make by RP (OpenId Relaying Party : my web app demo for example). Therefore, in my web app demo, I use the user openid : leleuj.localhost:8080/cas/openid/ to make authentication request being sent to my local CAS server on http://localhost:8080/cas (I need to add the host leleuj.localhost in my /etc/hosts). The redirect url to the OP is http://localhost:8080/cas/login with extra OpenId parameters. I don't know why this controller is activated by default ! If you followed : https://wiki.jasig.org/display/CASUM/OpenID#, you add OpenId support on the login phase : <prop key="/login">openIdValidateController</prop> (cas-servlet.xml). This configuration makes CAS server keep OpenId parameters received on /login url (no service parameter) and handles the final redirect to the callback url of the web app demo (declared through the first authentication send). Hope it helps you in your CAS OpenId understanding. Best regards, Jérôme -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
