The management app is a completely stand alone system. Needs to be
configured and ran separately. I don't use the gradle method, but you'll
have to make sure it spins up on a different port than CAS, as they are
two different systems. You can put the wars into a standalone Tomcat,
which is how we deploy.
The stub entries are for selecting specific attributes to return per
service. Not really a concern until you get the rest of it going, it's
just something that caught me off guard.
The management admin properties is probably right. I haven't worked with
the admin pages. Management application is separate.
On 07/11/2017 09:20 AM, Toby Archer wrote:
I have indeed been trying to get one thing working at a time. Though
when I get stumped with one thing I will try something else for a
little while, usually it helps me see things from a different angle.
I think I understand a little how the management app works. I have
plenty of experience with uPortal so servlet containers make sense to
me. But I'm not sure how I'm supposed to spin up this web app along
with CAS. I run cas through "gradlew run" and I don't know where it's
tomcat instance is or if I can just drop a war into it's tomcat. So I
guess I'm really just unsure of how I get both of these running at the
same time. Does it work like the overlay portlets in uPortal where the
management app is basically a subproject of CAS? It get's built and
deployed along with CAS? I feel like there is a lot of assumptions in
this documentation about what I know. :\
I'm not sure what the stub entries are for. Is that how I'm supposed
to link my LDAP account to things like ROLE_ADMIN in CAS?
I'm don't really know what I'm doing with adminusers.properties. What
I'm trying to do is say "toben.archer is an admin, give him permission
to the stuff." but that doesn't seem to be working. Here is my current
configuration for trying to get access to /status/dashboard:
management.contextPath=/status
management.security.enabled=true
management.security.roles=ACTUATOR,ADMIN
management.security.sessions=if_required
cas.adminPagesSecurity.ip=127\.0\.0\.1
cas.adminPagesSecurity.loginUrl=https://localhost:8443/cas/login
cas.adminPagesSecurity.service=https://localhost:8443/cas/status/dashboard
cas.adminPagesSecurity.users=file:/etc/cas/config/adminusers.properties
cas.adminPagesSecurity.adminRoles[0]=ROLE_ADMIN
cas.adminPagesSecurity.actuatorEndpointsEnabled=true
cas.mgmt.userPropertiesFile=classpath:/adminusers.properties
On Monday, July 10, 2017 at 4:11:51 PM UTC-5, richard.frovarp wrote:
Just do one small piece at a time and validate it's doing what you
want. Sounds like that is what you have been doing. If you're
going to use the JPA service registry, you need to use the
management application.
https://apereo.github.io/cas/5.1.x/installation/Installing-ServicesMgmt-Webapp.html
<https://apereo.github.io/cas/5.1.x/installation/Installing-ServicesMgmt-Webapp.html>
That will let you add and modify service definitions. For
properties you're going to need to add stub entries to select them
for selective attribute return if desired.
https://apereo.github.io/cas/5.1.x/installation/Configuration-Properties.html#stub
<https://apereo.github.io/cas/5.1.x/installation/Configuration-Properties.html#stub>
You are also doing to want to watch out for the ddlAuto attribute.
At some point you are going to want to change it to just update.
Otherwise it will end up dropping tables as you restart the
services to do further testing.
What are you trying to do with adminusers.properties? I'm not
familiar with that one. The management application uses a
different file (or an LDAP attribute).
On 07/10/2017 02:53 PM, Toby Archer wrote:
I'm kind of fumbling in the blind getting a CAS configuration up
and running. So let me explain where I'm at and what I want to
achieve. I've got a cas server running on my machine which uses
LDAP as it's auth backend. I can login with my ldap credentials
just fine, but at this point I can do nothing with it.
What I need to figure out and haven't yet (which I've been trying
to figure out):
1. How do you setup a registry of authenticated apps. We are
currently running 3.5 and we have a database table for this.
I think continue that way would be fine, but I'm open other
options.
2. How do you setup tickets in ehcache for clustering: once I
move off of my desktop into dev and prod there will be two
servers communicating.
3. configure the /status monitor.
I've managed, with some help from here, to get LDAP
authentication working. But now I'm trying to get the status and
dashboard up and running. While the brevity of the documentation
is appreciated, it perhaps is a bit to spartan. I found this:
https://apereo.github.io/cas/5.1.x/installation/Configuration-Properties.html#spring-boot-endpoints
<https://apereo.github.io/cas/5.1.x/installation/Configuration-Properties.html#spring-boot-endpoints>
which makes reference to a file named "|adminusers.properties"
|which I'm still not sure if I'm loading. (it doesn't show up
when I run gradlew run) After much confusion I noticed the lines
above where I specify the location of that file. But like I said,
I can't say for sure that it is actually loading. I see there is
also a configuration for LDAP:
https://apereo.github.io/cas/5.1.x/installation/Configuration-Properties.html#ldap-authorization
<https://apereo.github.io/cas/5.1.x/installation/Configuration-Properties.html#ldap-authorization>
but I honestly can't make heads or tails of it.
Sorry for the rookie questions, but I'm seriously lost. Is there
a more through documentation/guide somewhere I've missed? Any
help would be much appreciated.
--
- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines:
https://apereo.github.io/cas/Mailing-Lists.html
<https://apereo.github.io/cas/Mailing-Lists.html>
- CAS documentation website: https://apereo.github.io/cas
- CAS project website: https://github.com/apereo/cas
---
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 [email protected] <javascript:>.
To view this discussion on the web visit
https://groups.google.com/a/apereo.org/d/msgid/cas-user/c312ad21-3a07-427b-a30a-be617fe775cb%40apereo.org
<https://groups.google.com/a/apereo.org/d/msgid/cas-user/c312ad21-3a07-427b-a30a-be617fe775cb%40apereo.org?utm_medium=email&utm_source=footer>.
--
- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines:
https://apereo.github.io/cas/Mailing-Lists.html
- CAS documentation website: https://apereo.github.io/cas
- CAS project website: https://github.com/apereo/cas
---
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 [email protected]
<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/a/apereo.org/d/msgid/cas-user/d0679dd9-bd9b-41a7-8848-ec55c20a5826%40apereo.org
<https://groups.google.com/a/apereo.org/d/msgid/cas-user/d0679dd9-bd9b-41a7-8848-ec55c20a5826%40apereo.org?utm_medium=email&utm_source=footer>.
--
- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html
- CAS documentation website: https://apereo.github.io/cas
- CAS project website: https://github.com/apereo/cas
---
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/a/apereo.org/d/msgid/cas-user/05cc719f-ef89-280f-23e3-8e6e37ff2c00%40ndsu.edu.
