►
From YouTube: SIG-Auth Bi-Weekly Meeting for 20220706
Description
SIG-Auth Bi-Weekly Meeting for 20220706
A
B
B
I
will
I
it's
okay,
if
you
just
share
I'll,
just
give
a
quick
summary
of
it
and
kind
of
explain
where
it
is
right
now
so
yeah.
Basically,
this
steps
been
open
for
a
while.
I
didn't
get
a
chance
to
work
on
it
over
the
last
release,
so
I'd
like
to
keep
the
discussion
going
early
for
126,
but
basically
it
is
a
proposal
to
solve
a
number
of
use
cases.
B
One
of
the
use
cases
that
that
I'm
interested
in
is
basically
request
signing
so
allowing
clients
to
use
request,
signing
something
that
aws
would
like,
but
there's
a
number
of
other
use
cases
that
others
are
interested
in.
You
know
I've
been
working
with
mo
and
he
is
interested
in
an
external
tls
certificate,
signer
which
this
would
also
enable.
So
basically,
the
most
recent
update
there's
been
a
decent
amount
of
conversation
and
iteration.
B
B
Originally,
I
had
kind
of
done
a
separate
like
new
objects,
and
he
wanted
me
to
use
the
existing
exec
auth
api
objects,
which
makes
complete
sense.
I
kind
of
I
wasn't
a
fan
of
how
they
use
spec
and
status,
but
I
mean
there's
no
reason
to
recreate
what
we
already
have
so
ended
up
just
going
with
that
and
yeah.
So
I
think
it's
ready
for
another
round
of
review.
It's
it's
really
mostly
been
mo.
B
B
There
was,
I
think,
the
rest
of
the
comments
were
relatively
small,
just
like
asking
for
more
explanation
in
certain
places.
There's
so
one
area
is
whether
or
not
so,
we've
kind
of
settled
on
uds
so
that
the
the
proxy
gets
exact
by
the
client
and
then
the
proxy
returns
information
that
allows
the
client
to
talk
to
it.
So
right
now
we're
we've
kind
of
settled
on
a
ca
bundle
for
authentication
and
then
the
uds
like
socket
path.