Closed magaton closed 9 years ago
Unfortunately, I'm not surprised that there is an error on this demo.
There are main changes that have been lately committed to the CAS server 4.0.0 I need to adapt to.
Will do that next week as well as updating documentation BTW...
Thanks very much for the quick reply.. I am pretty much in a hurry to show a working demo on Tuesday. I've tried to solve it myself, but with missing class in the latest CAS server code and with no knowledge what should be used instead, i couldn't go much further. Do you maybe have any pointers how I can solve this? Thanks again. Milan
OK. I'll try to update the demo on Monday. I think that most changes are located in the deployerConfigContext.xml file: try to start from the default one in CAS server : https://github.com/Jasig/cas/blob/master/cas-server-webapp/src/main/webapp/WEB-INF/deployerConfigContext.xml...
Thanks, I tried replacing deployerConfigContext.xml, but it seems that this is not the only problem. Now I have new exceptions on tomcat startup like:
Your help is much appreciated.
Right! The logout has also been changed. I will take a look at that tomorrow... That said, I have a working demo with CAS 3.5.x : https://github.com/leleuj/cas-oauth-demo-3.5.x...
Thanks very much. I've tried demo with CAS 3.5.x, created a new issue and put some comments there.
I've just updated the demo but it still doesn't work as a patch is required : https://issues.jasig.org/browse/CAS-1331...
I just merged the pull request and everything works now...
Hi, I've pulled the latest: pac4j, cas and this demo, started cas & cas2 without the problem, but when I try to sign in with facebook, I am getting error: CAS is Unavailable There was an error trying to complete your request. Please notify your support desk or try again.
The tomcat log is:
2013-07-25 12:27:25,663 INFO [org.jasig.cas.web.flow.InitialFlowSetupAction] - <Setting path for cookies to: /cas/>
2013-07-25 12:27:26,748 INFO [org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] -
Any idea?
Pretty strange : don't you have a more explicit log ? I tested the Facebook support in the demo and it works...
ok, it looks like it happens because i am already somehow authenticated (maybe left from the previous run). Btw, when I logout and login, it works, but this time it doesn't ask me to allow auth via Facebook.
This is the full trace in tomcat from the moment I clicked on "authenticate with FB":
2013-07-26 08:32:14,350 INFO [org.jasig.cas.web.flow.InitialFlowSetupAction] - <Setting path for cookies to: /cas/>
2013-07-26 08:32:14,355 DEBUG [org.jasig.cas.web.support.CasArgumentExtractor] -
About the logout and login which doesn't ask for premissions confirmation, it's normal : the second time Facebook does not ask about permissions.
Can you give some more details about the scenario which fails ? Thx
Hi, when I try to run the demo under tomcat with latest CAS I am getting: 2013-07-19 20:22:33,204 ERROR [org.springframework.web.context.ContextLoader] -
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'centralAuthenticationService' defined in ServletContext resource [/WEB-INF/spring-configuration/applicationContext.xml]: Cannot resolve reference to bean 'authenticationManager' while setting constructor argument; nested exception is org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [org.jasig.cas.authentication.AuthenticationManagerImpl] for bean with name 'authenticationManager' defined in ServletContext resource [/WEB-INF/deployerConfigContext.xml]; nested exception is java.lang.ClassNotFoundException: org.jasig.cas.authentication.AuthenticationManagerImpl
any hint? Milan