ar:5.2.2]
>
>
>
> On Monday, April 9, 2018 at 2:05:47 AM UTC-5, Olivier Calzi wrote:
>>
>> Hi,
>>
>> No as it's behind an haproxy i'm using the 443.
>>
>> Here you will find more logs who
ocessorLight.process(AbstractProcessorLight.java:66)
> ~[tomcat8-coyote-8.5.14.jar:8.5.14]
> at
> org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:861)
> ~[tomcat8-coyote-8.5.14.jar:8.5.14]
> at
> org.apache.tomcat.util.net.AprEnd
As it's behind an haproxy i expected it to be the true url lie
sso..xy/cas-management not localhost.
On Sunday, April 8, 2018 at 10:29:24 PM UTC+2, Manfredo Hopp wrote:
>
> What do you expect you url to be.
> What do you type con browser
>
> El domingo, 8 de abril de 2018, O
, 8 de abril de 2018, Olivier Calzi <o...@earlytracks.com
> > escribió:
>
>> Hi,
>>
>> No problem.
>>
>> My folder is : /etc/cas/config
>> The file is named management.properties
>>
>>
>>
>> Le dim. 8 avr. 2018 à 18:11, Man
nt-webapp
>
> El domingo, 8 de abril de 2018, Olivier Calzi <o...@earlytracks.com
> > escribió:
>
>> Hello,
>>
>> It's my first post here so please be kind to me :).
>>
>> I managed to get a working CAS server with the following dependency on
Hello,
It's my first post here so please be kind to me :).
I managed to get a working CAS server with the following dependency on the
pom.xml
5.2.2
org.apereo.cas
cas-server-support-json-service-registry
${cas.version}
org.apereo.cas
