You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Gregory Orciuch <g....@gmail.com> on 2015/10/05 21:22:23 UTC

Cannot consume SAML2 AttributeStatement in STSClient

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

Re: Cannot consume SAML2 AttributeStatement in STSClient

Posted by Colm O hEigeartaigh <co...@apache.org>.
What is the full stack trace? How are you consuming the assertion exactly?
The link you gave only refers to creating an Assertion and not consuming it.

Colm.

On Mon, Oct 5, 2015 at 8:22 PM, Gregory Orciuch <g....@gmail.com> wrote:

> 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
>



-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com