I think you're not being able to get this done because you're updating the module as it was using 2.1.
There is no specific log entries when using the signing options. You can use a Firefox plugin called SAML Tracer to trace messages and check if they're being signed properly.
Btw, you can get 2.5.3.Beta1 binaries from the installer, which is available from this link:
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Hi Danny,
JBoss EAP uses PicketLink 2.1, which differs a bit how the module is updated when using 2.5.
To properly update the module, please follow these steps:
1) Copy picketlink-config-2.5.3.Beta1.jar to org/picketlink/main
2) Copy picketlink-common-2.5.3.Beta1.jar to org/picketlink/main
3) Copy picketlink-federation-2.5.3.Beta1-
PLINK-313.jar to org/picketlink/main (which I've attached)4) Copy picketlink-jbas7-2.5.3.Beta1.jar to org/picketlink/main
5) Update module.xml as follows:
I think you're not being able to get this done because you're updating the module as it was using 2.1.
There is no specific log entries when using the signing options. You can use a Firefox plugin called SAML Tracer to trace messages and check if they're being signed properly.
Btw, you can get 2.5.3.Beta1 binaries from the installer, which is available from this link:
http://www.picketlink.org/getstarted.html