On 11/28/2013 03:55 PM, Doug Hellmann wrote:
>
>
>
> On Wed, Nov 27, 2013 at 5:21 PM, Georgy Okrokvertskhov
> mailto:gokrokvertsk...@mirantis.com>> wrote:
>
> Hi,
>
> I am working on the user-authentication BP implementation. I need to
> introduce a new configuration option for ena
On Wed, Nov 27, 2013 at 5:21 PM, Georgy Okrokvertskhov <
gokrokvertsk...@mirantis.com> wrote:
> Hi,
>
> I am working on the user-authentication BP implementation. I need to
> introduce a new configuration option for enable or disable keystone
> authentication for incoming request. I am looking for
Ok. So I will keep all authentication parameters in one place: solum.conf
There will be standard section for keystone [keystone_authentication] with
all common parameters like keystone URL, port, etc.
In the default section [DEFAUT] there will be a parameter
enable_authentication=True.
Actually i
> On Nov 27, 2013, at 2:25 PM, "Georgy Okrokvertskhov"
> wrote:
>
> Hi,
>
> I am working on the user-authentication BP implementation. I need to
> introduce a new configuration option for enable or disable keystone
> authentication for incoming request. I am looking for a right place for thi
On 11/27/2013 05:21 PM, Georgy Okrokvertskhov wrote:
> Hi,
>
> I am working on the user-authentication BP implementation. I need to
> introduce a new configuration option for enable or disable keystone
> authentication for incoming request. I am looking for a right place for
> this option.
>
> Th
Hi,
I am working on the user-authentication BP implementation. I need to
introduce a new configuration option for enable or disable keystone
authentication for incoming request. I am looking for a right place for
this option.
The current situation is that we have two places for configuration, one
