Add protocol to identity provider using nonexistent mapping
Bug #1571878 reported by
Rodrigo Duarte
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Ron De Rose | ||
Newton |
Fix Released
|
High
|
Unassigned |
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.
description: | updated |
description: | updated |
Changed in keystone: | |
assignee: | nobody → Ron De Rose (ronald-de-rose) |
Changed in keystone: | |
milestone: | none → newton-3 |
Changed in keystone: | |
milestone: | newton-3 → none |
importance: | High → Medium |
Changed in keystone: | |
assignee: | Ron De Rose (ronald-de-rose) → Steve Martinelli (stevemar) |
Changed in keystone: | |
assignee: | Steve Martinelli (stevemar) → Ron De Rose (ronald-de-rose) |
Changed in keystone: | |
milestone: | none → ocata-1 |
To post a comment you must log in.
Make sense. Currently you can't have more than one mapping per protocol anyway.