Loading...

XML

Word

Printable

Type: Bug
Resolution: Obsolete
Priority: Major
Fix Version/s: TBD EAP 5
Affects Version/s: EAP_EWP 5.1.2
Component/s: Security
Labels:
None

Affects:

Release Notes
Release Note Text:

Hide
Draft: When customer is using PicketLink, uncomment following section in $JBOSS_HOME/server/<profile>/deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml.



Show
Draft: When customer is using PicketLink, uncomment following section in $JBOSS_HOME/server/<profile>/deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml.
Release Note Status:
Needs More Info
Docs QE Status:
NEW

Within the default EAP configuration the following JBoss Web authenticator is defined: -

<entry>
<key>SECURITY_DOMAIN</key>
<value>org.picketlink.identity.federation.bindings.tomcat.PicketLinkAuthenticator</value>
</entry>

During the initialisation of JBoss Web all defined authentictors are loaded, should this fail then the entire list of defined authenticators is dropped and the defaults used instead.

The side effect of this is that if any custom authenticator is added for a different purpose this default but missing authenticator causes the correct authenticators to be dropped.

is related to

JBPAPP-9741 NoClassDeffFound Error: PicketLinkAuthenticator

Closed

relates to

JBAS-5585 Fix tomcat federation tests

Closed

Assignee:: Peter Skopek

Reporter:: Darran Lofthouse

Writer:: Russell Dickenson (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Created:: 2012/07/20 1:01 PM

Updated:: 2019/05/21 4:49 AM

Resolved:: 2019/05/21 4:49 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates

Hide