Re: [cas-user] Jar version collision with Maven Overlay

I would argue yes, in many cases it is… The problem seems to be that Maven does not take into account libs that are apart of the war, so if a dependency that's being added to the overlay pom conflicts with what's in the pom, then there are issues. This is not a thoroughly researched opinion, but

Re: [cas-user] The supplied service xxxxx is not authorized to use CAS proxy authentication.

It’d be always useful to provide what exact version of CAS being used when asking questions. For CAS 4.1+ (4.1 and greater), please consult the following guide on proxying config options: https://jasig.github.io/cas/4.2.x/installation/Configuring-Service-Proxy-Policy.html

Re: [cas-user] The supplied service xxxxx is not authorized to use CAS proxy authentication.

Hi Vincent, I added *p:allowedToProxy="true"* - But then it throws an exception. Seems like there is no property named "allowedToProxy" - STDERR] org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.jasig.cas.services.RegexRegisteredService#49

Re: [cas-user] The supplied service xxxxx is not authorized to use CAS proxy authentication.

Hi, add p:allowedToProxy="true" in your RegexRegisteredService bean Le 25/03/2016 08:53, Jahid Shohel a écrit : Hi Ray, Actually I can't see anything when I browse to "https://localhost:8443/cas/services";. Just as a side note, my configuration is like below - *_CAS:_* Running on "*https:

Re: [cas-user] The supplied service xxxxx is not authorized to use CAS proxy authentication.

Hi Ray, Actually I can't see anything when I browse to "https://localhost:8443/cas/services";. Just as a side note, my configuration is like below - *CAS:* Running on "*https://localhost:8443*"; through maven jetty *Client:* Running on "*https://localhost:8441*"; through maven jetty. CAS and