cas-management 6.1.x incommon certificate

114 views
Skip to first unread message

Ray Bon

unread,
Aug 21, 2020, 4:11:19 PM8/21/20
to cas-...@apereo.org
I am trying to run cas-management-overlay 6.1.7.

It is complaining because I do not have an incommon certificate:

2020-08-20 16:06:24,685 ERROR [org.springframework.boot.SpringApplication] - <Application run failed>
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'samlController' defined in class path resource [org/apereo/cas/mgmt/config/CasManagementSamlConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.apereo.cas.mgmt.SamlController]: Factory method 'samlController' threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'metadataAggregateResolver' defined in class path resource [org/apereo/cas/mgmt/config/CasManagementSamlConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.apereo.cas.mgmt.MetadataAggregateResolver]: Factory method 'metadataAggregateResolver' threw exception; nested exception is java.lang.NullPointerException

.
.
.

Caused by: java.lang.NullPointerException
        at org.apereo.cas.mgmt.InCommonMetadataAggregateResolver.<init>(InCommonMetadataAggregateResolver.java:54) ~[cas-mgmt-support-saml-6.1.7.jar:6.1.7]
        at org.apereo.cas.mgmt.config.CasManagementSamlConfiguration.metadataAggregateResolver(CasManagementSamlConfiguration.java:82) ~[cas-mgmt-config-saml-6.1.7.jar:6.1.7]

Why does cas-management insist on an incommon certificate?

How do I skip over this requirement?

Thanks


-- 
Ray Bon
Programmer Analyst
Development Services, University Systems

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.

Bryan Wooten

unread,
Aug 21, 2020, 4:24:43 PM8/21/20
to cas-...@apereo.org
First Ray, thanks to you and others that helped me with cas-management. I hope I can return the favor.

I deployed my first JSON file created by cas-management today. Success after some frustration. hehe.

I can't help with your issue, but why is an Incommon cert needed? Is your CAS also a SAML IDP?

Cheers,

-Bryan

University of Utah

--
- 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+u...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/62a1d976c9144e4c388c2191c4beef798dc76178.camel%40uvic.ca.

Ray Bon

unread,
Aug 21, 2020, 8:29:04 PM8/21/20
to cas-...@apereo.org
The null pointer  exception is the result of a changes that happened between 6.1.0-RC4 and 6.1.7. That is where [most of] saml was introduced.

That any incommon references are in the base properties and configuration files is an architectural defect, sigh. It is grossly presumptuous that incommon would be required to run cas-management.

I downloaded the incommon feed from, https://mdq.incommon.org/entities. Then grabbed the first certificate and put it in src/main/resources/incommon.pem.

It looks like this has solved the problem.

I certainly hope this is cleared up before I am ready to go to production.

Ray
Reply all
Reply to author
Forward
0 new messages