Re: [cas-user] CAS 6.2.1 attribute release not working with PersonDirectory

[Ray Bon]

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 debug. You should see something about an 'unbound 
attribute' or 'could not bind attribute' with the name of the attribute. I am 
sure there are more changes than just that one.

It was a long time since we upgraded and I did not remember that I must have 
search the code base for the attribute names.

Ray

On Mon, 2020-11-16 at 14:40 -0800, P N wrote:
Notice: This message was sent from outside the University of Victoria email 
system. Please be cautious with links and sensitive information.

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
# cas.authn.attribute-repository.jdbc[0].attributes.display-name=displayName  
...

However, even changing the configuration as suggested to old notation from CAS 
5 - cas.authn.attributeRepository.jdbc[0] ... , I am getting same results, i.e. 
no attributes released.

Thanks,
Paul
On Monday, November 16, 2020 at 4:59:59 PM UTC-5 Ray Bon wrote:
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 
system. Please be cautious with links and sensitive information.

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:

cas.authn.attribute-repository.default-attributes-to-release=username,role,group,inherited_group,user_id,crm_user_id,organization_id,first_name,middle_name,last_name,email,work_phone,phone_extension,active,userstatus,accessMetadata
cas.authn.attribute-repository.jdbc[0].singleRow=false
cas.authn.attribute-repository.jdbc[0].sql= ...
cas.authn.attribute-repository.jdbc[0].username=user_name
cas.authn.attribute-repository.jdbc[0].columnMappings.attribute_name=attribute_value

cas.authn.attribute-repository.jdbc[0].attributes.user_name=username
cas.authn.attribute-repository.jdbc[0].attributes.role=role
cas.authn.attribute-repository.jdbc[0].attributes.group=group
cas.authn.attribute-repository.jdbc[0].attributes.inherited_group=inherited_group
cas.authn.attribute-repository.jdbc[0].attributes.user_id=user_id
cas.authn.attribute-repository.jdbc[0].attributes.crm_user_id=crm_user_id
cas.authn.attribute-repository.jdbc[0].attributes.organization_id=organization_id
cas.authn.attribute-repository.jdbc[0].attributes.first_name=first_name
cas.authn.attribute-repository.jdbc[0].attributes.middle_name=middle_name
cas.authn.attribute-repository.jdbc[0].attributes.last_name=last_name
cas.authn.attribute-repository.jdbc[0].attributes.email=email
cas.authn.attribute-repository.jdbc[0].attributes.work_phone=work_phone
cas.authn.attribute-repository.jdbc[0].attributes.phone_extension=phone_extension
cas.authn.attribute-repository.jdbc[0].attributes.active=active
cas.authn.attribute-repository.jdbc[0].attributes.userstatus=userstatus
cas.authn.attribute-repository.jdbc[0].attributes.accessMetadata=accessMetadata

cas.authn.attribute-repository.jdbc[0].id=AMS
cas.authn.attribute-repository.jdbc[0].failFastTimeout=1
cas.authn.attribute-repository.jdbc[0].healthQuery=select 1 from dual
cas.authn.attribute-repository.jdbc[0].isolateInternalQueries=false
cas.authn.attribute-repository.jdbc[0].leakThreshold=10
cas.authn.attribute-repository.jdbc[0].batchSize=1
cas.authn.attribute-repository.jdbc[0].defaultSchema=cihiweb
cas.authn.attribute-repository.jdbc[0].ddlAuto=none

cas.authn.attribute-repository.jdbc[0].autocommit=false
cas.authn.attribute-repository.jdbc[0].idleTimeout=5000

cas.authn.attribute-repository.jdbc[0].properties.propertyName=propertyValue
cas.authn.attribute-repository.jdbc[0].pool.suspension=false
cas.authn.attribute-repository.jdbc[0].pool.minSize=6
cas.authn.attribute-repository.jdbc[0].pool.maxSize=18
cas.authn.attribute-repository.jdbc[0].pool.maxWait=2000
cas.authn.attribute-repository.jdbc[0].pool.timeoutMillis=1000

cas.authn.attribute-repository.expirationTime=0
cas.authn.attribute-repository.merger=multivalued
cas.personDirectory.attributeResolutionEnabled=true
cas.personDirectory.activeAttributeRepositoryIds=AMS

However, none of the attributes are released in the service validation :

2020-11-16 16:15:41,642 DEBUG 
[org.apereo.cas.services.AbstractRegisteredServiceAttributeReleasePolicy] - 

Re: [cas-user] CAS 6.2.1 attribute release not working with PersonDirectory

[P N]

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 
# 
cas.authn.attribute-repository.jdbc[0].attributes.display-name=displayName  
...

However, even changing the configuration as suggested to old notation from 
CAS 5 - cas.authn.attributeRepository.jdbc[0] ... , I am getting same 
results, i.e. no attributes released.

Thanks,
Paul
On Monday, November 16, 2020 at 4:59:59 PM UTC-5 Ray Bon wrote:

> 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 system. Please be cautious with links and sensitive information. 
>
>
> 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:
>
>
> cas.authn.attribute-repository.default-attributes-to-release=username,role,group,inherited_group,user_id,crm_user_id,organization_id,first_name,middle_name,last_name,email,work_phone,phone_extension,active,userstatus,accessMetadata
> cas.authn.attribute-repository.jdbc[0].singleRow=false
> cas.authn.attribute-repository.jdbc[0].sql= ...
> cas.authn.attribute-repository.jdbc[0].username=user_name
>
> cas.authn.attribute-repository.jdbc[0].columnMappings.attribute_name=attribute_value
>
> cas.authn.attribute-repository.jdbc[0].attributes.user_name=username
> cas.authn.attribute-repository.jdbc[0].attributes.role=role
> cas.authn.attribute-repository.jdbc[0].attributes.group=group
>
> cas.authn.attribute-repository.jdbc[0].attributes.inherited_group=inherited_group
> cas.authn.attribute-repository.jdbc[0].attributes.user_id=user_id
> cas.authn.attribute-repository.jdbc[0].attributes.crm_user_id=crm_user_id
>
> cas.authn.attribute-repository.jdbc[0].attributes.organization_id=organization_id
> cas.authn.attribute-repository.jdbc[0].attributes.first_name=first_name
> cas.authn.attribute-repository.jdbc[0].attributes.middle_name=middle_name
> cas.authn.attribute-repository.jdbc[0].attributes.last_name=last_name
> cas.authn.attribute-repository.jdbc[0].attributes.email=email
> cas.authn.attribute-repository.jdbc[0].attributes.work_phone=work_phone
>
> cas.authn.attribute-repository.jdbc[0].attributes.phone_extension=phone_extension
> cas.authn.attribute-repository.jdbc[0].attributes.active=active
> cas.authn.attribute-repository.jdbc[0].attributes.userstatus=userstatus
>
> cas.authn.attribute-repository.jdbc[0].attributes.accessMetadata=accessMetadata
>
> cas.authn.attribute-repository.jdbc[0].id=AMS
> cas.authn.attribute-repository.jdbc[0].failFastTimeout=1
> cas.authn.attribute-repository.jdbc[0].healthQuery=select 1 from dual
> cas.authn.attribute-repository.jdbc[0].isolateInternalQueries=false
> cas.authn.attribute-repository.jdbc[0].leakThreshold=10
> cas.authn.attribute-repository.jdbc[0].batchSize=1
> cas.authn.attribute-repository.jdbc[0].defaultSchema=cihiweb
> cas.authn.attribute-repository.jdbc[0].ddlAuto=none
>
> cas.authn.attribute-repository.jdbc[0].autocommit=false
> cas.authn.attribute-repository.jdbc[0].idleTimeout=5000
>
>
> cas.authn.attribute-repository.jdbc[0].properties.propertyName=propertyValue
> cas.authn.attribute-repository.jdbc[0].pool.suspension=false
> cas.authn.attribute-repository.jdbc[0].pool.minSize=6
> cas.authn.attribute-repository.jdbc[0].pool.maxSize=18
> cas.authn.attribute-repository.jdbc[0].pool.maxWait=2000
> cas.authn.attribute-repository.jdbc[0].pool.timeoutMillis=1000
>
> cas.authn.attribute-repository.expirationTime=0
> cas.authn.attribute-repository.merger=multivalued
> cas.personDirectory.attributeResolutionEnabled=true
> cas.personDirectory.activeAttributeRepositoryIds=AMS
>
> However, none of the attributes are released in the service validation :
>
> 2020-11-16 16:15:41,642 DEBUG 
> [org.apereo.cas.services.AbstractRegisteredServiceAttributeReleasePolicy] - 
>  service [AbstractWebApplicationService(id=
> http://localhost:8080/ui-dev-guide/j_spring_cas_security_check, 
> originalUrl=http://localhost:8080/ui-dev-guide/j_spring_cas_security_check, 
> artifactId=null, principal=pnitat, source=service, loggedOutAlready=false, 
> format=XML, attributes={})] defined by registered service [http*://.*]...>
> 2020-11-16 16:15:41,643 DEBUG 
> [org.apereo.cas.services.AbstractRegisteredServiceAttributeReleasePolicy] - 
>  [DefaultPrincipalAttributesRepository()] to retrieve attributes>
> 2020-11-16 16:15:41,644 DEBUG 
> [org.apereo.cas.authentication.principal.DefaultPrincipalAttributesRepository]
>  
> -  

Re: [cas-user] CAS 6.2.1 attribute release not working with PersonDirectory

[Ray Bon]

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 
system. Please be cautious with links and sensitive information.

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:

cas.authn.attribute-repository.default-attributes-to-release=username,role,group,inherited_group,user_id,crm_user_id,organization_id,first_name,middle_name,last_name,email,work_phone,phone_extension,active,userstatus,accessMetadata
cas.authn.attribute-repository.jdbc[0].singleRow=false
cas.authn.attribute-repository.jdbc[0].sql= ...
cas.authn.attribute-repository.jdbc[0].username=user_name
cas.authn.attribute-repository.jdbc[0].columnMappings.attribute_name=attribute_value

cas.authn.attribute-repository.jdbc[0].attributes.user_name=username
cas.authn.attribute-repository.jdbc[0].attributes.role=role
cas.authn.attribute-repository.jdbc[0].attributes.group=group
cas.authn.attribute-repository.jdbc[0].attributes.inherited_group=inherited_group
cas.authn.attribute-repository.jdbc[0].attributes.user_id=user_id
cas.authn.attribute-repository.jdbc[0].attributes.crm_user_id=crm_user_id
cas.authn.attribute-repository.jdbc[0].attributes.organization_id=organization_id
cas.authn.attribute-repository.jdbc[0].attributes.first_name=first_name
cas.authn.attribute-repository.jdbc[0].attributes.middle_name=middle_name
cas.authn.attribute-repository.jdbc[0].attributes.last_name=last_name
cas.authn.attribute-repository.jdbc[0].attributes.email=email
cas.authn.attribute-repository.jdbc[0].attributes.work_phone=work_phone
cas.authn.attribute-repository.jdbc[0].attributes.phone_extension=phone_extension
cas.authn.attribute-repository.jdbc[0].attributes.active=active
cas.authn.attribute-repository.jdbc[0].attributes.userstatus=userstatus
cas.authn.attribute-repository.jdbc[0].attributes.accessMetadata=accessMetadata

cas.authn.attribute-repository.jdbc[0].id=AMS
cas.authn.attribute-repository.jdbc[0].failFastTimeout=1
cas.authn.attribute-repository.jdbc[0].healthQuery=select 1 from dual
cas.authn.attribute-repository.jdbc[0].isolateInternalQueries=false
cas.authn.attribute-repository.jdbc[0].leakThreshold=10
cas.authn.attribute-repository.jdbc[0].batchSize=1
cas.authn.attribute-repository.jdbc[0].defaultSchema=cihiweb
cas.authn.attribute-repository.jdbc[0].ddlAuto=none

cas.authn.attribute-repository.jdbc[0].autocommit=false
cas.authn.attribute-repository.jdbc[0].idleTimeout=5000

cas.authn.attribute-repository.jdbc[0].properties.propertyName=propertyValue
cas.authn.attribute-repository.jdbc[0].pool.suspension=false
cas.authn.attribute-repository.jdbc[0].pool.minSize=6
cas.authn.attribute-repository.jdbc[0].pool.maxSize=18
cas.authn.attribute-repository.jdbc[0].pool.maxWait=2000
cas.authn.attribute-repository.jdbc[0].pool.timeoutMillis=1000

cas.authn.attribute-repository.expirationTime=0
cas.authn.attribute-repository.merger=multivalued
cas.personDirectory.attributeResolutionEnabled=true
cas.personDirectory.activeAttributeRepositoryIds=AMS

However, none of the attributes are released in the service validation :

2020-11-16 16:15:41,642 DEBUG 
[org.apereo.cas.services.AbstractRegisteredServiceAttributeReleasePolicy] - 
http://localhost:8080/ui-dev-guide/j_spring_cas_security_check,
 originalUrl=http://localhost:8080/ui-dev-guide/j_spring_cas_security_check, 
artifactId=null, principal=pnitat, source=service, loggedOutAlready=false, 
format=XML, attributes={})] defined by registered service [http*://.*]...>
2020-11-16 16:15:41,643 DEBUG 
[org.apereo.cas.services.AbstractRegisteredServiceAttributeReleasePolicy] - 

2020-11-16 16:15:41,644 DEBUG 
[org.apereo.cas.authentication.principal.DefaultPrincipalAttributesRepository] 
- 
2020-11-16 16:15:41,644 DEBUG 
[org.apereo.cas.services.AbstractRegisteredServiceAttributeReleasePolicy] - 

2020-11-16 16:15:41,646 DEBUG 
[org.apereo.cas.services.AbstractRegisteredServiceAttributeReleasePolicy] - 

2020-11-16 16:15:41,646 DEBUG 
[org.apereo.cas.services.AbstractRegisteredServiceAttributeReleasePolicy] - 

2020-11-16 16:15:41,646 DEBUG 
[org.apereo.cas.services.AbstractRegisteredServiceAttributeReleasePolicy] - 

2020-11-16 16:15:41,647 DEBUG 
[org.apereo.cas.services.AbstractRegisteredServiceAttributeReleasePolicy] - 
http://localhost:8080/ui-dev-guide/j_spring_cas_security_check,
 originalUrl=http://localhost:8080/ui-dev-guide/j_spring_cas_security_check, 
artifactId=null, principal=pnitat, source=service, loggedOutAlready=false, 
format=XML, attributes={})] defined by registered service [http*://.*]...>
2020-11-16 16:15:41,647 DEBUG 

[cas-user] CAS 6.2.1 attribute release not working with PersonDirectory

[P N]

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:

cas.authn.attribute-repository.default-attributes-to-release=username,role,group,inherited_group,user_id,crm_user_id,organization_id,first_name,middle_name,last_name,email,work_phone,phone_extension,active,userstatus,accessMetadata
cas.authn.attribute-repository.jdbc[0].singleRow=false
cas.authn.attribute-repository.jdbc[0].sql= ...
cas.authn.attribute-repository.jdbc[0].username=user_name
cas.authn.attribute-repository.jdbc[0].columnMappings.attribute_name=attribute_value

cas.authn.attribute-repository.jdbc[0].attributes.user_name=username
cas.authn.attribute-repository.jdbc[0].attributes.role=role
cas.authn.attribute-repository.jdbc[0].attributes.group=group
cas.authn.attribute-repository.jdbc[0].attributes.inherited_group=inherited_group
cas.authn.attribute-repository.jdbc[0].attributes.user_id=user_id
cas.authn.attribute-repository.jdbc[0].attributes.crm_user_id=crm_user_id
cas.authn.attribute-repository.jdbc[0].attributes.organization_id=organization_id
cas.authn.attribute-repository.jdbc[0].attributes.first_name=first_name
cas.authn.attribute-repository.jdbc[0].attributes.middle_name=middle_name
cas.authn.attribute-repository.jdbc[0].attributes.last_name=last_name
cas.authn.attribute-repository.jdbc[0].attributes.email=email
cas.authn.attribute-repository.jdbc[0].attributes.work_phone=work_phone
cas.authn.attribute-repository.jdbc[0].attributes.phone_extension=phone_extension
cas.authn.attribute-repository.jdbc[0].attributes.active=active
cas.authn.attribute-repository.jdbc[0].attributes.userstatus=userstatus
cas.authn.attribute-repository.jdbc[0].attributes.accessMetadata=accessMetadata

cas.authn.attribute-repository.jdbc[0].id=AMS
cas.authn.attribute-repository.jdbc[0].failFastTimeout=1
cas.authn.attribute-repository.jdbc[0].healthQuery=select 1 from dual
cas.authn.attribute-repository.jdbc[0].isolateInternalQueries=false
cas.authn.attribute-repository.jdbc[0].leakThreshold=10
cas.authn.attribute-repository.jdbc[0].batchSize=1
cas.authn.attribute-repository.jdbc[0].defaultSchema=cihiweb
cas.authn.attribute-repository.jdbc[0].ddlAuto=none

cas.authn.attribute-repository.jdbc[0].autocommit=false
cas.authn.attribute-repository.jdbc[0].idleTimeout=5000

cas.authn.attribute-repository.jdbc[0].properties.propertyName=propertyValue
cas.authn.attribute-repository.jdbc[0].pool.suspension=false
cas.authn.attribute-repository.jdbc[0].pool.minSize=6
cas.authn.attribute-repository.jdbc[0].pool.maxSize=18
cas.authn.attribute-repository.jdbc[0].pool.maxWait=2000
cas.authn.attribute-repository.jdbc[0].pool.timeoutMillis=1000

cas.authn.attribute-repository.expirationTime=0
cas.authn.attribute-repository.merger=multivalued
cas.personDirectory.attributeResolutionEnabled=true
cas.personDirectory.activeAttributeRepositoryIds=AMS

However, none of the attributes are released in the service validation :

2020-11-16 16:15:41,642 DEBUG 
[org.apereo.cas.services.AbstractRegisteredServiceAttributeReleasePolicy] - 
http://localhost:8080/ui-dev-guide/j_spring_cas_security_check,
 
originalUrl=http://localhost:8080/ui-dev-guide/j_spring_cas_security_check, 
artifactId=null, principal=pnitat, source=service, loggedOutAlready=false, 
format=XML, attributes={})] defined by registered service [http*://.*]...>
2020-11-16 16:15:41,643 DEBUG 
[org.apereo.cas.services.AbstractRegisteredServiceAttributeReleasePolicy] - 

2020-11-16 16:15:41,644 DEBUG 
[org.apereo.cas.authentication.principal.DefaultPrincipalAttributesRepository] 
- 
2020-11-16 16:15:41,644 DEBUG 
[org.apereo.cas.services.AbstractRegisteredServiceAttributeReleasePolicy] - 

2020-11-16 16:15:41,646 DEBUG 
[org.apereo.cas.services.AbstractRegisteredServiceAttributeReleasePolicy] - 

2020-11-16 16:15:41,646 DEBUG 
[org.apereo.cas.services.AbstractRegisteredServiceAttributeReleasePolicy] - 

2020-11-16 16:15:41,646 DEBUG 
[org.apereo.cas.services.AbstractRegisteredServiceAttributeReleasePolicy] - 

2020-11-16 16:15:41,647 DEBUG 
[org.apereo.cas.services.AbstractRegisteredServiceAttributeReleasePolicy] - 
http://localhost:8080/ui-dev-guide/j_spring_cas_security_check,
 
originalUrl=http://localhost:8080/ui-dev-guide/j_spring_cas_security_check, 
artifactId=null, principal=pnitat, source=service, loggedOutAlready=false, 
format=XML, attributes={})] defined by registered service [http*://.*]...>
2020-11-16 16:15:41,647 DEBUG 
[org.apereo.cas.services.AbstractRegisteredServiceAttributeReleasePolicy] - 


Do I miss any configuration properties  or has anything changed in version 
6 from 5 regarding the default attributes release? 

Thanks,
Paul

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG

Re: [cas-user] CAS, config server and bootstrap outside war file

[Ray Bon]

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 
-Dspring.cloud.config.uri=https://user:password@config.local/casconfigserver;
export CATALINA_OPTS

bootstrap.yml (and some other config) gets deployed by jenkins and looks like

spring:
  cloud:
config:
  username: casuser
  password: Mellon

Ray

Note: do not hard code the username password in setenv.sh, tomcat writes 
CATALINA_OPTS to log on startup.

On Mon, 2020-11-16 at 17:09 +0100, Matthieu Marc wrote:
Notice: This message was sent from outside the University of Victoria email 
system. Please be cautious with links and sensitive information.

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 gradlew. The war file included the file and the service is 
starting as expected.

But, I manage my source file with git and I don't want to commit the 
bootstrap.properties file with content credentials used to connect to the 
spring config server. With my spring-boot2 application, I do not include this 
file in the jar file, put the file on my server in a directory called config, 
and launch the application with the following command :  java 
-Dloader.path="config" -jar myapp.jar

I tried to do so with CAS, but the bootstrap.properties file is not read as 
expected.

My question is how to make it working with the bootstrap.properties file 
outside the jar/war file ? Or are there others options/methods to not include 
spring config credential in bootstrap.properties commited on the git repository 
?

Thanks.


- - - -

CAS Version: 6.1.5
CAS Branch: 6.1.x
CAS Commit Id: ca6c71ae73f2418843a300165115a4c137649680
CAS Build Date/Time: 2020-02-29T00:51:20Z
Spring Boot Version: 2.2.0.RELEASE
Spring Version: 5.2.0.RELEASE
Java Home: /usr/lib/jvm/java-11-openjdk-amd64
Java Vendor: Ubuntu
Java Version: 11.0.9.1


--

Ray Bon
Programmer Analyst
Development Services, University Systems
2507218831 | CLE 019 | r...@uvic.ca

I respectfully acknowledge that my place of work is located within the 
ancestral, traditional and unceded territory of the Songhees, Esquimalt and 
WSÁNEĆ Nations.

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
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+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/e9f4034103d8f280700bfd9a08c1e65fd4c57b24.camel%40uvic.ca.

Re: [cas-user] Shibboleth and CAS

[Nathan Lewan]

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 added a comma at the end of the line... and it messed up the parsing, and 
that cascaded down the service setup from there.

so remember folks, commas are bad : )


On Monday, November 16, 2020 at 8:11:36 AM UTC-5 Nathan Lewan wrote:

> 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 Service Provider does NOT have reverse DNS set up, while 
> the other working SAML services in my CAS deployment do have reverse DNS. 
> But even in those cases my CAS server is not populating SubjectLocality, so 
> I'm guessing the other SP's aren't being as strict.
>
> i'll let you all know what I find.
>
> On Friday, November 13, 2020 at 10:54:38 PM UTC-5 cur...@newschool.edu 
> wrote:
>
>> It uses whatever the system has for DNS. But doing PTR records for 
>> address spaces you don't own in your own DNS is tricky; you may not be 
>> "fooling" it the way you think you are unless you're running your own faked 
>> root servers, etc.
>>
>> You might be able to do it with a local hosts file and nsswitch.conf...
>>
>> David A. Curry,  CISSP
>> Director • Information Security & Privacy
>> The New School • Information Technology
>> 71 Fifth Ave., 9th Fl., New York, NY 10003
>> +1 646 909-4728 <(646)%20909-4728> • david...@newschool.edu
>> Sent from my phone; please excuse typos and inane auto-corrections.
>> 
>>
>> On Fri, Nov 13, 2020, 21:42 Nathan Lewan  wrote:
>>
>>> ok, good to know, thanks. 
>>>
>>> i've been using that extension, as well as one on firefox. That's how i 
>>> was getting the SAML exchanges and saw the empty SubjectLocality
>>>
>>> May seem like a silly question, but i'm gonna just ask it: does CAS, the 
>>> application, require knowledge of DNS servers/network configurations in its 
>>> own configs, or does it piggy back off of the OS connections.
>>>
>>> Just trying to think of a reason that, given the reverse DNS entry is 
>>> there, CAS itself would not pick up on it, while the server host OS would.
>>>
>>> I'll keep you posted, and I appreciate the time you have given me on 
>>> this!
>>>
>>> On Friday, November 13, 2020 at 4:53:11 PM UTC-5 cur...@newschool.edu 
>>> wrote:
>>>

 Back when I was debugging this the last time, I ran a bunch of tests 
 against all the SAML SPs we have authenticating against our CAS servers 
 and 
 captured the SAML being exchanged, and in every case the SubjectLocality 
 element contained the IP address of the SP, not the CAS server.

 For example, when I log in to Workday:

 >>> SessionIndex="_9074398769568118801">
   

   
 
 urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport
   
 


 The 209.177.165.18 address belongs to Workday, not to us.

 You might want to grab the "SAML Chrome Panel" extension, which will 
 let you examine the entire SAML exchange between the SP and the IdP.

 --Dave


 --

 DAVID A. CURRY, CISSP
 *DIRECTOR • INFORMATION SECURITY & PRIVACY*
 THE NEW SCHOOL • INFORMATION TECHNOLOGY

 71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003
 +1 646 909-4728 <(646)%20909-4728> • david...@newschool.edu

 On Fri, Nov 13, 2020 at 3:01 PM Nathan Lewan  
 wrote:

> thanks everyone for the help so far.
> I did just do a restart of the service, and it would not populate that 
> field. I checks another service with a similar setup, and that also does 
> not have the subjectLocality populated, but that one works just fine.
>
>
>
>
> so here's the actual error i'm seeing:
> xmltooling::ValidationException at (https://[hostname]/SAML2/POST)
> SubjectLocality must have Address or DNSName. 
>
>
>
>
>
>
> Looking at the code for CAS, this appears to be the function to 
> populate the subjectLocality, but if i'm reading that right, it's trying 
> to 
> populate it with the CAS host address?
>
>
> protected SubjectLocality buildSubjectLocality(final Assertion 
> assertion, final RequestAbstractType authnRequest,
> final SamlRegisteredServiceServiceProviderMetadataFacade adaptor,
> final String binding) throws SamlException {
> val subjectLocality = SamlUtils.newSamlObject(SubjectLocality.class);
> *val hostAddress = 
> InetAddressUtils.getCasServerHostAddress(casProperties.getServer().getName());*
> val issuer = 

[cas-user] CAS, config server and bootstrap outside war file

[Matthieu Marc]

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 gradlew. The war file included the file and
the service is starting as expected.

But, I manage my source file with git and I don't want to commit the
bootstrap.properties file with content credentials used to connect to the
spring config server. With my spring-boot2 application, I do not include
this file in the jar file, put the file on my server in a directory called
config, and launch the application with the following command :  java
-Dloader.path="config" -jar myapp.jar

I tried to do so with CAS, but the bootstrap.properties file is not read as
expected.

My question is how to make it working with the bootstrap.properties file
outside the jar/war file ? Or are there others options/methods to not
include spring config credential in bootstrap.properties commited on the
git repository ?

Thanks.


- - - -

CAS Version: 6.1.5
CAS Branch: 6.1.x
CAS Commit Id: ca6c71ae73f2418843a300165115a4c137649680
CAS Build Date/Time: 2020-02-29T00:51:20Z
Spring Boot Version: 2.2.0.RELEASE
Spring Version: 5.2.0.RELEASE
Java Home: /usr/lib/jvm/java-11-openjdk-amd64
Java Vendor: Ubuntu
Java Version: 11.0.9.1

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
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+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/CADbxa2gXq%2BtjYM4kJSpLCvgT5iN46B0a8fE%3DjrVescp5yyu9Yg%40mail.gmail.com.

Re: [cas-user] pac4j error in cas management webapp

[Jérôme LELEU]

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 :

> 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 fact that added the dependency
> implementation 
> "org.apereo.cas:cas-server-support-json-service-registry:${project.'cas.version'}"
> in the build.gradle (same with git service registry implementation that I
> used initially).
>
> The *gradlew dependencies* results shows :
>
> runtimeClasspath - Runtime classpath of source set 'main'.
> \--- *org.apereo.cas:cas-server-support-json-service-registry:6.2.5*
>  +--- org.aspectj:aspectjrt:1.9.5
>  +--- org.aspectj:aspectjweaver:1.9.5
>  +--- javax.validation:validation-api:2.0.1.Final
>  +--- org.apereo.cas:cas-server-core-services:6.2.5
>  |+--- org.aspectj:aspectjrt:1.9.5
>  |+--- org.aspectj:aspectjweaver:1.9.5
>  |+--- javax.validation:validation-api:2.0.1.Final
>  |+--- org.apereo.cas:cas-server-core-services-api:6.2.5
>  ||+--- org.aspectj:aspectjrt:1.9.5
>  ||+--- org.aspectj:aspectjweaver:1.9.5
>  ||+--- javax.validation:validation-api:2.0.1.Final
>  ||+--- org.apereo.cas:cas-server-core-util-api:6.2.5
>  |||+--- org.aspectj:aspectjrt:1.9.5
>  |||+--- org.aspectj:aspectjweaver:1.9.5
>  |||+--- javax.validation:validation-api:2.0.1.Final
>  |||+--- org.bitbucket.b_c:jose4j:0.7.1
> * |||+--- org.pac4j:pac4j-config:4.1.0*
> * ||||\--- org.pac4j:pac4j-core:4.1.0*
> * |||+--- org.pac4j:pac4j-core:4.1.0*
> * |||+--- org.pac4j:pac4j-http:4.1.0*
> * ||||\--- org.pac4j:pac4j-core:4.1.0*
> * |||+--- org.pac4j:spring-webmvc-pac4j:4.0.1*
>
> If I set cas.version=6.2.3 in the gradle.properties of the cas-management
> overlay project, then the gradlew dependencies shows :
>
> runtimeClasspath - Runtime classpath of source set 'main'.
> \--- *org.apereo.cas:cas-server-support-json-service-registry:6.2.3*
>  +--- org.aspectj:aspectjrt:1.9.5
>  +--- org.aspectj:aspectjweaver:1.9.5
>  +--- javax.validation:validation-api:2.0.1.Final
>  +--- org.apereo.cas:cas-server-core-services:6.2.3
>  |+--- org.aspectj:aspectjrt:1.9.5
>  |+--- org.aspectj:aspectjweaver:1.9.5
>  |+--- javax.validation:validation-api:2.0.1.Final
>  |+--- org.apereo.cas:cas-server-core-services-api:6.2.3
>  ||+--- org.aspectj:aspectjrt:1.9.5
>  ||+--- org.aspectj:aspectjweaver:1.9.5
>  ||+--- javax.validation:validation-api:2.0.1.Final
>  ||+--- org.apereo.cas:cas-server-core-util-api:6.2.3
>  |||+--- org.aspectj:aspectjrt:1.9.5
>  |||+--- org.aspectj:aspectjweaver:1.9.5
>  |||+--- javax.validation:validation-api:2.0.1.Final
>  |||+--- org.bitbucket.b_c:jose4j:0.7.1
> * |||+--- org.pac4j:pac4j-config:4.0.3*
> * ||||\--- org.pac4j:pac4j-core:4.0.3*
> * |||+--- org.pac4j:pac4j-core:4.0.3*
> * |||+--- org.pac4j:pac4j-http:4.0.3*
> * ||||\--- org.pac4j:pac4j-core:4.0.3*
> * |||+--- org.pac4j:spring-webmvc-pac4j:4.0.1*
>
> and I can log into the cas-management, but the cas server version does not
> match and I don't know the potential consequences.
>
> CAS Management 6.2.3 seems to be fixing this pac4j dependency issue but I
> when I try to build it with the following gradle.properties :
>
> casmgmt.version=*6.2.3*
> cas.version=*6.2.5*
> springBootVersion=2.2.8.RELEASE
> appServer=-tomcat
> sourceCompatibility=11
> targetCompatibility=11
> gradleMavenPluginVersion=5.1.1
>
> I get the following error :
>
> Could not determine the dependencies of task ':extractCasBootWarOverlay'.
> > Could not resolve all files for configuration ':casBootWarOverlay'.
>> Could not resolve org.apereo.cas:cas-mgmt-webapp-tomcat:6.2.3.
>  Required by:
>  project :
>   > Could not resolve org.apereo.cas:cas-mgmt-webapp-tomcat:6.2.3.
>  > Could not get resource '
> https://oss.jfrog.org/artifactory/oss-snapshot-local/org/apereo/cas/cas-mgmt-webapp-tomcat/6.2.3/cas-mgmt-webapp-tomcat-6.2.3.pom
> '.
> > *Could not GET
> 'https://oss.jfrog.org/artifactory/oss-snapshot-local/org/apereo/cas/cas-mgmt-webapp-tomcat/6.2.3/cas-mgmt-webapp-tomcat-6.2.3.pom
> 

Re: [cas-user] Shibboleth and CAS

[Nathan Lewan]

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 Service Provider does NOT have reverse DNS set up, while 
the other working SAML services in my CAS deployment do have reverse DNS. 
But even in those cases my CAS server is not populating SubjectLocality, so 
I'm guessing the other SP's aren't being as strict.

i'll let you all know what I find.

On Friday, November 13, 2020 at 10:54:38 PM UTC-5 cur...@newschool.edu 
wrote:

> It uses whatever the system has for DNS. But doing PTR records for address 
> spaces you don't own in your own DNS is tricky; you may not be "fooling" it 
> the way you think you are unless you're running your own faked root 
> servers, etc.
>
> You might be able to do it with a local hosts file and nsswitch.conf...
>
> David A. Curry,  CISSP
> Director • Information Security & Privacy
> The New School • Information Technology
> 71 Fifth Ave., 9th Fl., New York, NY 10003
> +1 646 909-4728 <(646)%20909-4728> • david...@newschool.edu
> Sent from my phone; please excuse typos and inane auto-corrections.
> 
>
> On Fri, Nov 13, 2020, 21:42 Nathan Lewan  wrote:
>
>> ok, good to know, thanks. 
>>
>> i've been using that extension, as well as one on firefox. That's how i 
>> was getting the SAML exchanges and saw the empty SubjectLocality
>>
>> May seem like a silly question, but i'm gonna just ask it: does CAS, the 
>> application, require knowledge of DNS servers/network configurations in its 
>> own configs, or does it piggy back off of the OS connections.
>>
>> Just trying to think of a reason that, given the reverse DNS entry is 
>> there, CAS itself would not pick up on it, while the server host OS would.
>>
>> I'll keep you posted, and I appreciate the time you have given me on this!
>>
>> On Friday, November 13, 2020 at 4:53:11 PM UTC-5 cur...@newschool.edu 
>> wrote:
>>
>>>
>>> Back when I was debugging this the last time, I ran a bunch of tests 
>>> against all the SAML SPs we have authenticating against our CAS servers and 
>>> captured the SAML being exchanged, and in every case the SubjectLocality 
>>> element contained the IP address of the SP, not the CAS server.
>>>
>>> For example, when I log in to Workday:
>>>
>>> >> SessionIndex="_9074398769568118801">
>>>   
>>>
>>>   
>>> 
>>> urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport
>>>   
>>> 
>>>
>>>
>>> The 209.177.165.18 address belongs to Workday, not to us.
>>>
>>> You might want to grab the "SAML Chrome Panel" extension, which will let 
>>> you examine the entire SAML exchange between the SP and the IdP.
>>>
>>> --Dave
>>>
>>>
>>> --
>>>
>>> DAVID A. CURRY, CISSP
>>> *DIRECTOR • INFORMATION SECURITY & PRIVACY*
>>> THE NEW SCHOOL • INFORMATION TECHNOLOGY
>>>
>>> 71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003
>>> +1 646 909-4728 <(646)%20909-4728> • david...@newschool.edu
>>>
>>> On Fri, Nov 13, 2020 at 3:01 PM Nathan Lewan  wrote:
>>>
 thanks everyone for the help so far.
 I did just do a restart of the service, and it would not populate that 
 field. I checks another service with a similar setup, and that also does 
 not have the subjectLocality populated, but that one works just fine.




 so here's the actual error i'm seeing:
 xmltooling::ValidationException at (https://[hostname]/SAML2/POST)
 SubjectLocality must have Address or DNSName. 






 Looking at the code for CAS, this appears to be the function to 
 populate the subjectLocality, but if i'm reading that right, it's trying 
 to 
 populate it with the CAS host address?


 protected SubjectLocality buildSubjectLocality(final Assertion 
 assertion, final RequestAbstractType authnRequest,
 final SamlRegisteredServiceServiceProviderMetadataFacade adaptor,
 final String binding) throws SamlException {
 val subjectLocality = SamlUtils.newSamlObject(SubjectLocality.class);
 *val hostAddress = 
 InetAddressUtils.getCasServerHostAddress(casProperties.getServer().getName());*
 val issuer = SamlIdPUtils.getIssuerFromSamlObject(authnRequest);
 LOGGER.debug("Built subject locality address [{}] for the saml 
 authentication statement prepped for [{}]", hostAddress, issuer);
 *subjectLocality.setAddress(hostAddress);*
 return subjectLocality;
 } 

 is the subjectLocality supposed to be my address, or their address?


 On Friday, November 13, 2020 at 2:39:04 PM UTC-5 Mike Osterman wrote:

> Hi Nathan,
>
> I highly expect that #2 is why it's not yet working. Java, by default, 
> never lets go of a DNS resolution record until the application restarts. 
> You have to pass an argument at startup of your CAS application to 

Re: [cas-user] pac4j error in cas management webapp

[Frédéric Lohier]

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 fact that added the dependency 
implementation 
"org.apereo.cas:cas-server-support-json-service-registry:${project.'cas.version'}"
 
in the build.gradle (same with git service registry implementation that I 
used initially).

The *gradlew dependencies* results shows : 

runtimeClasspath - Runtime classpath of source set 'main'.
\--- *org.apereo.cas:cas-server-support-json-service-registry:6.2.5*
 +--- org.aspectj:aspectjrt:1.9.5
 +--- org.aspectj:aspectjweaver:1.9.5
 +--- javax.validation:validation-api:2.0.1.Final
 +--- org.apereo.cas:cas-server-core-services:6.2.5
 |+--- org.aspectj:aspectjrt:1.9.5
 |+--- org.aspectj:aspectjweaver:1.9.5
 |+--- javax.validation:validation-api:2.0.1.Final
 |+--- org.apereo.cas:cas-server-core-services-api:6.2.5
 ||+--- org.aspectj:aspectjrt:1.9.5
 ||+--- org.aspectj:aspectjweaver:1.9.5
 ||+--- javax.validation:validation-api:2.0.1.Final
 ||+--- org.apereo.cas:cas-server-core-util-api:6.2.5
 |||+--- org.aspectj:aspectjrt:1.9.5
 |||+--- org.aspectj:aspectjweaver:1.9.5
 |||+--- javax.validation:validation-api:2.0.1.Final
 |||+--- org.bitbucket.b_c:jose4j:0.7.1
* |||+--- org.pac4j:pac4j-config:4.1.0*
* ||||\--- org.pac4j:pac4j-core:4.1.0*
* |||+--- org.pac4j:pac4j-core:4.1.0*
* |||+--- org.pac4j:pac4j-http:4.1.0*
* ||||\--- org.pac4j:pac4j-core:4.1.0*
* |||+--- org.pac4j:spring-webmvc-pac4j:4.0.1*

If I set cas.version=6.2.3 in the gradle.properties of the cas-management 
overlay project, then the gradlew dependencies shows :

runtimeClasspath - Runtime classpath of source set 'main'.
\--- *org.apereo.cas:cas-server-support-json-service-registry:6.2.3*
 +--- org.aspectj:aspectjrt:1.9.5
 +--- org.aspectj:aspectjweaver:1.9.5
 +--- javax.validation:validation-api:2.0.1.Final
 +--- org.apereo.cas:cas-server-core-services:6.2.3
 |+--- org.aspectj:aspectjrt:1.9.5
 |+--- org.aspectj:aspectjweaver:1.9.5
 |+--- javax.validation:validation-api:2.0.1.Final
 |+--- org.apereo.cas:cas-server-core-services-api:6.2.3
 ||+--- org.aspectj:aspectjrt:1.9.5
 ||+--- org.aspectj:aspectjweaver:1.9.5
 ||+--- javax.validation:validation-api:2.0.1.Final
 ||+--- org.apereo.cas:cas-server-core-util-api:6.2.3
 |||+--- org.aspectj:aspectjrt:1.9.5
 |||+--- org.aspectj:aspectjweaver:1.9.5
 |||+--- javax.validation:validation-api:2.0.1.Final
 |||+--- org.bitbucket.b_c:jose4j:0.7.1
* |||+--- org.pac4j:pac4j-config:4.0.3*
* ||||\--- org.pac4j:pac4j-core:4.0.3*
* |||+--- org.pac4j:pac4j-core:4.0.3*
* |||+--- org.pac4j:pac4j-http:4.0.3*
* ||||\--- org.pac4j:pac4j-core:4.0.3*
* |||+--- org.pac4j:spring-webmvc-pac4j:4.0.1*

and I can log into the cas-management, but the cas server version does not 
match and I don't know the potential consequences. 

CAS Management 6.2.3 seems to be fixing this pac4j dependency issue but I 
when I try to build it with the following gradle.properties :

casmgmt.version=*6.2.3*
cas.version=*6.2.5*
springBootVersion=2.2.8.RELEASE
appServer=-tomcat
sourceCompatibility=11
targetCompatibility=11
gradleMavenPluginVersion=5.1.1

I get the following error : 

Could not determine the dependencies of task ':extractCasBootWarOverlay'.
> Could not resolve all files for configuration ':casBootWarOverlay'.
   > Could not resolve org.apereo.cas:cas-mgmt-webapp-tomcat:6.2.3.
 Required by:
 project :
  > Could not resolve org.apereo.cas:cas-mgmt-webapp-tomcat:6.2.3.
 > Could not get resource 
'https://oss.jfrog.org/artifactory/oss-snapshot-local/org/apereo/cas/cas-mgmt-webapp-tomcat/6.2.3/cas-mgmt-webapp-tomcat-6.2.3.pom'.
> *Could not GET 
'https://oss.jfrog.org/artifactory/oss-snapshot-local/org/apereo/cas/cas-mgmt-webapp-tomcat/6.2.3/cas-mgmt-webapp-tomcat-6.2.3.pom'.
 
Received status code 409 from server*

-Frederic

On Friday, November 13, 2020 at 5:32:17 PM UTC+1 leleuj wrote:

> Hi,
>
> Yes, I have an issue with the version 6.2.3 too, I can't download it.
>
> I just set up a Maven overlay based on the cas-mgmt-webapp v6.2.2, but I 
> only see pac4j-* v4.0.3 dependencies in the WEB-INF/lib.
>
> I don't know how you can get pac4j-core v4.1.0. Don't you have other 
> dependencies? What do you get with: *./gradlew allDependencies* in terms 
> of 

[cas-user] Cas consentReview

[Fotis Memis]

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: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
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+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/c5160428ca665ae33d2e0dde3faa33ca.squirrel%40webmail02.uoa.gr.