Allow for mapping to existing user in federated workflow

Registered by Marek Denis on 2015-01-21

Allow for specifying mapping rules where effective user must exist in the backend. Otherwise map users to default domain named federated.

Blueprint information

Status:
Complete
Approver:
Guang Yee
Priority:
High
Drafter:
Marek Denis
Direction:
Needs approval
Assignee:
Marek Denis
Definition:
Approved
Series goal:
Accepted for kilo
Implementation:
Implemented
Milestone target:
milestone icon 2015.1.0
Started by
Morgan Fainberg on 2015-02-16
Completed by
Steve Martinelli on 2015-03-02

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/federated-direct-user-mapping,n,z

Addressed by: https://review.openstack.org/149071 (merged)
    Allow for direct mapping in federated authN.

Gerrit topic: https://review.openstack.org/#q,topic:add_domain_to_fed_tokens,n,z

Addressed by: https://review.openstack.org/110858 (merged)
    Add a domain to federated users

Addressed by: https://review.openstack.org/154100 (Abandoned)
    Change user identification in mapping engine

Addressed by: https://review.openstack.org/154934 (merged)
    Make user an object in mapping engine.

Addressed by: https://review.openstack.org/156158 (merged)
    Fix nits from patch #110858

Addressed by: https://review.openstack.org/156308 (merged)
    Authenticate local users via federated workflow.

Gerrit topic: https://review.openstack.org/#q,topic:fed_domain_config_option,n,z

Addressed by: https://review.openstack.org/156461 (merged)
    Make federated domain configurable

Addressed by: https://review.openstack.org/157711 (merged)
    Make Rule.Processor_UserType class public

Addressed by: https://review.openstack.org/157717 (merged)
    Move UserAuthInfo to a separate file

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.