|
||||||||
|
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 |
||||||||
It worked! Thanks for the help!
The solution above would have worked with picketlink version 2.1.6 that comes with JBoss EAP 6.1.0.Alpha1 (AS 7.2.0.Alpha1-redhat-4) (when applied to picketlink/main/module.xml). I upgraded to Picketlink 2.5.2.Final using the picketlink-installer. The dependencies have now been broken out into federation and federation.bindings, so I had to make the update above in the following 2 files:
modules\system\layers\base\org\picketlink\federation\main\module.xml
modules\system\layers\base\org\picketlink\federation\bindings\main\module.xml
I posted this work-a-around at https://community.jboss.org/thread/234107
Others will have this issue unless a fix made. I'm thinking this issue needs to be fixed in the picklink-installer and not in picketlink. Anyone know how to assign this ticket to the appropriate place/person?