57
1 Multi Cloud Navid Pustchi April 25, 2014 [email protected] World-Leading Research with Real-World Impact!

Multi Cloud Navid Pustchi April 25, 2014 [email protected]

  • Upload
    torin

  • View
    44

  • Download
    0

Embed Size (px)

DESCRIPTION

Multi Cloud Navid Pustchi April 25, 2014 [email protected]. World-Leading Research with Real-World Impact!. User seamlessly or by choice can use services from another cloud. The user belongs to one CSP. Each cloud has independent administration(different). . Motivation. User. CSP B. - PowerPoint PPT Presentation

Citation preview

Page 1: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

1

Multi Cloud

Navid Pustchi

April 25, 2014

[email protected]

World-Leading Research with Real-World Impact!

Page 2: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

User seamlessly or by choice can use services from another cloud.

The user belongs to one CSP.

Each cloud has independent administration(different).

2World-Leading Research with Real-World Impact!

Motivation

AWSOpenstack

CSP A CSP BUser

Page 3: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

Federation Deployment of multiple CSPs (heterogeneous or

homogenous) to provide complex services.

Based on deployment Hybrid Cloud Community Cloud

3World-Leading Research with Real-World Impact!

Background

Page 4: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

Composition of two or more cloud deployment models that remain unique entities but are bound together by proprietary technology that enables data and application portability.

One organization provides and manages the resources.

4World-Leading Research with Real-World Impact!

Hybrid Cloud

[NIST 2012, p18]

Page 5: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

Provisioned for exclusive use by a specific community of consumers from organizations that have shared concerns.

It may be owned, managed and operated by one or more of the organizations in the cloud.

5World-Leading Research with Real-World Impact!

Community Cloud

[NIST 2012, p18]

Page 6: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

Heterogeneity and tight coupling.

Pre-established business agreements.

Service Delivery Model.

6World-Leading Research with Real-World Impact!

Multi Cloud Restrictions

Page 7: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

A central management system.

Homogenous federation running the same management system on all infrastructures.

Central front end.

Common API on top of distinct independent management systems.

7World-Leading Research with Real-World Impact!

Multi Cloud Architectures

[VANDER 2012, p4]

Page 8: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

Separate infrastructure replaces their management system with a common one.

Easy to deploy and maintain.

Potential compatibility issues and new software adoption.

8World-Leading Research with Real-World Impact!

Central management system

[VANDER 2012, p5]

Page 9: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

Each infrastructure manages its resources independent from a central point.

Each management infrastructure should be replaced with tools capable of federation.

9World-Leading Research with Real-World Impact!

Homogenous Federation

[VANDER 2012, p6]

Page 10: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

All facilities and associated tools remain unchanged and keep their own user registration, procedures, etc.

The only commonality is a central location, hosting a list of all facilities and their tools.

10World-Leading Research with Real-World Impact!

Central front-end

[VANDER 2012, p5]

Page 11: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

Each facility keeps its current management software.

Common interfaces on top of each management software are specified, standardized and made available within the federation.

The need of a common protocol.

11World-Leading Research with Real-World Impact!

Common API

[VANDER 2012, p6]

Page 12: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

Replication of application.

Partition of application system into tiers.

Partition of application logic into fragments.

Partition of application data into fragments.

12World-Leading Research with Real-World Impact!

Security Prospects Multi Cloud

[BOHLI 2013, p3]

Page 13: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

Allows to receive multiple results from one operation performed in distinct clouds and compare them.

Integrity of the result.

13World-Leading Research with Real-World Impact!

Replication of Application

[BOHLI 2013, p3]

Page 14: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

Allows to separate the logic from the data.

Additional protection against data leakage due to flaws in application logic.

14World-Leading Research with Real-World Impact!

Partition into tiers

[BOHLI 2013, p5]

Page 15: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

Allows to distribute the application logic into distinct clouds.

No cloud provider learns the complete application.

No cloud providerlearns the overallcalculated result.

15World-Leading Research with Real-World Impact!

Logic into Fragments

[BOHLI 2013, p5]

Page 16: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

Allows distributing fine-grained fragments of data to distinct clouds.

None of the involved cloud providers gains access to all the data.

16World-Leading Research with Real-World Impact!

Data into Fragments

[BOHLI 2013, p7]

Page 17: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

We imagine a university Professor in physics at University of china that is a part of a multi institute scientific collaboration like CERN, who is collaborating on a new data set.

He wants to start an analysis program, which dispatches his code to the remote location where data is stored at University of Switzerland. Hence it contacts his identity provider at university of china, in order to get access to University of Switzerland resources that can be used for his simulation.

17World-Leading Research with Real-World Impact!

Federation

Page 18: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

18World-Leading Research with Real-World Impact!

Federation

University of China Idp

University of Switzerland Recourses

Client Trust

[CHADWK 2014]

Page 19: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

19World-Leading Research with Real-World Impact!

Federation

University of China Idp

University of Switzerland Recourses

Client Trust

1. Request for a service.

1

[CHADWK 2014]

Page 20: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

20World-Leading Research with Real-World Impact!

Federation

University of China Idp

University of Switzerland Recourses

Client Trust

1. Request for a service.2. Determine user’s identity provider.

12

[CHADWK 2014]

Page 21: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

21World-Leading Research with Real-World Impact!

Federation

University of China Idp

University of Switzerland Recourses

Client Trust

1. Request for a service.2. Determine user’s identity provider.3. SP redirect user to his idp for

authentication and user identity attributes.

123

3

[CHADWK 2014]

Page 22: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

22World-Leading Research with Real-World Impact!

Federation

University of China Idp

University of Switzerland Recourses

Client Trust

1. Request for a service.2. Determine user’s identity provider.3. SP redirect user to his idp for

authentication and user identity attributes.

4. User authentication with his idp.

123

34

[CHADWK 2014]

Page 23: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

23World-Leading Research with Real-World Impact!

Federation

University of China Idp

University of Switzerland Recourses

Client Trust

1. Request for a service.2. Determine user’s identity provider.3. SP redirect user to his idp for

authentication and user identity attributes.

4. User authentication with his idp.5. Idp authentication response to SP

with identity attributes of the user.

1235

345

[CHADWK 2014]

Page 24: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

24World-Leading Research with Real-World Impact!

Federation

University of China Idp

University of Switzerland Recourses

Client Trust

1. Request for a service.2. Determine user’s identity provider.3. SP redirect user to his idp for

authentication and user identity attributes.

4. User authentication with his idp.5. Idp authentication response to SP

with identity attributes of the user.6. Access the resource.

12356

345

[CHADWK 2014]

Page 25: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

25World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

1. User calling the client for federated log in, giving it the address of the keystone service.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

[CHADWK 2014]

Page 26: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

26World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

1. User calling the client for federated log in, giving it the address of the keystone service.

2. The client calls the federated keystone for the list of IdPs.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

[CHADWK 2014]

Page 27: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

27World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

1. User calling the client for federated log in, giving it the address of the keystone service.

2. The client calls the federated keystone for the list of IdPs.

3. Keystone Calls Directory Service to obtain the list of federation IdPs.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

[CHADWK 2014]

Page 28: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

28World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

1. User calling the client for federated log in, giving it the address of the keystone service.

2. The client calls the federated keystone for the list of IdPs.

3. Keystone Calls Directory Service to obtain the list of federation IdPs.

4. Keystone sends the set of idps back to the client.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

[CHADWK 2014]

Page 29: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

29World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

1. User calling the client for federated log in, giving it the address of the keystone service.

2. The client calls the federated keystone for the list of IdPs.

3. Keystone Calls Directory Service to obtain the list of federation IdPs.

4. Keystone sends the set of idps back to the client.

5. User chooses the idp. Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

[CHADWK 2014]

Page 30: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

30World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

1. User calling the client for federated log in, giving it the address of the keystone service.

2. The client calls the federated keystone for the list of IdPs.

3. Keystone Calls Directory Service to obtain the list of federation IdPs.

4. Keystone sends the set of idps back to the client.

5. User chooses the idp.6. The client returns the chosen idp and

asks an Idp request message.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

[CHADWK 2014]

Page 31: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

31World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

1. User calling the client for federated log in, giving it the address of the keystone service.

2. The client calls the federated keystone for the list of IdPs.

3. Keystone Calls Directory Service to obtain the list of federation IdPs.

4. Keystone sends the set of idps back to the client.

5. User chooses the idp.6. The client returns the chosen idp and

asks an Idp request message.7. Keystone look up the identity provider

for its protocol.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

[CHADWK 2014]

Page 32: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

32World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

1. User calling the client for federated log in, giving it the address of the keystone service.

2. The client calls the federated keystone for the list of IdPs.

3. Keystone Calls Directory Service to obtain the list of federation IdPs.

4. Keystone sends the set of idps back to the client.

5. User chooses the idp.6. The client returns the chosen idp and

asks an Idp request message.7. Keystone look up the identity provider

for its protocol.8. Keystone asks RI for appropriate format

of authentication and attribute request.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

[CHADWK 2014]

Page 33: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

33World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

1. User calling the client for federated log in, giving it the address of the keystone service.

2. The client calls the federated keystone for the list of IdPs.

3. Keystone Calls Directory Service to obtain the list of federation IdPs.

4. Keystone sends the set of idps back to the client.

5. User chooses the idp.6. The client returns the chosen idp and

asks an Idp request message.7. Keystone look up the identity provider

for its protocol.8. Keystone asks RI for appropriate format

of authentication and attribute request.9. RI make request to Directory Service to

obtain Idp metadata.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

[CHADWK 2014]

Page 34: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

34World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

1. User calling the client for federated log in, giving it the address of the keystone service.

2. The client calls the federated keystone for the list of IdPs.

3. Keystone Calls Directory Service to obtain the list of federation IdPs.

4. Keystone sends the set of idps back to the client.

5. User chooses the idp.6. The client returns the chosen idp and

asks an Idp request message.7. Keystone look up the identity provider

for its protocol.8. Keystone asks RI for appropriate format

of authentication and attribute request.9. RI make request to Directory Service to

obtain Idp metadata.10. RI returns Idp message to keystone.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

[CHADWK 2014]

Page 35: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

35World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

11. Keystone returns the request message to client.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

[CHADWK 2014]

Page 36: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

36World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

11. Keystone returns the request message to client.

12. Client or keystone passes request to Idp.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

[CHADWK 2014]

Page 37: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

37World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

11. Keystone returns the request message to client.

12. Client or keystone passes request to Idp.13. Idp asks user to authenticate.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

[CHADWK 2014]

Page 38: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

38World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

11. Keystone returns the request message to client.

12. Client or keystone passes request to Idp.13. Idp asks user to authenticate.14. Client passes the Idps response to

keystone.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

[CHADWK 2014]

Page 39: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

39World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

11. Keystone returns the request message to client.

12. Client or keystone passes request to Idp.13. Idp asks user to authenticate.14. Client passes the Idps response to

keystone.15. Keystone passes the response to the

credential validation function.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

[CHADWK 2014]

Page 40: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

40World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

11. Keystone returns the request message to client.

12. Client or keystone passes request to Idp.13. Idp asks user to authenticate.14. Client passes the Idps response to

keystone.15. Keystone passes the response to the

credential validation function.16. Credential validation calls directory to

obtain metadata to validate the response.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

[CHADWK 2014]

Page 41: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

41World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

11. Keystone returns the request message to client.

12. Client or keystone passes request to Idp.13. Idp asks user to authenticate.14. Client passes the Idps response to

keystone.15. Keystone passes the response to the

credential validation function.16. Credential validation calls directory to

obtain metadata to validate the response.

17. Credential validation returns the user’s ID, set of identity attributes and idp to keystone.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

[CHADWK 2014]

Page 42: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

42World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

11. Keystone returns the request message to client.

12. Client or keystone passes request to Idp.13. Idp asks user to authenticate.14. Client passes the Idps response to

keystone.15. Keystone passes the response to the

credential validation function.16. Credential validation calls directory to

obtain metadata to validate the response.

17. Credential validation returns the user’s ID, set of identity attributes and idp to keystone.

18. Keystone checks with Attribute Issuer Policy to ensure only allowed attributes asserted by Idp.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

[CHADWK 2014]

Page 43: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

43World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

11. Keystone returns the request message to client.

12. Client or keystone passes request to Idp.13. Idp asks user to authenticate.14. Client passes the Idps response to

keystone.15. Keystone passes the response to the

credential validation function.16. Credential validation calls directory to

obtain metadata to validate the response.

17. Credential validation returns the user’s ID, set of identity attributes and idp to keystone.

18. Keystone checks with Attribute Issuer Policy to ensure only allowed attributes asserted by Idp.

19. Keystone calls User Provisioning module , deletes expired entries and create temporary entry for the user.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

[CHADWK 2014]

Page 44: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

44World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

20. Keystone calls Attribute Mapper to obtain local set authorization attributes.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

[CHADWK 2014]

Page 45: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

45World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

20. Keystone calls Attribute Mapper to obtain local set authorization attributes.

21. Keytone updates these attributes in the temporary user entry and calls the token service to obtain unscoped token.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

[CHADWK 2014]

Page 46: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

46World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

20. Keystone calls Attribute Mapper to obtain local set authorization attributes.

21. Keytone updates these attributes in the temporary user entry and calls the token service to obtain unscoped token.

22. Keystone returns the token and list endpoints available.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

[CHADWK 2014]

Page 47: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

47World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

20. Keystone calls Attribute Mapper to obtain local set authorization attributes.

21. Keytone updates these attributes in the temporary user entry and calls the token service to obtain unscoped token.

22. Keystone returns the token and list endpoints available.

23. The user chooses the service.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

[CHADWK 2014]

Page 48: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

48World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

20. Keystone calls Attribute Mapper to obtain local set authorization attributes.

21. Keytone updates these attributes in the temporary user entry and calls the token service to obtain unscoped token.

22. Keystone returns the token and list endpoints available.

23. The user chooses the service.24. The client passes the token and chosen

domain and project to keystone. Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

[CHADWK 2014]

Page 49: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

49World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

20. Keystone calls Attribute Mapper to obtain local set authorization attributes.

21. Keytone updates these attributes in the temporary user entry and calls the token service to obtain unscoped token.

22. Keystone returns the token and list endpoints available.

23. The user chooses the service.24. The client passes the token and chosen

domain and project to keystone.25. Keystone calls TS to validate unscoped

token and get scoped token.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

[CHADWK 2014]

Page 50: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

50World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

20. Keystone calls Attribute Mapper to obtain local set authorization attributes.

21. Keytone updates these attributes in the temporary user entry and calls the token service to obtain unscoped token.

22. Keystone returns the token and list endpoints available.

23. The user chooses the service.24. The client passes the token and chosen

domain and project to keystone.25. Keystone calls TS to validate unscoped

token and get scoped token.26. Keystone returns to the client scoped

token and list of services.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

[CHADWK 2014]

Page 51: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

51World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

20. Keystone calls Attribute Mapper to obtain local set authorization attributes.

21. Keytone updates these attributes in the temporary user entry and calls the token service to obtain unscoped token.

22. Keystone returns the token and list endpoints available.

23. The user chooses the service.24. The client passes the token and chosen

domain and project to keystone.25. Keystone calls TS to validate unscoped

token and get scoped token.26. Keystone returns to the client scoped

token and list of services.27. Client contact the service provider

requesting service.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

CSP

[CHADWK 2014]

Page 52: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

52World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

20. Keystone calls Attribute Mapper to obtain local set authorization attributes.

21. Keytone updates these attributes in the temporary user entry and calls the token service to obtain unscoped token.

22. Keystone returns the token and list endpoints available.

23. The user chooses the service.24. The client passes the token and chosen

domain and project to keystone.25. Keystone calls TS to validate unscoped

token and get scoped token.26. Keystone returns to the client scoped

token and list of services.27. Client contact the service provider

requesting service.28. CSP passes the token to Keystone for

validation.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

CSP

[CHADWK 2014]

Page 53: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

53World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

20. Keystone calls Attribute Mapper to obtain local set authorization attributes.

21. Keytone updates these attributes in the temporary user entry and calls the token service to obtain unscoped token.

22. Keystone returns the token and list endpoints available.

23. The user chooses the service.24. The client passes the token and chosen

domain and project to keystone.25. Keystone calls TS to validate unscoped

token and get scoped token.26. Keystone returns to the client scoped

token and list of services.27. Client contact the service provider

requesting service.28. CSP passes the token to Keystone for

validation.29. Keystone contact TS.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

CSP

[CHADWK 2014]

Page 54: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

54World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

20. Keystone calls Attribute Mapper to obtain local set authorization attributes.

21. Keytone updates these attributes in the temporary user entry and calls the token service to obtain unscoped token.

22. Keystone returns the token and list endpoints available.

23. The user chooses the service.24. The client passes the token and chosen

domain and project to keystone.25. Keystone calls TS to validate unscoped

token and get scoped token.26. Keystone returns to the client scoped

token and list of services.27. Client contact the service provider

requesting service.28. CSP passes the token to Keystone for

validation.29. Keystone contact TS.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

CSP

[CHADWK 2014]

Page 55: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

55World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

20. Keystone calls Attribute Mapper to obtain local set authorization attributes.

21. Keytone updates these attributes in the temporary user entry and calls the token service to obtain unscoped token.

22. Keystone returns the token and list endpoints available.

23. The user chooses the service.24. The client passes the token and chosen

domain and project to keystone.25. Keystone calls TS to validate unscoped

token and get scoped token.26. Keystone returns to the client scoped

token and list of services.27. Client contact the service provider

requesting service.28. CSP passes the token to Keystone for

validation.29. Keystone contact TS.30. Keystone sends the response to CSP.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

CSP

[CHADWK 2014]

Page 56: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

56World-Leading Research with Real-World Impact!

Federation Protocol Sequence

IdP

Keystone

Client

Trust

31. CSP checks PDP if authorized, reply is granted.

Directory Service

Federated Keystone

Attribute Mapping

Request Issuing

Federation Protocol

Negotiation

Credential Validation

Attribute Issuing Policy

User Provisioning

Token Issuing & Validation Service

CSP

[CHADWK 2014]

Page 57: Multi Cloud Navid Pustchi April 25, 2014 navid.pustchi@utsa.edu

NIST. (2012). Cloud Computing Synopsis and Recommendations. Special Publication 800-146,

May 2012

VANDER. (2013). Architecture for the Heterogeneous Federation of Future Internet

Experimentation Facilities. Future Network & MobileSummit, 2013

BOHLI. (2013). Security and Privacy-Enhancing Multicloud Architectures. IEEE Transaction on

Dependable and Secure Computing, 2013

CASTILO. (2013). OpenStack Federation in Experimentation Multi-cloud Testbeds. UNICO,

2013

CHADWK. (2014). Adding Federated Identity Management to OpenStack. Journal of Grid

Computing, 2014

57World-Leading Research with Real-World Impact!

References