Validating parser saml
When a principal is acting directly on its own behalf, for example, neither delegation nor impersonation are in play.They are, however, the more common semantics operating for token exchange and, as such, are given more direct treatment in this specification.Examples of security tokens include JSON Web Tokens (JWTs) [JWT] and SAML Assertions [OASIS.saml-core-2.0-os].Security tokens are typically signed to achieve integrity and sometimes also encrypted to achieve confidentiality.A new grant type for a token exchange request and the associated specific parameters for such a request to the token endpoint are defined by this specification.A token exchange response is a normal OAuth 2.0 response from the token endpoint with a few additional parameters defined herein to provide information to the client.You can subscribe to plugin releases via RSS (or here) or via Twitter.
Although a few new JWT claims are defined that enable delegation semantics to be expressed, the specific syntax, semantics and security characteristics of the tokens themselves (both those presented to the AS and those obtained by the client) are explicitly out of scope and no requirements are placed on the trust model in which an implementation might be deployed.
The OAuth 2.0 Authorization Framework have emerged as popular standards for authorizing and securing access to HTTP and RESTful resources but do not provide everything necessary to facilitate token exchange interactions.
This specification defines a lightweight protocol extending OAuth 2.0 that enables clients to request and obtain security tokens from authorization servers acting in the role of an STS.
Web Service clients have used WS-Trust as the protocol to interact with an STS for token exchange, however WS-Trust is a fairly heavyweight protocol, which uses XML, SOAP, etc.
Whereas, the trend in modern Web development has been towards lightweight services utilizing RESTful patterns and JSON.