590 likes | 773 Views
Federated Identity Management. Dr Jens Jensen, STFC Contrail Summer School, Almere Summer(!) 2013. contrail is co-funded by the EC 7th Framework Programme under Grant Agreement nr. 257438 . 0 1. Principles. Federation. SP. SP. SP. SP. SP. IdP. User. IdP. IdP. IdP.
E N D
Federated Identity Management Dr Jens Jensen, STFC Contrail Summer School, Almere Summer(!) 2013 contrailis co-funded by the EC 7th Framework Programme under Grant Agreement nr. 257438 contrail-project.eu 01
Principles Federation SP SP SP SP SP IdP User IdP IdP IdP Discovery, Trust
Principles of Federated Identity Management • Identity is managed by “home” institute • User authenticates only to home institute • Password (or other secret) never leaves home institute • Potential for true SSO • Federation: multiple service providers • Normally, IdPs and SPs negotiate once – with the Federation • Instead of many-to-many negotiations • Federation policies • Common baseline for operations • Procedures for resolving incidents
Principles: A(uthentication), A(uthorisation), A(ccounting) I(nfrastructure) • Authentication • Make use of existing infrastructures • SSO whenever possible • Make use of existing code - pragmatic • Authorisation • Link to community rôles (users can be in more than one community) • Delegation… • Even if it’s identity delegation • Infrastructure • Like the grids, secure with IGTF+commercial • Accounting – what accounting? (UR-WG…)
Federated ID in Contrail – goals Make use of existing AAI Single Sign on to all of Contrail Support delegation Support all services by creating a certificate Provide own (internal) IdP supporting users with no other IdP Make use of external attributes Supplement with internal attributes Communicate attributes to resources
What is Single Sign-On (SSO) • Single account – user is registered once • And the account details are kept up to date • Single password – one password to rule them all • Can be modified (or reset) in a single location • Accepted by multiple service providers • Single login – only need to type password once • (Until it times out or something)
(Other) High Level Goals • Usable… users are often non-technical • Can’t manage X.509 certificates • Promote collaborations – interdisciplinary • Work with what communities already have • Unless it’s rubbish (maybe) • So need multi-LoA support • “The Facebook generation” • Modular – SOA (use of standards, web services) • Practical rather than perfect
External Requirements Scalable (10**7 users) Easy enough to use for “non-technical” users Support long tail researchers (aka homeless) Portal and command line login Mature, robust, performant Standards-based Work with existing practices (if pos.)
Shibboleth IdP AA WAYF User Web server
Shibboleth IdP AA WAYF User Web server
Shibboleth IdP AA WAYF User Web server
Shibboleth IdP AA WAYF User Web server
Shibboleth IdP AA WAYF User Web server
Attributes • Shibboleth uses eduPerson • E.g., CN, email, telephonenumber, … • Inconsistently published between federations • Attributes published, • Values of attributes • Supporting diverse communities – lowest baseline • Ought to have user-defined ARP… • In my opinion, ought to negotiate according to ARP
Shibboleth SAML2 National (educational/research) federations – WAYF Superfederations ... WAYF vs WFAYF ... the need to maintain the list of IdPs ... the need to maintain trust in IdPs (fed metadata)
<?xml version="1.0"?> <saml1p:Response xmlns:saml1p="urn:oasis:names:tc:SAML:1.0:protocol" xmlns="urn:oasis:names:tc:SAML:1.0:protocol" xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion" xmlns:samlp="urn:oasis:names:tc:SAML:1.0:protocol" xmlns:xsd="h ttp://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" InResponseTo="_4af1ff7443f2 9674d732a8a870de7225" IssueInstant="2011-01-18T13:05:58.183Z" MajorVersion="1" MinorVersion="1" ResponseID="_4b19a 8abc5b08687aa7c0644abe8e3fa"> <saml1p:Status> <saml1p:StatusCode Value="saml1p:Success"/> </saml1p:Status> <saml1:Assertion xmlns:saml1="urn:oasis:names:tc:SAML:1.0:assertion" AssertionID="_2e206ce17497f236534267bca235d deb" IssueInstant="2011-01-18T13:05:58.183Z" Issuer="https://idp01.stfc.ac.uk/shibboleth" MajorVersion="1" MinorVe rsion="1"> <saml1:Conditions NotBefore="2011-01-18T13:05:58.183Z" NotOnOrAfter="2011-01-18T13:10:58.183Z"> <saml1:AudienceRestrictionCondition> <saml1:Audience>https://cts.ngs.ac.uk/shibboleth-sp</saml1:Audience> </saml1:AudienceRestrictionCondition> </saml1:Conditions> <saml1:AttributeStatement> <saml1:Subject> <saml1:NameIdentifier Format="urn:mace:shibboleth:1.0:nameIdentifier">_84d5fc1bf7cdf55f01c475384035e7a8</s aml1:NameIdentifier> <saml1:SubjectConfirmation> <saml1:ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:sender-vouches</saml1:ConfirmationMethod> </saml1:SubjectConfirmation> </saml1:Subject> <saml1:Attribute AttributeName="urn:mace:dir:attribute-def:eduPersonScopedAffiliation" AttributeNamespace="u rn:mace:shibboleth:1.0:attributeNamespace:uri"> <saml1:AttributeValue Scope="stfc.ac.uk">STAFF</saml1:AttributeValue> </saml1:Attribute>
<saml1:Attribute AttributeName="urn:mace:dir:attribute-def:eduPersonTargetedID" AttributeNamespace="urn:mace :shibboleth:1.0:attributeNamespace:uri"> <saml1:AttributeValue Scope="stfc.ac.uk">iRhj7iQBkAdX0RNROmF8tZ2LRPo=</saml1:AttributeValue> </saml1:Attribute> <saml1:Attribute AttributeName="urn:oid:1.3.6.1.4.1.5923.1.1.1.10" AttributeNamespace="urn:mace:shibboleth:1 .0:attributeNamespace:uri"> <saml1:AttributeValue> <saml2:NameID xmlns:saml2="urn:oasis:names:tc:SAML:2.0:assertion" Format="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent" NameQualifier="https://idp01.stfc.ac.uk/shibboleth" SPNameQualifier="https://cts.ngs.ac.uk/shibboleth-sp">iRhj7iQBkAdU0RNROmF8tZ2LRPo=</saml2:NameID> </saml1:AttributeValue> </saml1:Attribute> </saml1:AttributeStatement> <ds:Signaturexmlns:ds="http://www.w3.org/2000/09/xmldsig#"> <ds:SignedInfo> <ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> <ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/> <ds:Reference URI="#_2e206ce17497f236534267bca235ddeb"> <ds:Transforms> <ds:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/> <ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"> <ec:InclusiveNamespacesxmlns:ec="http://www.w3.org/2001/10/xml-exc-c14n#" PrefixList="ds saml1 saml2"/> </ds:Transform> </ds:Transforms> <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/> <ds:DigestValue>3LnxpiimX52ooRFA3U19m6M222E=</ds:DigestValue> </ds:Reference> </ds:SignedInfo>
<ds:SignatureValue> dAocOTGz/SzwJDFgXUKkE5QASv7aDdZOtKQhqtbwreEFlb/73cVMgbcYf+/RTIVZyEAxUwnmAW3z e4n8mh+hgwHYjw11VHset/vk4E9PNDv5uLq1QlLpaO7oUDjYir4W1HPFeMv/27nrEqei0F9rBwn2 0SsRcJSGqnBhLm42XDPJlOkE24MLbirVJYG4q/un3CjdRe2WxOw4f/cSo91vVrUDMcaYBl2w+ekU fwysdECKGtHrbM4zlKZFxjdB/NvDLuzrouywb99SjzaFozP2PTjQ3vuZKB9DQjZ9feSLATXXREla 34qTRF2kbk+pQgQlFkAHlF/drb30oDRqJjDU0w== </ds:SignatureValue> <ds:KeyInfo> <ds:X509Data> <ds:X509Certificate>MIIEyjCCA7KgAwIBAgIRAK+p22GgJZ2vghQCYUoavLEwDQYJKoZIhvcNAQEFBQAwNjELMAkGA1UE BhMCTkwxDzANBgNVBAoTBlRFUkVOQTEWMBQGA1UEAxMNVEVSRU5BIFNTTCBDQTAeFw0xMDA1Mjgw ... blah blahblah... ZW5hLm9yZy9URVJFTkFTU0xDQS5jcnQwJgYIKwYBBQUHMAGGGmh0dHA6Ly9vY3NwLnRjcy50ZXJl bmEub3JnMCIGA1UdEQQbMBmCF3NoaWJib2xldGgwMS5zdGZjLmFjLnVrMA0GCSqGSIb3DQEBBQUA A4IBAQAE8B8pMfIaUbes+d9rNNWgOBxxBzsvU1kfp4RHt5ePYx8Sfz9I0Pb+2D7e6fZhil+WBv4E paiMK7J8k+UbmiWkNEALx4CGsdFWtwpoiHuADZN3EY6xxHM7enS/vlrHQRK2BPEihRCFtoAdrVYc J+/iSoeuNXrFZpWgsiwYWTh3/ZYvNDZE/uZ9Uhor7m9jEj4NjOkrHthX7r/UDVN4wFfGyPd7VTzT ls5xbg4s1Q6Z/2eKTYtSt86FDg5ebi02Yw2YwLXZqlk8p5ujoQzcpItOItEEN0Z0nZuZjGQbsNqd ctCGsvyDXXM0b9iI44OhCIk2SWb95Wf7ZsHHYUe8AjFX</ds:X509Certificate> </ds:X509Data> </ds:KeyInfo> </ds:Signature> </saml1:Assertion> </saml1p:Response>
Schemata • eduPerson – extension of inetOrgPerson • CN, SN, givenName, • eduPersonTargetedID (ePTID) • eduPersonPrincipalName (ePPN) • SCHAC – SChema for Academia • schacHomeOrganization, schacHomeOrganizationType • schacMotherTongue, schacCountryOfCitizenShip, schacCountryOfResidence • schacPersonalUniqueID, schacPersonalUniqueCode • Australian persistent identifier
OpenID 130.246.76.71 - - [25/Jul/2012:12:33:58 +0100] "GET /signin/openid_submit?janrain_nonce=2012-07-25T11%3A33%3A51Zsa4Iog&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&openid.mode=id_res&openid.op_endpoint=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fud&openid.response_nonce=2012-07-25T11%3A33%3A58ZVRUQt7xTangcpw&openid.return_to=https%3A%2F%2Fone-test.contrail.rl.ac.uk%2Fsignin%2Fopenid_submit%3Fjanrain_nonce%3D2012-07-25T11%253A33%253A51Zsa4Iog&openid.assoc_handle=AMlYA9VOguYX5ucZsKPMbKtwn5gM5dGud_BCRYzqZkqBEdwtz9GbplGv&openid.signed=op_endpoint%2Cclaimed_id%2Cidentity%2Creturn_to%2Cresponse_nonce%2Cassoc_handle&openid.sig=lhSjosRGBcAgxQlzMTzTegXfqpQ%3D&openid.identity=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid%3DAItOawkoR5eGsi1gq6j_dBTyG23TgLZ7WKThFLs&openid.claimed_id=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid%3DAItOawkoR5eGsi1gq6j_dBTyG23TgLZ7WKThFLs HTTP/1.1" 302 308 "https://accounts.google.com/o/openid2/auth?openid.assoc_handle=AMlYA9VOguVX5ucZsKPMbKtwn5gM5dGud_BCRYzqZkqBEdwtz9GbplGv&openid.claimed_id=http://specs.openid.net/auth/2.0/identifier_select&openid.identity=http://specs.openid.net/auth/2.0/identifier_select&openid.mode=checkid_setup&openid.ns=http://specs.openid.net/auth/2.0&openid.realm=https://one-test.contrail.rl.ac.uk&openid.return_to=https://one-test.contrail.rl.ac.uk/signin/openid_submit?janrain_nonce%3D2012-07-25T11%253A33%253A51Zsa4Iog" "Mozilla/5.0 (Windows NT 5.1) AppleWebKit/536.11 (KHTML, like Gecko) Chrome/20.0.1132.47 Safari/536.11" 130.246.76.71 - - [25/Jul/2012:12:33:58 +0100] "GET / HTTP/1.1" 302 276 "https://accounts.google.com/o/openid2/auth?openid.assoc_handle=AMlYA9VOguYX5ucZsKPMbKtwn5gM5dGud_BCRYzqZkqBEdwtz9GbplGv&openid.claimed_id=http://specs.openid.net/auth/2.0/identifier_select&openid.identity=http://specs.openid.net/auth/2.0/identifier_select&openid.mode=checkid_setup&openid.ns=http://specs.openid.net/auth/2.0&openid.realm=https://one-test.contrail.rl.ac.uk&openid.return_to=https://one-test.contrail.rl.ac.uk/signin/openid_submit?janrain_nonce%3D2012-07-25T11%253A33%253A51Zsa4Iog" "Mozilla/5.0 (Windows NT 5.1) AppleWebKit/536.11 (KHTML, like Gecko) Chrome/20.0.1132.47 Safari/536.11" 130.246.76.71 - - [25/Jul/2012:12:34:06 +0100] "GET /provider HTTP/1.1" 301 452 "https://accounts.google.com/o/openid2/auth?openid.assoc_handle=AMlYA9VOguYX5ucZsKPMbKtwn5gM5dGud_BCRYzqZkqBEdwtz9GbplGv&openid.claimed_id=http://specs.openid.net/auth/2.0/identifier_select&openid.identity=http://specs.openid.net/auth/2.0/identifier_select&openid.mode=checkid_setup&openid.ns=http://specs.openid.net/auth/2.0&openid.realm=https://one-test.contrail.rl.ac.uk&openid.return_to=https://one-test.contrail.rl.ac.uk/signin/openid_submit?janrain_nonce%3D2012-07-25T11%253A33%253A51Zsa4Iog" "Mozilla/5.0 (Windows NT 5.1) AppleWebKit/536.11 (KHTML, like Gecko) Chrome/20.0.1132.47 Safari/536.11" 130.246.76.71 - - [25/Jul/2012:12:34:06 +0100] "GET /provider/ HTTP/1.1" 200 1748 "https://accounts.google.com/o/openid2/auth?openid.assoc_handle=AMlYA9VOguYX5ucZsKPMbKtwn5gM5dGud_BCRYzqZkqBEdwtz9GbplGv&openid.claimed_id=http://specs.openid.net/auth/2.0/identifier_select&openid.identity=http://specs.openid.net/auth/2.0/identifier_select&openid.mode=checkid_setup&openid.ns=http://specs.openid.net/auth/2.0&openid.realm=https://one-test.contrail.rl.ac.uk&openid.return_to=https://one-test.contrail.rl.ac.uk/signin/openid_submit?janrain_nonce%3D2012-07-25T11%253A33%253A51Zsa4Iog" "Mozilla/5.0 (Windows NT 5.1) AppleWebKit/536.11 (KHTML, like Gecko) Chrome/20.0.1132.47 Safari/536.11"
OpenID 2.0 • They’re HTTP GET requests • Using HTTP redirects to connect to IdP • (Which will ask you for permission)
OpenID Request for authentication https://accounts.google.com/o/openid2/auth openid.assoc_handle=AMlYA9VOguYX5ucZsKPMbKtwn5gM5dGud_BCRYzqZkqBEdwtz9GbplGv openid.claimed_id=http://specs.openid.net/auth/2.0/identifier_select openid.identity=http://specs.openid.net/auth/2.0/identifier_select openid.mode=checkid_setup openid.ns=http://specs.openid.net/auth/2.0 openid.realm=https://one-test.contrail.rl.ac.uk openid.return_to=https://one-test.contrail.rl.ac.uk/signin/openid_submit janrain_nonce=2012-07-25T11%253A33%253A51Zsa4Iog
OpenID – Successful response GET /signin/openid_submit janrain_nonce=2012-07-25T11:33:51Zsa4Iog openid.ns=http://specs.openid.net/auth/2.0 openid.mode=id_res openid.op_endpoint=https://www.google.com/accounts/o8/ud openid.response_nonce=2012-07-25T11:33:58ZVRUQt7xTangcpw openid.return_to=https://one-test.contrail.rl.ac.uk/signin/openid_submit?janrain_nonce=2012-07-25T11%3A33%3A51Zsa4Iog openid.assoc_handle=AMlYA9VOguYX5ucZsKPMbKtwn5gM5dGud_BCRYzqZkqBEdwtz9GbplGv&openid.signed=op_endpoint,claimed_id,identity,return_to,response_nonce,assoc_handle openid.sig=lhSjosRGBcAgxQlzMTzTegXfqpQ= openid.identity=https://www.google.com/accounts/o8/id?id=AItOawkoR5eGsi1gq6j_dAUyG23TgLZ7HKThFLs openid.claimed_id=https://www.google.com/accounts/o8/id?id=AItOawkoR5eGsi1gq6j_dAUyG23TgLZ7HKThFLs
Portal view – the ePTID problem A. N. Other Portal IdP Contrail Portal Different identities with ePTID Home problem: identity changes if home IdP changes (ePPN) Persistent identifier (Australia, new eduPerson revision), Umbrella
Example of practical applications:GO Integration Globus Online Federation Portal MyProxy Could we use OAuth…? CILogon use OAuth version 1
The Contrail approach – high level view • Use external identity providers • Used by communities: OpenID, Shib • Delegation with OAuth2 • Internal SLCS: X.509 • Credential managed by portal, not user • Support command line access • Support delegation • (Has been done N times before: SWITCHAAI, MyProxy CA (SARoNGS, NCSA, …)) • Central federation database • Can be distributed, but is one DB • Handles attributes, too • Infrastructure – accept IGTF (like EGI, PRACE)
Contrail ConSec/Fed architecture Web AuzSvr/CA PIP Fed core SLAMF Federation layer Resource layer Prov’ingmgr SLAMP PEP VEP
OAuth2-in-a-slide Owner Access token Authorisation Server Client Authenticate, permit delegation Access token Resource
“Owner”, Client AuZsvr OAuth roles Web AuzSvr/CA Client, Resource PIP Fed core SLAMF Client Prov’ingmgr SLAMP PEP VEP
Authentication workflow CA WEB Fed API Core Contrail IdP AS External IdP
How does the Contrail WAYF (auth bridge) work? Google Yahoo AuzSvr IdP Bridge Umbrella Account creation LoA set Attribute update (eg email) WAYF DB IdP
Contrail WAYF vs Normal WAYF • Contrail WAYF handles multiple identity providers • Not just a single LoA… • So LoA needs to be set upon authentication • Contrail WAYF handles both OpenId and Shib (via SSPhp) • Normal WAYF belongs to a single federation • Compare the WFAYF… (demo: Terena TCS)
Authorisation and Access Control PEP Resource Federated Id • OK • X reject • + suspend PDP PIP DB Subscr. Federation core PAP Policies =attributes (SAML)
Community Authorisation “Standard XACML infrastructure” Use Case Fed. Infrastructure Resource/cloud Policy ctrl / adm Policies PEP PIP / attrs PDP Access
Standards SAML (OASIS) XACML (OASIS) X.509 (ITU-T) OAuth2 (IETF) HTTP (IETF) TLS (IETF) REST – not a standard, a principle
Experiences - Minor Issues • Certificates (deployment) • Need for browser-friendly certificates on browser-facing services • Need for trusted certificates on infrastructure hosts • LoA(release 1.4?) • Signing AUP (maintained as federation attribute) • Mobile access? • Supporting command line login • And iRODS command line access (tickets) • Portal integration HOWTO (documentation) • Registration with existing (Shib) feds (deployment) • Controlling the delegation – still needs user interaction • Preauthorise, authorise, or log
Making use of the ConSec • Time/effort/skills needed for integration • Hungry student algorithm? • Sustainability of components (SOA) • Use “standard” (open source) components when pos. • Maintain components • Replace components • Do without it • Pay someone to support it (or similar) • Live with the risk…
End to end demonstrator User goes to portal and logs in Redirect to authorisation server (AS), which notices user is not logged in (in this case) AS redirects user to AuC bridge AuC bridge asks user to select IdP and redirects Home IdPremembers if users authenticated earlier But the WAYF doesn’t…
End to end demonstrator When authentication returns, AuC bridge updates database and creates its own SAML identity assertion for the user, and returns to AS AS validates assertion, and sets up authorisation for the portal to access fed api (or whatever…!) Portal receives access token Portal generates key pair and obtains certificate (using Contrail API) Now “logged in” to all services Display overview of resources, etc.
End to end demonstrator User access resource (via portal) Resource extracts attribute assertion and passes to PDP PDP takes access control decision and returns to resource
Demo: Contrail login If there is time…
Contrail Fed Portal Architecture (1) Federation CLI Browser Federation Id Prov, Contrail CA Federation API (REST) Federation Web Int. Federation core Users db Federation of Cloud Providers Slide from Aleš Černivec, XLAB 43
Architecture (2) Federation CLI Browser Federation Id Prov, Contrail CA Federation API (REST) Federation Web Int. Federation core Users db Federation of Cloud Providers Slide from Aleš Černivec, XLAB 44
Example: File access via portal MyProxy Globus Online GridFTP(?) GridFTP iRODS Portal GridFTP(?) HTTP(S) GridFTP PRACE Browser EUDAT project: reusing Contrail federation code
Portal login – summary • ConSec manages login and attributes • Portal is delegatee (OAuth client) – can access resources using OAuth • Obtains certificate and SAML assertion • Communicate with more complex resources • More complex authorisation (XACML) • Uses certificate to act on behalf of user
The future…? • Moonshot – www.project-moonshot.org • Like eduRoam, but for higher level services • Carries attributes • Based on IETF standards • RADIUS • EAP • And OASIS • SAML • Has its own IETF working group (ABFAB-WG)
Wherefore art thou Moonshot • Moonshot is a technology project • Towards building actual federations • Towards meaningful and useful attributes • But giving users control of their privacy • Cf. new data protection directive
RADIUS-in-a-slide Attrs Add SAML assertion to respone Access (NAS) Server Server Local Local “Sup-plicant” EAP: extensible access protocol – tunnel Routing servers can see anonymised credentials E.g. “@stfc.ac.uk” instead of the tunnelled full identity
The Future (i.e., long term) • Managing identities – user perspective • Remembering passwords • Remembering usernames! • Where to log in • Service provider perspective • Accuracy of account information • Email addresses • Reuse of credentials • (R)evolution of technology, protocols, crypto, … • And keeping track of emerging protocols, standards, best practices, interoperation