Paul,
Unfortunately the docs have not been updated.
The reference is here on line 186,
https://github.com/apereo/cas/blob/6.2.x/api/cas-server-core-api-configuration-model/src/main/java/org/apereo/cas/configuration/model/core/authentication/AuthenticationProperties.java
Set your logging to
Hi Ray,
I am actually using the notation prescribed in CAS 6.2.x documentation -
see
https://apereo.github.io/cas/6.2.x/configuration/Configuration-Properties.html#jdbc-1
:
# cas.authn.attribute-repository.jdbc[0].attributes.uid=uid
#
Paul,
You will have to check all your attribute names, they often change between
versions.
cas.authn.attribute-repository.jdbc
is now
cas.authn.attributeRepository.jdbc
Ray
On Mon, 2020-11-16 at 13:20 -0800, P N wrote:
Notice: This message was sent from outside the University of Victoria email
Hi,
I am in the process to migrate from CAS 5.3.15 to CAS 2.1 and in CAS 6 I am
using the same configuration properties as in CAS 5 for the principal
attribute release from an external JDBC repository using default Person
Directory to all services by default:
Matthieu,
In our tomcat bin directory, we have a file called setenv.sh with a couple
lines like this (among others)
CATALINA_OPTS="$CATALINA_OPTS
-Dspring.config.additional-location=/home/uvtomcat/config/bootstrap.yml"
CATALINA_OPTS="$CATALINA_OPTS
welp, got it working. This is embarrassing.
I had to put the log level to 'trace' to see the error.
in my cas.properties file i had this
cas.server.name=https://${hcc.local.hostname}.harford.edu:${hcc.cas.port},
I use variables passed in to set the hostname and port. But do you see it?
I
Hi everyone,
I am working on CAS 6.1.5 and I configured a spring configuration server
for my spring-boot applications.
The spring config server is working as expected for my CAS instance : I
wrote the bootstrap.properties file and put it in the src/main/resources
directory before building with
Hi,
You could also explicitly set the *pac4j-** dependencies with the version
4.0.3.
All the 4.x versions are compatible as long as the *pac4j-core* and other
*pac4j-** dependencies are on the same version.
Thanks.
Best regards,
Jérôme
Le lun. 16 nov. 2020 à 13:59, Frédéric Lohier a
écrit :
thanks again,
since I am not seeing a SubjectLocality field on multiple SAML service
definitions I have in my CAS deployment (all the others work though), and I
know that my CAS service is behind a load balancer, I am wondering if that
plays into it at all. I'll have to dig.
This particular
Hello,
Thank you for the *gradlew dependencies* tip which allowed me to move
forward.
The pac4j-core v4.1.0 dependency comes from CAS 6.2.5 (in the
gradle.properties of the cas-management overlay project, I have
cas.version=6.2.5 which matches the version of my cas server deployment)
and the
Hello to everyone,
We noticed that that the endpoint /consentReview and the matching
ConsentReviewEndpoint.java of the 6.0 CAS release have been removed from
6.1 release and its subsequent ones.
Has its functionality been moved to a different endpoint?
--
- Website:
11 matches
Mail list logo