►
From YouTube: Pairing session Jira Connect authentication
Description
Related issue https://gitlab.com/gitlab-org/gitlab/-/issues/325278
A
Record
locally
yep
hey,
so
this
is
the
end
of
our
pairing
session,
where
we're
looking,
how
to
implement
or
off
with
for
our
jira
connect.
App
and
we've
just
ran
into
some
limitations
that
were
unknown
before
the
session.
So
the
biggest
limitation
is
that
you
need
to
define
an
or
of
application
beforehand
and
it
has
needs
to
have
the
redirect
uris
defined.
A
But
as
we
are
coming
from
jira
namespaces,
you
know
those
namespaces
don't
have
a
fixed,
redirect
url.
So
our
thinking
now
was
we're
just
going
to.
We
already
have
like
an
intermediary
page
that
actually
can
show
right.
We
already
have
like
an
intermediary.
I
probably
broke
things
now.
We
already
have
an
intermediary
page
where
you
land,
when
you're
not
signed
in
and
then
you're
redirected
back
to
the
jira
connect
app,
and
we
think
we
can
basically
use
this
page
as
a
middleman
for
redirects,
because
it
has
a
stable
url.
A
We
just
need
some
way
to
tie
in
the
url
to
door
flow,
and
the
idea
we
came
up
with
is
that
we
potentially
just
use
the
jira
connect
app
jot.
They
are
providing
us
because
it's
a
generated
thing
and
it
allows
us
to
tie
tie
after
the
oauth
flow
has
finished.
Thai
from
coming
from
his
chart,
allows
us
to
tie
it
back
to
the
original
url
and
go
back
to
it
right.
B
A
I
mean
that's
the
only
other
thing
we
probably
need
like.
We
need
like
an
api
with
the
final
access
token
like
we,
we
would
probably
need
another
endpoint
where
we
just
then
again
from
the
front
end,
send
you
know
the
state
and
the
code
and
then
the
back
end
gets
the
token
right
like
basically
doing
doing
this
call
right
yeah,
because
that
one
contains
the
secret
as
well
as
a
secret
as
well
yeah.