►
From YouTube: Support Ops Sync - 2022-12-13
Description
Support Ops Sync - 2022-12-13
A
Greetings
all
it
is
the
13th
of
December
welcome
all
we
kind
of
have
a
short
mentioned
on
this
one.
So
the
bill
and
myself
are
beginning
working
on
planning
the
removal
of
the
Explorer.
A
Once
we
kind
of
hammer
out
a
game
plan
and
get
some
of
the
details,
all
filled
in
we're
going
to
move
to
the
sandbox
and
we're
gonna
set
it
up
and
do
testing
and
we'll
do
all
that
fun
stuff.
You
might
get
paid
for
assistance
in
setup
or
testing
or
other
your
thoughts,
all
that
fun
stuff.
So
just
kind
of
be
aware,
you're
going
to
see
progress
on
that,
it's
not
slated
to
go,
live
until
February,
beginning
of
February.
So
this
is
just
us
getting
everything.
A
Kind
of
set
up
and
ready
beyond
that
does
invest.
Renewal
is
still
in
progress
so
once
that
is
finalized
I'll,
let
you
all
know
that's
kind
of
all.
I
have
at
the
moment.
Does
anybody
else
have
any
questions
comments,
concerns.
B
In
the
meantime,
I
was
trying
to
ask
one
question:
Jason
why
we
are
not
using
SSO
JWT
ssos,
specifically
for
users
to
log
in
in
to
zendesk.
So.
B
A
There's
another
one,
but
it
won't
work
with
gitlab.
The
problem
is
gitlab
itself
does
not
support
either
of
those
as
a
SSO
method
to
authenticate
to
gitlab.
So.
A
That
we
can't
actually
move
forward
with
either
of
those
it
is
like
a.
It
is
a
feature
request
that
is
being
worked
on,
because
it's
not
just
us
that
have
requested
that,
but
other
customers,
users.
So
the
auth
team
is
working
on
the
ability
to
make
gitlab
either
a
sample
provider
or
awt
provider,
but
because
that
was
the
other
one
by
the
way
Samuel.
B
A
Customers,
it
would
do
nothing
for
self-managed
customers
because
they
may
not
have
a
gitlab.com
account,
so
there's
that
whole
just
ordeal.
But
right
now
we
are
kind
of
blocked
on
even
the
concept
of
testing
it,
without
gitlab
being
able
to
be
a
JWT
or
more
likely
sample
provider,
because
obviously
sample
provider
would
be
the
better
option.
A
B
Yeah,
that's
weird
because
I
was
thinking
about.
If
they
could
log
in
Via
gitlab
SSO,
we
will
have
already
pretty
much
information
of
what
they
are
and
what
organization
they
belong
to,
and
we
can
probably.
A
B
B
A
That
that
is
one
like
substantial
problem
of,
even
if
we
had
all
that
in
place,
we
still
can't
do
contact
syncing
with
30
hundred
thousand
plus.
You
know
users
that
number's,
probably
not
even
close
to
Accurate
anymore,
but
so
there
are
substantial
limits
there.
We
do
have
kind
of
a
different
solution
with
the
contact
management
project
does
work,
we
have
some
people
tested
beta
tested
and
they
they
loved
it
in
that
they
were
like
I
didn't
have
to
file
a
ticket.
A
A
So
that's
kind
of
where
we're
going
moving
with
there
will
be
two
options
for
managing
your
contacts
file,
a
ticket
with
Ops
and
do
it
the
way
we
currently
do
it
or
right
ask
us
to
set
up
a
contact
management
project
for
you,
your
organization.
We
do
that
and
you
use
that
moving
forward
so
like
there
are
options
available
that
we
are
giving
that
new
option
as
we
take
away
the
old
prove
your
entitlements
method.
B
Right
and
how
do
we
differentiate
between
the
real
Associated
ones
and
the
realness
that
rejection
method,
that
is
pretty
complex,
to
be
honest
because
sometimes
customers
they
do
file
with
the
weird
free
stuff
and
they
get.
You
know
based
upon
their
selection
of
that.
Probably
we
have
to
remove
those
fields
as
well.
If
we
are
doing
this
and
consider
non-associated
free.
A
Yes,
that's
that's
something
in
the
issue.
I've
already
kind
of
posed
of
like
unassociated
free
is
not
really
impacted
by
this
because
that's
a
whole
different.
Like
ball
game.
This
is
right,
I'm
paid
but
I'm
on
Associated.
It's
that
what
we've
traditionally
called
the
needs
org
category
free
unassociated
is
I
mean
I,
wouldn't
even.
A
A
It
it's
not
great
security
wise.
It
can
always
be
an
issue,
it's
not
fun,
for
the
customers
to
have
to
spend
the
first
half
of
their
ticket,
proving
who
they
are
perfect
so
yeah.
It
is
a
massive
change,
which
is
why
there's
going
to
be
things
like
a
blog
post
and
communication
with
sales
who
should
be
communicating
with
their
customers
if
we're
going
to
communicate
it
internally,
probably
using
like
the
what's
happening
in
git
lab,
probably
doing
an
Ama.
A
Of
working
out
all
the
internal
communication
concept
for
that,
but
yeah
no,
this
is
a
big
thing.
That's
why,
instead
of
going
kind
of
a
this
is
what
we're
doing
and
doing
like
we
traditionally
would
have
testing
and
sandbox
and
kind
of
figuring
as
we
go.
You
and
I
are
starting
with
a
no
we're
gonna
plan
this
one,
because
this
is
a
particularly
big
change-
that,
if
done
poorly,
could
have
very
nasty
consequences
right.
A
That's
kind
of
why
you
and
I
are
starting
with
a
planning
issue
instead
of
just
kind
of
going
into
the
sandbox
and
setting
it
up
and
seeing
you
know
and
playing
with
it
that
way,
we're
going
to
kind
of
tackle
this
a
different
way,
and
maybe
we
end
up
saying
this
planning
issue
really
wasn't
needed.
We
could
have
done
it
the
old
way
and
it's
good
to
know
for
future
presents.
Maybe
we'll
say
this
was
the
right
way.
We
should
do
it.
A
B
Yeah
I
was
just
wondering
about
those
technical
stuff
about
JWT
that
why
we
are
not
using
it
now.
I've
got
my
answer
so
yeah.
A
Unfortunately,
gitlab
doesn't
support
being
a
JWT,
stable
provider
and
even
if
they
did
there's
still
that
problem
that
we've
had
moving
over
us
forever.
If
we
have
too
many
contacts
to
say.