Re: [cas-user] Re: Unsuccessful in configuring CAS 5.1.3 as a OAuth server ("/callbackAuthorize" redirects to "/" instead of client app)

2019-04-06 Thread Anuja Paradkar
Thanks for the mail. Sure will check that. I will appreciate if you can help me finding what might be happening in step number 4 below. This is forceful scenario to reproduce the problem (please note in prod this is random and scenario might be different): 1) Let your application take you to

[cas-user] Re: Unsuccessful in configuring CAS 5.1.3 as a OAuth server ("/callbackAuthorize" redirects to "/" instead of client app)

2019-04-06 Thread Anuja Paradkar
On Tuesday, 5 September 2017 21:13:56 UTC-6, Zhang Yu wrote: > > env: > Java 8, CAS 5.1.3, Tomcat 8.5 (standalone), IntelliJ, macOS Sierra. > > pom.xml: > > > 5.1.3 > > > > > org.apereo.cas > cas-server-webapp > ${cas.version} > war > runtime >

Re: [cas-user] Re: Unsuccessful in configuring CAS 5.1.3 as a OAuth server ("/callbackAuthorize" redirects to "/" instead of client app)

2019-04-05 Thread Ray Bon
Anuja, What you are seeing are duplicate log entries (time stamps match). Check 'additivity' in log4j2.xml to make sure only one message is logged. Ray On Fri, 2019-04-05 at 13:41 -0700, Anuja Paradkar wrote: Log file shows it creates and validates same ticket twice, no doubt during second

[cas-user] Re: Unsuccessful in configuring CAS 5.1.3 as a OAuth server ("/callbackAuthorize" redirects to "/" instead of client app)

2019-04-05 Thread Anuja Paradkar
Log file shows it creates and validates same ticket twice, no doubt during second validation it wont find entry for that service. Funny thing it does not throw exception but just uses default redirect path which is "/" in CAS source code. [[32m2019-04-02 19:58:09,776 INFO

[cas-user] Re: Unsuccessful in configuring CAS 5.1.3 as a OAuth server ("/callbackAuthorize" redirects to "/" instead of client app)

2019-04-03 Thread Anuja Paradkar
Facing same issue with 5.3.1, but on random occasion. Wondering were you able to resolve this. -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this

[cas-user] Re: Unsuccessful in configuring CAS 5.1.3 as a OAuth server ("/callbackAuthorize" redirects to "/" instead of client app)

2019-02-28 Thread Andy Ng
Cas server is design to only work with https, please change to use https even if you are testing only -Andy -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You

[cas-user] Re: Unsuccessful in configuring CAS 5.1.3 as a OAuth server ("/callbackAuthorize" redirects to "/" instead of client app)

2019-02-28 Thread Diego Henrique Pagani
Hi guys, I'm facing the same issue with 6.0.0 and 6.0.1. I'm not using https and using custom context-path (setting the server.servlet.context-path param) Does anyone have found the solution ? Em quarta-feira, 6 de setembro de 2017 00:13:56 UTC-3, Zhang Yu escreveu: > > env: > Java 8, CAS

[cas-user] Re: Unsuccessful in configuring CAS 5.1.3 as a OAuth server ("/callbackAuthorize" redirects to "/" instead of client app)

2019-02-28 Thread Diego Henrique Pagani
Hi guys, I'm facing the same issue with 6.0.0 and 6.0.1. I'm not using https. Does Em quarta-feira, 6 de setembro de 2017 00:13:56 UTC-3, Zhang Yu escreveu: > > env: > Java 8, CAS 5.1.3, Tomcat 8.5 (standalone), IntelliJ, macOS Sierra. > > pom.xml: > > > 5.1.3 > > > > >

Re: [cas-user] Re: Unsuccessful in configuring CAS 5.1.3 as a OAuth server ("/callbackAuthorize" redirects to "/" instead of client app)

2017-12-04 Thread Sandor Juhasz
We are on https. For a while it works and at some point - somehow related to existing/expired session it goes to location /. On Monday, December 4, 2017 at 12:51:03 PM UTC+1, Fei Wang wrote: > > When I use HTTPS , the issue gone. What's the trick here? > > On Mon, Dec 4, 2017 at 7:27 PM, Sandor

Re: [cas-user] Re: Unsuccessful in configuring CAS 5.1.3 as a OAuth server ("/callbackAuthorize" redirects to "/" instead of client app)

2017-12-04 Thread Tommy
When I use HTTPS , the issue gone. What's the trick here? On Mon, Dec 4, 2017 at 7:27 PM, Sandor Juhasz wrote: > Happening to us with 5.1.6, using openid connect webflow. Same symptoms, > only thing making it > interesting is that it does not happen every time. > > See

Re: [cas-user] Re: Unsuccessful in configuring CAS 5.1.3 as a OAuth server ("/callbackAuthorize" redirects to "/" instead of client app)

2017-12-04 Thread Sandor Juhasz
Happening to us with 5.1.6, using openid connect webflow. Same symptoms, only thing making it interesting is that it does not happen every time. See threads: https://groups.google.com/a/apereo.org/forum/#!topic/cas-user/TDh7Zz7g5TY -- *Sándor Juhász* System Administrator *ChemAxon* *Ltd*.

[cas-user] Re: Unsuccessful in configuring CAS 5.1.3 as a OAuth server ("/callbackAuthorize" redirects to "/" instead of client app)

2017-12-04 Thread Fei Wang
I met the exactly same problem . Have you resolve it ? On Wednesday, September 6, 2017 at 11:13:56 AM UTC+8, Zhang Yu wrote: > > env: > Java 8, CAS 5.1.3, Tomcat 8.5 (standalone), IntelliJ, macOS Sierra. > > pom.xml: > > > 5.1.3 > > > > > org.apereo.cas >