Max,
If you want tomcat to listen on localhost only then edit server.xml file
and add the address to the connector, and do the same for 8443 connector.
ex:
Then in HTTP proxy config use https://localhost:8443 .
In cas.properties you can specify with
"cas.server.name=https://localhost:8443;
Hi CAS Users,
I'm serving CAS via an HTTP proxy, is it possible to bind the embedded
tomcat server to localhost only?
I found configuration properties, server.port and
cas.server.tomcat.http.port, but I don't see an associated server.address
or server.host or cas.server.tomcat.http.address?
Any
We can't get the status/discovery endpoint to work following this:
https://apereo.github.io/cas/5.3.x/installation/Configuration-Properties.html#cas-endpoints
We keep getting this error message:
Property: cas.monitor.endpoints.discovery.enabled
Value: true
Origin:
Here is my REST endpoint detail
1. GET email
2. GET username
3. GET password
On Tuesday, July 21, 2020 at 2:24:13 PM UTC+7 Napoleon Ponaparte wrote:
> Hi,
> Can you support me about Password Management via REST API?
> I have setup my CAS configuration global like this:
>
>
>
Hi,
Can you support me about Password Management via REST API?
I have setup my CAS configuration global like this:
{"_id":{"$oid":"5f0e5cb43c849e73fc9fb39c"},"name":"cas.authn.pm.enabled","value":"true"}
Hi,
I think you have to map your custom user attributes from attribute
repository, to your claims/scope oidc :
https://apereo.github.io/cas/5.3.x/installation/Configuration-Properties.html#openid-connect
Jérôme.
Le lun. 20 juil. 2020 à 20:55, Yan Zhou a écrit :
> Hello,
>
> I have CAS5.3.x,
