|
||||||||
|
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 |
||||||||
|
||||||||
|
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 |
||||||||
Please point me in the direction of how to apply this update without using the picketlink installer. Of the 12 packages that are dropped in place with picketlink-1.1.4.Final-installer, I believe I need two of them updated in order to make use of this update and get the entire response signed:
picketlink-common-2.5.3.Beta1.jar
picketlink-federation-2.5.3.Beta1.jar
I dropped these two .jar files in place with the rest of my installation, and then symlinked to them from:
/usr/share/jbossas/modules/system/layers/base/org/picketlink/main
I then edited the module.xml in that directory to include these two .jar files as resources. I believe this was in accordance with this doc:
https://community.jboss.org/wiki/HowToUpdateJBossAS7ToNewerVersionsOfPicketLink
Finally, I edited the picketlink.xml to include the Option Key inside the Handler (like the above comment, except without the SIGN_ASSERTION_ONLY).
The IdP runs and the SP can auth but the SAML response looks exactly as it did before I updated, and I'm not sure the entire thing is getting signed.
Please advise:
1) Are these the only two 2.5.3 .jar files that are needed in order to get the SIGN_RESPONSE_AND_ASSERTION to work?
2) Is the deployment method correct?
3) Is the configuration method correct?
4) How will I be able to tell from the SAML if the entire response is signed or not?