I don't think so. Federated auth is always 'External' so there is no need
to make that explicit.
On Tue, Oct 9, 2018, 4:26 AM Colleen Murphy <email address hidden> wrote:
> How should we fix this? Do we need a separate option for federated auth
> methods?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1643112
>
> Title:
> Auth plugins should be linked to Federation Protocol
>
> Status in OpenStack Identity (keystone):
> Triaged
>
> Bug description:
> When setting up Federation, if the protocol needs an new auth plugin,
> the current mechanism is to add it to the methods list for the [auth]
> section. However, this has the effect of linking them all together,
> when the real method should be to link the auth plugin with the
> protocol. Most of the Federation code is going to require the mapped
> plugin, but that should not be included in the stack that is then used
> for password or token based authentication.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/keystone/+bug/1643112/+subscriptions
>
I don't think so. Federated auth is always 'External' so there is no need
to make that explicit.
On Tue, Oct 9, 2018, 4:26 AM Colleen Murphy <email address hidden> wrote:
> How should we fix this? Do we need a separate option for federated auth /bugs.launchpad .net/bugs/ 1643112 /bugs.launchpad .net/keystone/ +bug/1643112/ +subscriptions
> methods?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Auth plugins should be linked to Federation Protocol
>
> Status in OpenStack Identity (keystone):
> Triaged
>
> Bug description:
> When setting up Federation, if the protocol needs an new auth plugin,
> the current mechanism is to add it to the methods list for the [auth]
> section. However, this has the effect of linking them all together,
> when the real method should be to link the auth plugin with the
> protocol. Most of the Federation code is going to require the mapped
> plugin, but that should not be included in the stack that is then used
> for password or token based authentication.
>
> To manage notifications about this bug go to:
> https:/
>