I'm trying to cas config server to pull configurations details from a
DynamoDB instance, but am running into a host of problems.
I've added the dependency to the pom.xml
org.apereo.cas
cas-server-core-configuration-cloud-dynamodb
${cas.version}
and added the following lines to s
Did you ever get the LdapAuthenticator to work? I'm looking at doing a
minor modification to the handler as well.
--Mike K.
On Thursday, January 25, 2018 at 3:25:00 PM UTC-8, Satnam Sarai wrote:
>
> I am able to create my own LdapAuthentication but CAS insert default
> LdapAuthentication as w
The title should read CAS 5.2.2 for the version
--Mike K.
On Wednesday, February 7, 2018 at 1:03:43 AM UTC-8, Mike Kromarek wrote:
>
> I recently switched from the Postgresql JPA ticket registry to MongoDB and
> am having a strange issue. The authentication succeeds, but then it fa
I recently switched from the Postgresql JPA ticket registry to MongoDB and
am having a strange issue. The authentication succeeds, but then it fails
to add the ticket to the mongo database, causing the process to fail and
return to the login screen.
-- cas.properties --
cas.ticket.registry.mon
I recently upgraded from CAS 5.1.6 to 5.2.0 and noticed that the theme
parameter in my JSON service definitions is being treated as if it is a
reference to a groovy script and not the name of the theme to load.
-- cas.properties --
### -- Theme settings -- ###
cas.theme.paramName=theme
spring.th
I'm looking to release custom attributes based off of the retrieved
attributes from LDAP for an authenticated user. Current I have my
cas.properties file setup to return all attributes for the authenticated
user, but I would like to be able to do something like the following:
Take the pwdLastS
