When integrating the Shibboleth IDP and the Shibboleth SP, I would receive the following saml2 metadata issue
The system encountered an error at
To report this problem, please contact the site administrator at root@localhost.
Please include the following message in any email:
opensaml::saml2md::MetadataException at (http://HOSTNAME/secure/)
Unable to locate metadata for identity provider (https://HOSTNAME/idp/shibboleth)
A simple solution here, the mapping within the shibboleth2.xml file must point to the IDP. The issue here was that the Shibboleth IDP metadata was pointing correctly and the entity ID seemed to be correct
<MetadataProvider type="XML" file="C:\App\shibboleth\Metadata\idp-metadata.xml"/>
The specific issue here was that the entity ID within the shibboleth2.xml must match the entity ID within the idp-metadata.xml (Which it was) though the entityID is case sensitive so after matching up the entityID exactly, resolved the issue
About the authorDaniel is a Technical Manager with over 10 years of consulting expertise in the Identity and Access Management space.
Daniel has built from scratch this blog as well as technicalconfessions.com
Follow Daniel on twitter @nervouswiggles
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
During the reconcilation from OpenIDM to the ICF google apps connector, the following error response would occur. ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_grant
Received the JWT error
Unexpected character occurred when the IP addresses changes and the virtual instance was migrated into a separate network subnet.
When trying to connect, I would then receive the following error "Connect Error Result Code: 91 (Connect Error)"
When initiating the Tomcat instance, the cas-stderr log file will log a SEVERE error logging multiple times every few seconds
IDM ERROR - JDBC repository configured but datasource default was not found
org.forgerock.json.JsonException: org.forgerock.json.crypto.JsonCryptoException: javax.crypto.BadPaddingException: Given final block not properly padded