Give more details about the K2K flow
Bug #1459686 reported by
Rodrigo Duarte
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Invalid
|
Medium
|
Unassigned |
Bug Description
Currently, the K2K flow in the config file [1] isn't detailed enough, we should provide at least the next step where we exchange a SAML assertion for a unscoped token from the SP.
tags: | added: federation |
Changed in keystone: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in keystone: | |
assignee: | nobody → Marek Denis (marek-denis) |
To post a comment you must log in.
I am not sure whether we should start explaining vaguely how the idp-initiated saml workflow works. Maybe it's worth waiting few more days for K2KAuthPlugin and make a reference to that?