[ https://issues.jboss.org/browse/WFLY-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974256#comment-12974256 ]
Pedro Igor edited comment on WFLY-3140 at 6/6/14 12:56 PM:
-----------------------------------------------------------
The SP configuration for WildFly is a bit different. The LM class is different than EAP.
{code}
<security-domain name="sp" cache-type="default">
<authentication>
<login-module code="org.picketlink.identity.federation.bindings.wildfly.SAML2LoginModule" flag="required"/>
</authentication>
</security-domain>
{code}
We've also updated the documentation of quickstarts to highlight this difference.
https://github.com/jboss-developer/jboss-picketlink-quickstarts/tree/master/picketlink-federation-saml-sp-post-with-signature#create-the-security-domain-for-wildfly
was (Author: pcraveiro):
The SP configuration for WildFly is a bit different. The LM class is different than EAP.
{code}
<security-domain name="sp" cache-type="default">
<authentication>
<login-module code="org.picketlink.identity.federation.bindings.wildfly.SAML2LoginModule" flag="required"/>
</authentication>
</security-domain>
{code}
> 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
> Fix For: No Release
>
> 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 was sent by Atlassian JIRA
(v6.2.3#6260)