-
Notifications
You must be signed in to change notification settings - Fork 4
REQ#1 - ERROR - SP Metadata not being generated #90
Comments
Update after deploying latest code from https://github.com/dotCMS/plugin-com.dotcms.dotsaml/releases/tag/4.0-4.3.x-alpha2 I'm still not able to generate my SP metadata file, but the new log message is at least giving more detailed information about the cause of the NullPointerException: it seems to be related to the private key/public cert validation. I've tested several combinations for the values assigned to the public certificate, but I'm using the same command shared by @thstave on Saturday: openssl req -x509 -newkey rsa:4096 -sha256 -nodes -keyout saml.key -out sp.crt -days 3650
|
Issue persists. Error message is different, thoug:
When initializing the plugin at dotCMS startup:
|
Fixed by @jcastro-dotcms . Method org.slf4j.helpers.MessageFormatter.format in in conflict due to different definitions on:
To solve the issue we had to move slf4j-api-1.7.25.jar to /dotserver/tomcat-8.0.18/lib . The repackage code in dot.tika-app-1.3_3.jar cannot be modified at this point, but it will be removed on dotCMS 5.0. We need to pay attention to any other conflicts that this same method may generate for non-SAML related functionality. |
mv dotserver/tomcat-8.0.18/webapps/ROOT/WEB-INF/lib/slf4j-api-1.7.25.jar dotserver/tomcat-8.0.18/lib |
I'm getting the following errors when trying to generate the SP metadata file for a brand new SAML Config:
The text was updated successfully, but these errors were encountered: