This interface is the SPI defined by WS-Security to enable WS-Trust/SecureConversation
specific security interactions.
This interface represents a Context containing information
populated and used by the Trust and the Security Enforcement Layers
(for example the proof-token of an Issued token needs to be used
by the SecurityEnforcement Layer to secure the message).
getAttachedSecurityTokenReference() If the token returned doesnt allow use of wsu:id attribute then a STR is returned as
which needs to be inserted into a for example.
getSecurityPolicy() get the SecurityPolicy to be applied for the request or response
to which this SecurityContext corresponds to
This allows the Client and/or the Service (WSP/STS) to dynamically inject
policy to be applied.
getUnAttachedSecurityTokenReference() If the token returned doesnt allow use of wsu:id attribute then a STR is returned as
which needs to be inserted into a for example.
If the token returned doesnt allow use of wsu:id attribute then a STR is returned as
which needs to be inserted into a for example.
STR if set, null otherwise
Get the Entropy if any provided by the other party, null otherwise
If the Entropy was specified as an then
this method would return the decrypted secret
get the SecurityPolicy to be applied for the request or response
to which this SecurityContext corresponds to
This allows the Client and/or the Service (WSP/STS) to dynamically inject
policy to be applied. For example in the case of SignChallenge when the
Initiator (client) has to sign a specific challenge.
Note: Inserting an un-solicited RSTR into a SOAP Header can also be expressed as
a policy and the subsequent requirement to sign the RSTR will also be expressed as
a policy
TODO: There is no policy today to insert a specific element to a SOAP Header, we
need to extend the policy definitions in XWS-Security.
Depending on the policy get the Token to be
used in Securing requests and/or responses. The token returned
is to be used only for inserting into the SecurityHeader, if the
getAssociatedProofToken is not null, and it should also be used for
securing the message if there is no Proof Token associated.
If the token returned doesnt allow use of wsu:id attribute then a STR is returned as
which needs to be inserted into a for example.
STR if set, null otherwise
Set the Entropy information provided by the other Part (if any)
WS-Trust allows requestor to provide input
to key material in the request.
The requestor might do this to satisfy itself as to the degree of
entropy(cyrptographic randomness) of atleast some of the material used to
generate the actual Key.
For composite Keys Entropy can be set by both parties, the concrete
entropy element can be a instance but the argument here is
generic to avoid a dependence of the SPI on WS-Trust packages