CAS Management Service -- hxxps://example.edu/cas/login?service=http%3A%2F%2Flocalhost%3A8080%2Fcas-management%2Fmanage.html

josbrodie

unread,

May 27, 2018, 10:44:47 PM5/27/18

to CAS Community

This is driving me nuts - if anyone can notice what I am missing.

CAS Management Service triggers an authentication at hxxps://example.edu/cas-management --- however it redirects to login page as hxxps://example.edu/cas/login?service=http%3A%2F%2Flocalhost%3A8080%2Fcas-management%2Fmanage.html

I have grepped the folder where the folder for 'cas-services-management-overlay'; however no sign of the 'localhost:8080' configuration. 'netstat -alp' does not find a port listing on 8080.

cas-services-management-overlay]# grep -r "8080" .

./README.md:* `http://cas.server.name:8080/cas-management`

./target/cas-management/WEB-INF/classes/static/css/cas-management.css: border-color: #080808;

./target/cas-management/WEB-INF/classes/static/css/cas-management.css: background-color: #080808;

./target/cas-management/WEB-INF/classes/static/css/cas-management.css: border-color: #080808;

./target/cas-management/WEB-INF/classes/static/css/cas-management.css: background-color: #080808;

Binary file ./target/cas-management/WEB-INF/lib/xalan-2.7.2.jar matches

./target/war/work/org.apereo.cas/cas-management-webapp/WEB-INF/classes/static/css/cas-management.css: border-color: #080808;

./target/war/work/org.apereo.cas/cas-management-webapp/WEB-INF/classes/static/css/cas-management.css: background-color: #080808;

./target/war/work/org.apereo.cas/cas-management-webapp/WEB-INF/classes/static/css/cas-management.css: border-color: #080808;

./target/war/work/org.apereo.cas/cas-management-webapp/WEB-INF/classes/static/css/cas-management.css: background-color: #080808;

Binary file ./target/war/work/org.apereo.cas/cas-management-webapp/WEB-INF/lib/xalan-2.7.2.jar matches

Binary file ./target/cas-management.war.original matches

Binary file ./target/cas-management.war matches

Bergner, Arnold

unread,

May 28, 2018, 2:25:18 AM5/28/18

to cas-...@apereo.org

Maybe it’s only a default setting in the code…

You might try setting cas.mgmt.serverName in the management.properties if you haven’t already.

Regards

Arnold

--
- 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 you are subscribed to the Google Groups "CAS Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+u...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/59f4a0c5-fda6-4ab7-9bb2-c29cfaf8a4c8%40apereo.org.

josbrodie

unread,

May 28, 2018, 11:53:45 AM5/28/18

to CAS Community, arnold....@hrz.tu-darmstadt.de

Yes -- it was already set --- properties below.

However, I was less than accurate in my initial post.

The CAS.WAR and CAS-MANAGEMENT.WAR are running in same Tomcat. The Tomcat is listening on port 8080; there is an Apache listening at 443 that proxies traffic to the Tomcat.

Is the CAS-MANAGEMENT.war being very smart in that it is picking up the localhost:8080 from the Tomcat (which has no idea on the domain example.edu -- only the Apache does)? And the 'cas.mgmt.serverName' is being ignored?

# CAS server that management app will authenticate with

# This server will authenticate for any app (service) and you can login as casuser/Mellon

cas.server.name:https://example.edu

cas.server.prefix:https://example.edu/cas

cas.mgmt.adminRoles[0]=ROLE_ADMIN

cas.mgmt.userPropertiesFile=file:/etc/cas/config/admusers.properties

# Update this URL to point at server running this management app

cas.mgmt.serverName=https://example.edu

josbrodie

unread,

May 30, 2018, 1:28:09 AM5/30/18

to CAS Community, arnold....@hrz.tu-darmstadt.de

It was me, not the software.

Hunting around the group posting, I found another person had posted their 'server.xml' (Mike K). Their setup is similar to mine where I have Apache HTTPD --> Tomcat.

The key is the 'proxyName'. I did not have that earlier and hence it was defaulting to localhost:8080. Seems simple now, but I spent many hours triaging and now enjoying joy.

Thank you MIke! Your post from many weeks ago has saved my evenings.

<Connector port="8080" protocol="HTTP/1.1"

connectionTimeout="20000"

URIEncoding="UTF-8"

server="Apache"

address="127.0.0.1"

maxThreads="150"

proxyPort="443"

proxyName="cas.server.name"

scheme="https"

secure="true"/>

Olivier Calzi

unread,

May 30, 2018, 11:25:11 AM5/30/18

to cas-...@apereo.org

Hello,

Thanks to you Josbrodie.

Your unlock my situation too as i was also struggling with it.

Have a nice day.

________________________________________________________________
Olivier Calzi
Ingénieur Systèmes - EarlyTracks S.A.
Mail: olivie...@earlytracks.com

To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/e0708297-7ef0-4d7f-856b-253e7b5d1d62%40apereo.org.

Reply all

Reply to author

Forward