OpenSAML user discussion

[Asa Hardcastle <>]

I have figured it out.  Basically the saml assertion that I was given  
is not properly formed .. eg has the wrong case for elements and  
attributes.     So the bug is in the assertion, and in my  
understanding.  solved.

later,

asa

--
Asa Hardcastle, Technical Lead, openLiberty
Tel: +1.413.429.1044 Skype: subsystem7



On Jul 11, 2007, at 1:00 PM, Chad La Joie wrote:

> Asa, is the marshaller/unmarshaller part of some of the code you're  
> writing or are you seeing it the SAML code (i.e. my bug or yours ;))?
>
> Asa Hardcastle wrote:
> > I was on the wrong trail.   After further investigation, it turns  
> > out that the problem turns out to be case.
> > this gets unmarshalled:
> > <xyz:Assertion  ID="asdasdasdasdasdasd"
> > this does not:
> > <xyz:assertion  id="asdasdasdasdasdasd"
> > Is there a setting for ignore case?  (on both attributes and  
> > elements)
> > thanks,
> > asa
> > --
> > Asa Hardcastle, Technical Lead, openLiberty
> > Tel: +1.413.429.1044 Skype: subsystem7
> > On Jul 11, 2007, at 10:46 AM, Scott Cantor wrote:
> > > > How do I handle random namespace prefixes?  Like this for example:
> > >
> > > Define "handle". Our code doesn't change prefixes, it just tracks  
> > > them as
> > > best it can. It will probably add different prefixes if the  
> > > objects are
> > > modified or added to, but if it makes the XML non-well-formed,  
> > > there's a
> > > bug.
> > >
> > > That said, while our code is vastly more willing to actually try  
> > > and deal
> > > with stuff like this than the average library, whatever code is  
> > > producing
> > > that needs to be taken out and shot.
> > >
> > > -- Scott
>
> --
> Chad La Joie             2052-C Harris Bldg
> OIS-Middleware           202.687.0124