On 07/17/2015 07:55 PM, Jamie Lennox wrote:
So I'm not familiar with how Sahara handles contexts however from a theoretical
stand point anything that is defined in config should be able to be cached
globally. So service specific sessions, and admin auth. The context typically
would contain thi
On 18 Jul 2015 6:29 am, michael mccune wrote:
>
> On 07/16/2015 04:31 PM, michael mccune wrote:
> > i will also likely be rewriting the spec to encompass these changes if i
> > can get them working locally.
>
> just wanted to follow up before i rewrite the spec.
>
> i think the most sensible
On 07/16/2015 04:31 PM, michael mccune wrote:
i will also likely be rewriting the spec to encompass these changes if i
can get them working locally.
just wanted to follow up before i rewrite the spec.
i think the most sensible approach at this point is to store an auth
plugin object in our co
hi all,
i've been researching, and coding, about how to upgrade sahara to use
keystone sessions for authentication instead of our current method. i'm
running into some issues that i believe might make the current proposed
approach[1] unfeasible.
one issue i'm running into is the nature of ho
