►
Description
Our second episode dives into disabling the root user account and enabling users to authenticate using GitHub.
A
A
One
of
the
things
that
makes
those
default
options,
particularly
unsuited
for
production,
is
that
they
enable
just
one
single
root
user
account.
So
today
we're
going
to
walk
through
the
relatively
small
amount
of
setup
required
for
integrating
brigade
with
a
third
party
authentication
provider.
I'm
going
to
start
out
by
visiting
our
quick
start
documentation.
A
A
A
A
A
A
Last,
we
need
to
provide
an
authentication
callback
url.
This
is
the
base
of
a
brigade
api
server
url.
That
github
will
redirect
the
user's
browser
to
in
order
to
complete
the
authentication
process
I'll
be
deploying
brigade
in
a
local
kind.
Cluster.
That's
already
up
and
running.
My
plan
is
to
forward
traffic
from
local
host
port
8443
to
the
api
server
running
inside
my
kind
cluster.
A
A
A
When
we
complete
the
authorization
process,
we're
redirected
to
a
splash
page,
this
cert
warning
is
to
be
expected
because
again
we're
using
a
self-signed
certificate
at
the
moment.
So
we
can
ignore
this
and
we
see
our
beautiful
splash
page.
That
says
you
are
now
logged
in
and
may
resume
using
the
brigade
cli
back
in
our
terminal.
We
can
now
type
just
about
any
brig
command
to
verify
that
we
are
logged
in
we'll
list
users.