Reviewed: https://review.openstack.org/362397
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=de8fbcf9a0072c84adf4f3630088bc34f9e9782e
Submitter: Jenkins
Branch: master
commit de8fbcf9a0072c84adf4f3630088bc34f9e9782e
Author: Ronald De Rose <ronald.de.r...@intel.com>
Date: Mon Aug 29 20:13:35 2016 +0000
Validate mapping exists when creating/updating a protocol
This patch validates that a mapping exists when adding or updating
a federation protocol.
Change-Id: I996f94d26eb0f2c679542ba13a03bbaa4442486a
Closes-Bug: #1571878
** Changed in: keystone
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1571878
Title:
Add protocol to identity provider using nonexistent mapping
Status in OpenStack Identity (keystone):
Fix Released
Bug description:
Currently, it is possible to add a protocol to a identity provider [0]
using a nonexistent mapping id. We could add a mapping later using the
ID in the previous step, but several errors can occur in between this
steps.
We might want to enforce steps here:
1 - create idp
2 - create mapping
3 - create protocol
This would also be valid for the update case: only allow update the
protocol using a valid mapping ID.
[0] https://github.com/openstack/keystone-specs/blob/master/api/v3
/identity-api-v3-os-federation-ext.rst#add-a-protocol-and-attribute-
mapping-to-an-identity-provider
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1571878/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
