Public bug reported:
In order to activate a protocol for Federation, you need SOME value for
remote_id_attribute. However , this is set once per protocol in the
config file, not in the federated data. Thus, if two different SAML
implementations both wanted to use different values for
remote_id_attribute (DN vs CN for example) they could not.
** Affects: keystone
Importance: Undecided
Status: New
--
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/1724645
Title:
remote_id_attribute config options prevents multiple protocol
variations for Federation
Status in OpenStack Identity (keystone):
New
Bug description:
In order to activate a protocol for Federation, you need SOME value
for remote_id_attribute. However , this is set once per protocol in
the config file, not in the federated data. Thus, if two different
SAML implementations both wanted to use different values for
remote_id_attribute (DN vs CN for example) they could not.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1724645/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
