No generated SAML metadata after migration

[Mohamed Amdouni]

Hello,

I'm migrating the cas from 5.X to 6.6.12

So I created a new template from Cas Initializer and try to apply the properties i cas.properties.

Actually the server is started with the Ready message.

The authentication with an ldap user is OK.

But when testing cas as a SAML Idp, I have some issues:

1- The metadata of the IDP is not generated with the message : <Attempting to generate/fetch SAML Idp metadata....>

<Generated SAML Idp metadata document is [null]>

I configured the properties :

cas.authn.saml-idp.core.entity-id (this property has moved to core package)

cas.authn.saml-idp.metadata.file-system.location=/d:/mydir/etc/cas/saml

I notice that when activating the TRACE log, I see an exception about on RandomUtils : NativePRNGNonBlocking SecureRandom not available. I think it's related to Windows machine. I'm testin on local machine before deploying.

Is it related to the problem of generating the Idp metadata.

I tried to place the old version metadata without success : the url /cas/saml/metadata does not generate the metadata with a nullpointerException @ SamlIdpmetadataController 61.

Any idea?

Thanks.

  

[Mohamed Amdouni]

Hi,

Update : when requesting the /idp/metadata I get a null pointer exception because the registered service is null.

I checked the required properties for saml like entity id etc and they are all specified …

Thank you in advance 

[Mohamed Amdouni]

Hello, 

When removing the saml-idp-metadata-jpa from the dendencies I’m able to generate the idp metadata from the endpoint /idp/metadata and files are generated on startup (idp metadata and certs ) in the folder /cas/saml.

Is it wrong to keep both idp-metadat and idp-metadata-jpa ? As I understand  Jpa is used for per service metadata which is not the case for me. My cas server is acting as a saml idp. The dependencies was already present in the old version 5.3

Thank you for your help.

Best regards.

[Ray Bon]

Mohamed,

jpa is an alternative to file system storage (default). Services can use the file system as well.

If you do not need/use it, remove it.

Ray

On Thu, 2023-11-02 at 18:24 +0100, Mohamed Amdouni wrote:

Notice: This message was sent from outside the University of Victoria email system. Please be cautious with links and sensitive information.

[Mohamed Amdouni]

Thank you Ray for your response.

In previous versions the two dependencies are present. So I would like to keep the top options if possible.

I think there is a problem getting the service locator or and the generator bean when the two dependencies are presents 

When keeping only jpa, do you know where to find the default idp saml metadata.

Best regards 

--
- 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/f1a36e5936f28544d4da78de89024917efd86705.camel%40uvic.ca.

[Ray Bon]

Mohamed,

I have not used JPA for any cas config. 

The metadata should be in some table in the datastore. see https://apereo.github.io/cas/6.6.x/installation/Configuring-SAML2-DynamicMetadata-JPA.html

Ray