Hi

I struggle with consuming AttributeStatement which was produced by .NET
software
Trying to consume that with cxf 3.1.3

Example:
<AttributeStatement>
              <Attribute Name="bla1r"
NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic">
                <AttributeValue>12345678</AttributeValue>
              </Attribute>
              <Attribute Name="bla2"
NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic">
                <AttributeValue>3</AttributeValue>
              </Attribute>
              <Attribute Name=bla3r"
NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic">
                <AttributeValue>SAML-2.0</AttributeValue>
              </Attribute>
              <Attribute Name="bla4"
NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic">
                <AttributeValue>1.0</AttributeValue>
              </Attribute>
            </AttributeStatement>

I suppose because it does not specify the value type.
Though cxf complains:

java.lang.ClassCastException: org.opensaml.xml.schema.impl.XSAnyBuilder
cannot be cast to org.opensaml.core.xml.XMLObjectBuilder
at
org.opensaml.core.xml.config.XMLConfigurator.initializeObjectProviders(XMLConfigurator.java:238)

Stepped into this one
http://stackoverflow.com/questions/28724098/saml2-xml-structured-attribute-values
However I'm not able to understand Colm's conclusion about usage the
AttributeBean.

Can anyone share sample usage which can fit the attribute you see above ?
or maybe this is solvable in different way ?

Thanks in advance,
Gregory Orciuch

Reply via email to