Skip to Content.
Sympa Menu

shibboleth-dev - Re: log4j...

Subject: Shibboleth Developers

List archive

Re: log4j...


Chronological Thread 
  • From: Walter Hoehn <>
  • To: Howard Gilbert <>
  • Cc: Shibboleth Developers <>, Nate Klingenstein <>
  • Subject: Re: log4j...
  • Date: Thu, 12 May 2005 13:08:26 -0500

The function of this configuration element has changed substantially. It now serves an ordered list of valid name mappings that are supported by the relying party. During SSO transactions the IdP determines the appropriate mapping to use by negotiating between what the SP would like to receive (as indicated by the metadata) and what the IdP can offer. In attribute queries, the IdP will reject queries that don't contain a name identifier format that is configured for the relying party.

-Walter



On May 12, 2005, at 8:29 AM, Howard Gilbert wrote:

- Encountered an error while parsing Shibboleth Identity Provider
configuration file: org.xml.sax.SAXParseException:
cvc-complex-type.2.4.a: Invalid content was found starting with element
'HSNameFormat'. One of '{"urn:mace:shibboleth:idp:config: 1.0":NameID}'
is expected.


Walter changed the syntax of the IdP configuration file changed over the
weekend. The element previously known as "HSNameFormat" in "RelyingParty"
has been changed to "NameID". Nothing changes but the tag. I changed my
conf/Idp.xml on Monday, but just a few minutes ago realized that I did not
check this change in. [I probably got interrupted by E-Mail when someone had
a bug.]




Archive powered by MHonArc 2.6.16.

Top of Page