Hello Pouria, All,
To build on David's response, you should be able to echo out the HTTP Headers
on the server side with whatever language you are using.
For example, in PHP see http://php.net/manual/en/function.getallheaders.php
(Example #1) - just create a test page in your DocumentRoot,
Excellent. Thanks That was it.
On Monday, November 21, 2016 at 1:41:30 PM UTC-8, dhawes wrote:
>
> On 21 November 2016 at 16:13, pouria Mahmoudi > wrote:
> ...
> > Description: If enabled, this will store the user returned by CAS in an
> HTTP
> > header
> >
I'm having difficulty understanding how to configure the security layer
for the CAS management webapp, if I don't want to use a static list.
If I provide cas.mgmt.authzAttributes=memberOf, then it would seem that
I should set cas.mgmt.adminRoles to the group.
In theory this might seem like
On 21 November 2016 at 16:13, pouria Mahmoudi wrote:
...
> Description: If enabled, this will store the user returned by CAS in an HTTP
> header
> accessible to your web applications.
...
> but it doesn't look like I have an http header. At least by doing Inspect
>
Hi Everyone,
In the documentation, there is a part said:
Directive: CASAuthNHeader
Default: None
Description: If enabled, this will store the user returned by CAS in an
HTTP header
accessible to your web applications.
And this is the CAS configuration:
*LoadModule auth_cas_module
I had to implement custom Authentication handler where user creds are
stored in Cassandra db.
Followed below steps, not sure whether this is recommneded approach or not:
1. Created package org.apereo.cas..adaptors.cassandra
2. CassandraAuthenticationHandler
> public class
The issue was resolved.
I was modifying cas.properties within the overlay project and then compiling
the project. Actually you need to copy the updated cas.properties into a new
“etc/cas/config/” folder. That is located in the root of the drive where Tomcat
is located.
From: Maxwell, Gary
Done : https://github.com/apereo/cas/issues/2138
Let's switch to cas-dev.
Regards.
Le 18/11/2016 à 16:31, Misagh Moayyed a écrit :
>
> That’s an excellent find. I suspect bypass rules don’t account for
> non-interactive AuthN somehow. If you can change your config to bypass
> MFA based on the
Hy,
I would like to configure the new mgmt webapp (v5) authorization through
LDAP like in CAS v4.2.x.
I have a LDAP group (groupOfNames) with many members (member attribute).
In CAS 4.x, this was possible through ldaptive:AuthorizationGenerator.
In CAS 5.x, I didn't find any doc to configure