{"id":1699,"date":"2010-02-28T18:49:22","date_gmt":"2010-02-28T23:49:22","guid":{"rendered":"http:\/\/www.coresecuritypatterns.com\/blogs\/?p=1699"},"modified":"2020-08-08T04:20:54","modified_gmt":"2020-08-08T04:20:54","slug":"saml-attribute-exchange-for-x509-authentication-based-identity-federation","status":"publish","type":"post","link":"https:\/\/websecuritypatterns.com\/blogs\/2010\/02\/28\/saml-attribute-exchange-for-x509-authentication-based-identity-federation\/","title":{"rendered":"SAML Attribute Exchange for X.509 Authentication based Identity Federation"},"content":{"rendered":"

In a typical Single Sign-On (SSO)\/Federation scenario using SAML, the Service Provider (SP) initiates the user authentication request using SAML AuthnRequest<\/em><\/strong> assertion with an Identity Provider (IDP). The IDP authenticates the principal and returns a SAML AuthnStatement<\/strong> <\/em>assertion response confirming the user authentication. If the user is successfully authenticated, the SP is required to have the subject’s profile attributes of the authenticated principal for making local authorization decisions. To obtain the subject’s profile attributes (ex. organization, email, role), the SP initiates a SAML AttributeQuery<\/em><\/strong> request with the target IDP.  The IDP returns a response SAML AttributeStatement<\/em><\/strong> assertion listing the name of the attributes and the associated values.  Using the subject’s profile attributes, the SP can perform authorization operations.<\/p>\n

Ofcourse, it looks simple…here is the complexity – Last two weeks I spent on building a Proof-of-Concept that conforms to HSPD-12 Back-end Attribute Exchange specifications<\/a> and SAMLv2 Attribute Sharing Profile for X.509 Authentication based systems<\/a> (Both specifications are mandated as part of Federal Identity, Credential and Access Management (ICAM)<\/a> initiative of Federal CIO Council<\/a>).  I had been experimenting with an Identity Federation scenario that makes use of Smartcard\/PKI credentials – Card Authentication Key (CAK)\/X.509 Certificate on a PIV card authenticates a PKI provider (using OCSP) and then using its X.509 credential attributes (Subject DN) for looking up off-card user attributes from an IDP (that acts as an Attribute Authority). The IDP provides the user profile attribute information to the requesting SP. In simpler terms, the SP initiated X.509 authentication directly  via OCSP request\/response with a Certificate Validation Authority (VA) of a Certificate Authority (CA). Upon successful authentication, the SP  initiates a SAML AttributeQuery to the IDP (which acts as an Attribute Authority), the SAML AttributeQuery uses the SubjectDN<\/em> of the authenticated principal from the X.509 certificate and requests the IDP to provide the subject’s user profile attributes.<\/p>\n

Using Fedlet for SAML X.509 Authentication based Attribute Sharing<\/h3>\n
\"\"<\/a>

SAML Attribute Exchange for X.509 based Authentication<\/p><\/div>\n

Fedlet is a lightweight SAMLv2 based Service Provider (SP) implementation (currently part of Sun OpenSSO 8.x and sooner to be available in Oracle Identity Federation<\/a>) for enabling SAMLv2 based Single Sign-On environment. In simpler terms, Fedlet allows an Identity Provider (IDP) to enable an SP that need not have federation implemented. The SP plugs in the Fedlet to a Java\/.NET web application and then ready to initiate SAML v2 based SSO authentication, authorization and attribute exchanges.  A Fedlet installed and configured with a SP can set up to use multiple IDPs where select IDPs can acts as Attribute Authorities. In this case, the Fedlet need to update its configuration with the IDP Metadata configuration (such as entity ID, IDP Meta Alias, Attribute Authority Meta Alias – same as IDP ). In addition, the Fedlets are capable of performing XML signature verification and decryption of responses from the IDP must identify the alias of signing and encryption certificates.<\/p>\n

Here is the quick documentation,<\/a> which I referred  for putting together the solution using Fedlets for SAMLv2 Attribute Sharing for X.509 based authentication scenarios. In case, if you want your Service Provider to use OpenSSO for PIV\/CAC based certificate authentication, you may refer to my earlier entry on Smartcard\/PKI authentication based SSO (Using OpenSSO)<\/a>. Besides that you should be good to test-drive your excercise. Ofcourse, you can use Fedlets for Microsoft .NET service providers but it was’nt in my scope of work !<\/p>\n

In case of SP requiring to fetch multiple user profile attributes you may also choose to use SPML based queries (SPML Lookup\/Update\/Batch Request\/Response<\/a>) to an Identity Manager (acting as Attribute Authority) – assuming it facilitates an SPML implementation). If you are looking for a solution that requires user profile attributes after a single-user X.509 authentication, then SAML Attribute query should help fetching a single user profile of an authenticated principal !<\/p>\n

\ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"

In a typical Single Sign-On (SSO)\/Federation scenario using SAML, the Service Provider (SP) initiates the user authentication request using SAML AuthnRequest assertion with an Identity Provider (IDP). The IDP authenticates the principal and returns a SAML AuthnStatement assertion response confirming the user authentication. If the user is successfully authenticated, the SP is required to have the subject’s profile attributes of the authenticated… Read more »<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[4,5,6,8,9,11],"tags":[37,39,51,55,57,60,62,64,66,75],"class_list":["post-1699","post","type-post","status-publish","format-standard","hentry","category-compliance","category-identity-management","category-main","category-pki-main","category-security","category-smartcards-pki","tag-j2ee","tag-java","tag-opensso","tag-piv","tag-pki-main","tag-saml","tag-security","tag-smartcards","tag-spml","tag-ws-security"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/websecuritypatterns.com\/blogs\/wp-json\/wp\/v2\/posts\/1699","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/websecuritypatterns.com\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/websecuritypatterns.com\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/websecuritypatterns.com\/blogs\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/websecuritypatterns.com\/blogs\/wp-json\/wp\/v2\/comments?post=1699"}],"version-history":[{"count":2,"href":"https:\/\/websecuritypatterns.com\/blogs\/wp-json\/wp\/v2\/posts\/1699\/revisions"}],"predecessor-version":[{"id":2846,"href":"https:\/\/websecuritypatterns.com\/blogs\/wp-json\/wp\/v2\/posts\/1699\/revisions\/2846"}],"wp:attachment":[{"href":"https:\/\/websecuritypatterns.com\/blogs\/wp-json\/wp\/v2\/media?parent=1699"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/websecuritypatterns.com\/blogs\/wp-json\/wp\/v2\/categories?post=1699"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/websecuritypatterns.com\/blogs\/wp-json\/wp\/v2\/tags?post=1699"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}