[
https://issues.jboss.org/browse/WFLY-3140?page=com.atlassian.jira.plugin....
]
Pedro Igor commented on WFLY-3140:
----------------------------------
Hi Tom,
WildFly 8.0.0.Final is shipped with PicketLink 2.5.2.Final version. This version is
not fully integrated with Undertow, so you won't be able to use the federation
features. Beside that, Undertow 1.0.0.Final has an issue that is a blocker to get PL fully
functional.
PicketLink SAML is working in WildFly 8.0.1 (upstream) when using PicketLink
2.6.0.CR1, which provides all the necessary integration to Undertow.
Please take a look at this workspace [1], which I'm working to get as much tests
scenarios as possible for PicketLink Federation. Currently, this workspace is using EAP
6.3 and WildFly 8.0.1 during the tests.
[1]
https://github.com/pedroigor/picketlink-tests
Regards.
Pedro Igor
simply picketlink setup of an sp+idp delivers a 403
---------------------------------------------------
Key: WFLY-3140
URL:
https://issues.jboss.org/browse/WFLY-3140
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Security
Affects Versions: 8.0.0.Final
Reporter: Tom Fonteyne
Assignee: Pedro Igor
Priority: Critical
Attachments: plhello.war, plidp.war
A simple picket links setup of an sp and an idp. Accessing the sp, simply delivers
"403 - Forbidden"
The same security domains and the identical sp/idp war deployed on EAP 6.1.1 work fine
--
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