InvestorsHub Logo
Followers 35
Posts 5775
Boards Moderated 0
Alias Born 07/22/2003

Re: awk post# 191524

Friday, 03/26/2010 12:28:56 PM

Friday, March 26, 2010 12:28:56 PM

Post# of 249238
Re: SAML:

As best I can determine, id.wave provides TPM-secured credentials in response to an SAML-based request from the relying party (ie. website), whereas the credentials released by non-id.wave identity providers are not TPM-secured. Apparently an id.wave identity assertion (still TPM-secured credentials like a non-SAML assertion) can be done in the SAML format in case the relying party uses SAML.

Id.wave is the only identity provider at the present time to secure credentials in the TPM (SAML assertions or other).

Thus a service provider relies on the identity provider to identify the principal. At the principal's request, the identity provider passes a SAML assertion to the service provider. On the basis of this assertion, the service provider makes an access control decision.

So, Wave is the identity provider passing the SAML assertion to the service provider (releasing the user's credentials for website access)...the credentials are hardware-secured in the TPM.

http://en.wikipedia.org/wiki/SAML

Join the InvestorsHub Community

Register for free to join our community of investors and share your ideas. You will also get access to streaming quotes, interactive charts, trades, portfolio, live options flow and more tools.