OpenSAML user discussion

[Chad La Joie <>]

The OpenSAML object providers are modeled after the schema.  So, in the
case, for example, of an AuthenStatement, in the schema it extends
StatementAbstractType.  In the code then AuthenStatement extends
Statement (which models StatementAbstractType).

Your XACML classes should do the same.

Note, that you don't get
<saml:Statement xsi:type="xacml-saml:XACMLAuthzDecisionStatementType">

You get:
<XACMLAuthzDecisionStatement ..... />

Assertions, in the code, are set up to properly handle new statement
types already, as well.

When you're implementing this I would strongly suggest that you look at
the SAML schema and the SAML objects in the code.  See how the schema is
translated into the object, see how the object providers are
implemented, how they are configured, etc.  In this case pay particular
attention to the various SAML statement types (AuthnStatement,
AttributeStatement, etc.)


 wrote:
> Hi, 
> 
> Thanks Chad, you were right, it was my mistake. I had registered my object 
> but not in the good file.
> 
> Now I would like to know if this object have to be an "extends" of 
> statement or just a SAMLObject. Because I don't see very well how I can 
> obtain this :
> <saml:Statement xsi:type="xacml-saml:XACMLAuthzDecisionStatementType">
> and particularly how I can get the "xsi-type" and the relation with the new 
> object. 
> 
> Do I have to modify the statement file to add the attribute 
> XACMLAuthzDecisionStatement?
> 
> I thank you in advance for your reply.
> 
> Yours faithfully,
> 
> Raynal Sylvain

-- 
Chad La Joie             2052-C Harris Bldg
OIS-Middleware           202.687.0124