On Thu, Aug 14, 2014 at 11:20 AM, Bill Farner wrote:
> Disclaimer: I am far from an expert in security.
>
> As for mechanics of where auth code should live, a new HTTP filter sounds
> like the best approach.
>
> Since the scheduler already does authentication for the API, ideally the
> mechanics o
Disclaimer: I am far from an expert in security.
As for mechanics of where auth code should live, a new HTTP filter sounds
like the best approach.
Since the scheduler already does authentication for the API, ideally the
mechanics of the two will be the same. This might mean that the
authenticati
Hello,
This is similar to this thread [1], but for aurora scheduler. We are
implementing cookie based authentication for aurora scheduler (port:
8080). It is a single sign-on implementation. The unauthenticated
users will be redirected to a login service. After user is
successfully authenticated i
