MAA Use Case SAML

From MemberWiki

This is a common use case scenario in several enterprise deployments of mashups where the token being passed to the gadget server is a SAML identity assertion which is verified by the gadget server before supplying the gadget. In a typical use case the flow is as follows:

   b1: User authenticates to mashup server, loads mashup page 
   b2: mashup page opens iframe: points to a server which issues SAML idenity assertion token and redirects to gadget server 
   b3: gadget server verifies SAML token and serves gadget 

TBD: Detailed flow diagrams.

We have this requirement typically from enterprises which have a federation story in place and its typically based on SAML