cas-management.log
2019-04-10 06:01:07,068 INFO
[org.apereo.cas.mgmt.web.CasManagementWebApplicationServletInitializer] -
The following profiles are active: standalone
2019-04-10 06:01:12,235 DEBUG
[org.apereo.cas.config.CasCoreUtilSerializationConfiguration] - Configuring
component
Thank you for the quick reply.
First I accessed via the browser
https://cas.example.com/cas/status/discovery, then CAS directed to login.
After successfully logging in, the results are like this:
{
"@class": "java.util.LinkedHashMap",
"profile": {
"@class":
Fahmi,
I have not set up any of the status features for cas, so have no experience
here.
Can you access it with a browser (that is, have you verified it is working as
expected)?
What is your reason for using curl?
Perhaps there is another alternative that others on the list have tried.
Ray
i have to configured like:
*cas.properties*
cas.adminPagesSecurity.ip = .*
cas.adminPagesSecurity.loginUrl = ${cas.server.prefix}/login
cas.adminPagesSecurity.service = ${cas.server.prefix}/status/dashboard
cas.adminPagesSecurity.users = file:/etc/cas/config/admusers.properties
i have to configured like:
*cas.properties*
cas.adminPagesSecurity.ip = .*
cas.adminPagesSecurity.loginUrl = ${cas.server.prefix}/login
cas.adminPagesSecurity.service = ${cas.server.prefix}/status/dashboard
cas.adminPagesSecurity.users = file:/etc/cas/config/admusers.properties
Please tell me how to unprotect? In cas.properties i have to set
endpoints.status.discovery.enabled = true
..sensitive = false
Sorry for my questions. Thank you Ray.
Sent from my iPhone
> On 10 Apr 2019, at 07.05, Ray Bon wrote:
>
> Fahmi,
>
> It looks like /cas/status/discovery is protected
Fahmi,
It looks like /cas/status/discovery is protected by cas and it redirects to
cas/login (status code 302).
Should the discovery page be protected?
Ray
On Tue, 2019-04-09 at 16:43 -0700, Fahmi L. Ramdhani wrote:
I tried accessing the result curl like this:
curl -v
I tried accessing the result curl like this:
curl -v https://cas.example.com:8443/cas/status/discovery
* Trying 2xx.60.112.9...
* Connected to cas.example.com (2xx.60.112.9) port 8443 (#0)
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 592 certificates in /etc/ssl/certs
I tried accessing the result curl like this:
curl -v https://cas.example.com:8443/cas/status/discovery
* Trying 103.60.182.9...
* Connected to cas.example.com (103.60.182.9) port 8443 (#0)
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 592 certificates in /etc/ssl/certs
I tried accessing the result curl like this
curl -v https://cas.example.com/cas/status/discovery * Trying 103.60.182.9... *
Connected to cas.example.com (xx.60.xxx.2) port 8443 (#0)
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt * found 592
certificates in /etc/ssl/certs *
CAS 6.0.3 is released:
https://github.com/apereo/cas/releases/tag/v6.0.3
--Misagh
--
- 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 message because
Raphael,
Tomcat logs are in TOMCAT_HOME/logs.
Ray
On Tue, 2019-04-09 at 02:11 -0700, Raphaël CHANE wrote:
hello,
I am trying to get CAS to work with AD, but i've got this error on tomcat logs
"
/var/log/cas
debug
I did some research and saw
hello,
I am trying to get CAS to work with AD, but i've got this error on tomcat
logs "
/var/log/cas
debug
I did some research and saw that it was no longer necessary to use the
deployerConfigContext.xml file with cas 5.3.x.
here is my
13 matches
Mail list logo
