[External] Re: Question on supportsForcedAuthentication

[Brewer, Edward L]

Scott,

Update:  Works in my Tomcat 2.4.0 IdP... Does not work in my JBOSS 2.3.6 IdP

Lee

-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Brewer, Edward L
Sent: Wednesday, July 23, 2014 11:01 AM
To: Shib Users
Subject: RE: [External] Re: Question on supportsForcedAuthentication 

Scott,

Sorry... This instance is actually running on JBOSS 5.  I am currently upgrading and moving to 2.4.0 on Tomcat.  I will check my new Tomcat 2.4.0 instance as well.

Lee

-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Wednesday, July 23, 2014 10:47 AM
To: Shib Users
Subject: [External] Re: Question on supportsForcedAuthentication 

On 7/23/14, 10:58 AM, "Brewer, Edward L" <lee.brewer at Vanderbilt.Edu> wrote:

> 
>I am currently using a shibboleth 2.3.6 IdP on Tomcat which has being 
>working fine up to the point of my last change.  I am attempting to 
>configure supportsForcedAuthentication=true on my external auth login 
>handler and I get the following error
> 
>09:51:43.895 - ERROR
>[edu.internet2.middleware.shibboleth.common.config.BaseService:188] - 
>Configuration was not loaded for shibboleth.HandlerManager service, 
>error creating components.  The root cause of this error was:
>org.xml.sax.SAXParseException:
> cvc-complex-type.3.2.2: Attribute 'supportsForcedAuthentication' is 
>not allowed to appear in element 'ph:LoginHandler'.

That's pretty strange. Any chance you don't have Xerces/Xalan endorsed?

But I guess the official answer would be to reproduce that on 2.4.0, because it's basically inexplicable. Particularly if the External handler is loading/working without the attribute.

-- Scott

--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net