OpenSAML user discussion

[Brent Putman <>]

Well, those are Java 5 generics parameters.  How you parameterize for
instantiation depends on the SAML protocol and profile you're
implementing.  You can see examples of how these message contexts get
used in an IdP in the profile handlers in the Shibboleth 2.x IdP:

http://svn.middleware.georgetown.edu/view/java-idp/branches/REL_2/src/main/java/edu/internet2/middleware/shibboleth/idp/profile/

In that code usually there is actually a specific concrete subclass of
that the SAML message context which locks those types down for a
particular protocol/profile, but you don't strictly speaking have to do
it that way.

For an SP the inbound/outbound types are typically going to be reversed
from those of the IdP, obviously, e.g. outbound might be AuthnRequest or
AttributeQuery, inbound would be Response.

The name identifier type is going to vary based on the version of SAML,
e.g. NameIdentifer for SAML 1, NameID for SAML 2.



Bailo, John wrote:
> I'm having trouble discovering the canonical way of instantiating the
> BasicSAMLMessageContext.   What are the associated Types for:
>
> InboundMessageType
> OutboundMessageType
> NameIdentifierType
>
> So I can complete:
>
> messageContext = new BasicSAMLMessageContext<Object, Object, Object>();
>
>
> CONFIDENTIALITY NOTICE: The information in this Internet email is 
> confidential and may be legally privileged. It is intended solely for the 
> addressee. Access to this email by anyone else is unauthorized. 
>
>