CAS Services Management "Access Denied"

855 views
Skip to first unread message

Eric Kyle

unread,
Feb 29, 2016, 2:43:21 PM2/29/16
to CAS Community
The title says it call. I have CAS (4.2 RC2) setup to authenticate against ADFS, which works fine when I got to localhost/cas, but when I try to go to the deployed cas-services page (which also authenticates successfully against cas/adfs), I get the message


Access Denied

You are not authorized to access this resource. Contact your CAS administrator for more info


This is the one thing holding me back from authenticating uPortal and our other services. I have looked in the deployerConfigContext.xml file and a hundred other places, but I can't seem to figure out how to authenticate properly. Any help would be greatly appreciated.


Eric

Misagh Moayyed

unread,
Feb 29, 2016, 3:13:31 PM2/29/16
to CAS Community

--
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.
Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/.

Warren White

unread,
Apr 19, 2016, 6:01:49 PM4/19/16
to CAS Community, mmoa...@unicon.net
And more specifically, the

Static List of Users


With my setup, I had to add the default casuser=Mellon,ROLE_ADMIN to the user-details.properties, then it allowed me to log in.

Dan Reeder

unread,
May 23, 2016, 7:48:41 PM5/23/16
to CAS Community
Hi Eric, did you ever manage to get this working? 
We're using CAS 4.2 with the additional cas-services app. CAS is setup to use our ADFS which works beautifully for other registered json services, but I can't figure out how to get the cas-services app to also pay attention to ADFS auth tickets. It would be nice if cas-services could check for an attribute being passed back from adfs (such as the presence of a particular AD group membership), but I'd settle for a static list of permitted principal usernames. 

cheers,
Dan

Eric Kyle

unread,
Jun 7, 2016, 8:50:54 AM6/7/16
to Dan Reeder, CAS Community
Hi Dan,

No, I still haven't figured this out - though I haven't had much time to look at it. I plan on digging back into it this summer.

Eric

--
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 post to this group, send email to cas-...@apereo.org.

Dan Reeder

unread,
Jun 7, 2016, 11:24:01 PM6/7/16
to CAS Community, mel...@gmail.com
I figured it out in the end... the users listed in /etc/cas/user-details.properties were required to have the "enabled" flag on the end, despite the comments indicating it was optional.
eg:
jsmith=notused,ROLE_ADMIN,enabled

cheers,
Dan

Misagh Moayyed

unread,
Jun 8, 2016, 12:00:09 AM6/8/16
to CAS Community

This probably points to some other underlying issue. I have never had to set that.

 

You can see the configuration of the demo webapp running on heroku. There is no reference to that flag.

https://github.com/apereo/cas/blob/heroku-mgmtwebapp/src/main/resources/user-details.properties

 

From: cas-...@apereo.org [mailto:cas-...@apereo.org] On Behalf Of Dan Reeder


Sent: Tuesday, June 7, 2016 8:24 PM
To: CAS Community <cas-...@apereo.org>

Eric Kyle

unread,
Jun 8, 2016, 1:57:40 PM6/8/16
to Dan Reeder, CAS Community
Are you logging into your cas-services app with ADFS? I can't figure out how to get cas-services to either use ADFS or ignore it and use the user in the user.details file.

Reply all
Reply to author
Forward
0 new messages