mace-opensaml-users - RE: org.opensaml.MalformedException: Subject is invalid, requires either NameIdentifier or at least one ConfirmationMethod
Subject: OpenSAML user discussion
List archive
RE: org.opensaml.MalformedException: Subject is invalid, requires either NameIdentifier or at least one ConfirmationMethod
Chronological Thread
- From: "Scott Cantor" <>
- To: <>
- Subject: RE: org.opensaml.MalformedException: Subject is invalid, requires either NameIdentifier or at least one ConfirmationMethod
- Date: Thu, 30 Nov 2006 14:51:51 -0500
- Organization: The Ohio State University
> Unless I'm mistaken, it appears that _Element is an Assertion element,
> which gets fed into the SAMLAttributeStatement constructor. Of course
> we wouldn't expect that to work :-) If you turn on
> strict-dom-checking, I think you'll see if fail right off the bat,
> before it gets to checkValidity.
Ah, thanks Tom. I missed that because the earlier call to build the
Assertion looked ok to me and I didn't follow the rest of it.
-- Scott
- org.opensaml.MalformedException: Subject is invalid, requires either NameIdentifier or at least one ConfirmationMethod, rameshpsg, 11/30/2006
- RE: org.opensaml.MalformedException: Subject is invalid, requires either NameIdentifier or at least one ConfirmationMethod, Scott Cantor, 11/30/2006
- Re: org.opensaml.MalformedException: Subject is invalid, requires either NameIdentifier or at least one ConfirmationMethod, Tom Scavo, 11/30/2006
- RE: org.opensaml.MalformedException: Subject is invalid, requires either NameIdentifier or at least one ConfirmationMethod, Scott Cantor, 11/30/2006
- <Possible follow-up(s)>
- Re: org.opensaml.MalformedException: Subject is invalid, requires either NameIdentifier or at least one ConfirmationMethod, Ramesh Sundararajan, 11/30/2006
Archive powered by MHonArc 2.6.16.