►
From YouTube: Deep dive on using MSAL.js to integrate Angular single-page applications with Azure AD – August 2022
Description
This month’s in-depth topic: Deep dive on using MSAL.js to integrate Angular single-page applications with Azure Active Directory. Integrate an Angular single page app with the Microsoft identity platform. Integrate single sign-on and get an access token for Microsoft Graph API. Coding walk-through includes subscribing to MSAL events, protecting routes using MSAL Angular Guard, and acquiring tokens with MSAL Angular Interceptor. See how apps can prepare themselves for Continuous Access Evaluation (CAE) events and deploying app on Azure Static App Service. Microsoft Presenters are Doğan Erişen, Salman Salem and Kalyan Krishna. Recorded August 18, 2022
Learn more
• See the full blog post for this call in the Microsoft 365 platform community blog - https://aka.ms/m365/blog
• Download the recurrent invite for this call | https://aka.ms/IDDevCommunityCalendar
• Microsoft 365 Unified Sample gallery - https://aka.ms/m365/samples
• Microsoft 365 Platform Community in YouTube - https://aka.ms/m365/videos
• Microsoft 365 Platform Community - http://aka.ms/m365/community
A
A
We
had
a
lot
of
folks
joining
that
call
and
in
fact,
we've
got
good
number
of
youtube
views
as
well,
and
there's
a
lot
of
talking
buzz
about
how
the
call
went.
We
have
a
similar
topic
this
month
as
well.
The
only
change
being
it's
going
to
be
an
angular
framework
and
again
run
by
dogan,
salman
and
kalyan
the
quick
pointers
as
usual.
This
call
gets
recorded.
So
let's
try
to
be
friendly
on
the
call,
please
feel
free
to
ask
in
your
questions.
We
would
love
to
know
your
experiences.
A
We
have
the
calls
recorded
and
posted
at
that
link,
which
is
ak
dot.
Ms
m365
pnp
slash
videos,
and
then
we
have
a
survey
that
will
be
shared
on
the
chat
window.
It's
it's.
It's
really
important
for
us
to
know
your
experience
of
the
call,
because
that
helps
us
plan.
The
call
as
well
as
speakers
get
to
know
what
was
the
experience
and
feedback
on
the
call.
A
B
B
We
are
going
to
basically
have
walkthrough
of
how
to
integrate
your
angular
javascript
applications
with
microsoft's
identity
platform
as
your
active
directory
or
microsoft
intra,
whichever
name
that
you
are
familiar
with
today.
It's
a
continuation
of
the
call
we
had
last
month,
which
was
essentially
covered.
The
javascript
react
applications
this
time
we
want
to
cover
the
angular
side
of
things.
So
without
further
ado,
I
will
basically
hand
it
over
to
the
one
in
my
team
who
would
introduce
himself
and
then
inshallah
salman,
and
then
we
can
get
forward.
Go.
C
C
C
Our
first
target
will
be
to
enable
single
sign-on,
and
then
we
will
attempt
to
get
an
access
token
for
microsoft.
Graph,
then
cellman
will
talk
us
about
what
is
continuous
access
evaluation
and
how
you
can
handle
those
in
your
applications,
and
then
we
will
finish
the
session
with
deploying
our
application
to
azure
static
web
apps.
C
At
the
end
of
the
slide,
there
will
be
some
next
steps
and
references
we
will
share
with
the
deck,
so
you
can
take
a
look
at
those
later
on
as
well
all
right.
So
very
briefly,
what
is
microsoft,
authentication
library
for
javascript?
It's
essentially
a
family
of
packages,
family
of
libraries
targeting
various
kind
of
javascript
applications
and
enables
them
to
acquire
access,
tokens
and
id
tokens
for
the
microsoft
identity
platform.
C
C
C
The
pixi
is
a
mechanism
that
prevents
authorization
called
replay
attacks,
so
it's
a
more
secure
than
the
previously
used
implicit
flow
and
then
angular
supports
angular
applications,
nine
version.
Nine
and
later
we
have
some
limited
support
for
server
side,
rendering
via
angular
universal,
and
it
has
the
same
public
api
with
m
sub
browser.
C
C
C
As
always.
Let's
cover
some
prerequisites:
you'll
need
to
have
node.js
version
14
or
later
on
your
system,
you're
also
going
to
need
an
azure
subscription,
especially
for
the
deploying
our
apps
to
static
web
apps
and
then
you're
going
to
need
a
github
account
if
you
like
to
use
github
to
deploy
your
apps
okay,
so
I'll
take
a
break
from
the
slides
here
and
I'll.
Show
you
what
I
have
cyclone
this
project,
it's
a
very
simple,
angular
application.
Let
me
go
ahead
and
write
start.
This
I've
generated
this
project
using
angular
cli.
C
C
C
C
I
have
a
login
and
logout
button.
I
have
a
text
to
identify
the
signed
in
user.
Of
course
we
are
not
signed
in
at
the
moment,
and
then
I
have
a
profile
page
to
display
some
dummy
data
right
now,
I'm
using
some
dummy
data,
but
I
will
eventually
replace
it.
So,
let's
go
ahead
and
step
by
step.
Add
authentication
to
this
guy,
so
I'll
terminate
this
and
I'll
begin
by
importing
our
dependencies.
C
And
while
this
is
happening,
let's
go
to
our
app
module,
and
here
I'm
going
to
instantiate
my
msul
application
object
and
there
are
multiple
ways
of
doing
this.
You
could,
for
instance,
use
the
m
cell
module
the
static
method
to
instantiate
it.
You
could
perhaps
want
to
fetch
some
configuration
data
from
some
other
server,
some
other
location
and
then
instantiate
msul.
C
C
C
C
You
have
multiple
options
here:
you
can,
you
want
to
go
and
perhaps
go
with
a
multi-tenant
application,
or
you
may
want
to
sign
in
a
personal
microsoft
account
I'm
going
to
choose
single
tenant.
I
want
to
sign
in
the
users
in
my
own
tenants
and
then
I
need
to
select
a
redirect
uri.
It
has
to
be
a
single
page
application,
so
I'll
go
ahead
and
register.
My.
C
C
So
if
you
have
a
sign
out
uri
that
also
has
to
be
specified
here
and
then
I'll
go
to
api
permissions,
and
I
have
a
permission
here
for
calling
microsoft
graph,
the
profile
endpoint,
and
that
is
the
permission
that
I'm
going
to
need
to
acquire
an
access
token
for
okay,
so
I'll
go
back
to
my
app
I'll
copy,
this
client
id
and
I'll
do
this
and
I'm
getting
an
address
here.
Why?
Because
we
didn't
import
this,
so
let's
go
ahead
and
do
that.
C
C
So
if
you're
developing
a
line
of
business
application-
and
you
want
to
sign
in
the
users
in
your
own
tenants
that
will
contain
your
tenant
id
and
then
you
should
specify
a
redirect
uri.
This
is
the
uri
that
your
application
will
receive
the
authorization
code
from
azure
id,
and
then
you
have
some
more
options
we
will
get
to
that
later
on.
But
for
now
these
three
should
suffice.
C
So
I'll
go
back
to
my
app
I'll
specify
the
authority
parameters.
I
want
to
use
common
if
I
use
common
that'll
be
a
multi-tenant
app,
and
I
don't
want
this
I'll
go
back
to
my
app
registration
and
I'll
copy,
my
tenant
id
and
then
I'll
have
a
redirect
uri.
Here
you
can
specify
the
whole
uri
or
you
can
just
specify
a
path
which
is
going
to
be
better
actually
because
later
on,
we're
going
to
deploy
this
application
and
then
I
don't
want
to
come
back
and
change
this
with
the
deployed
application
origin.
C
C
C
Instance-
and
so
let
me
first
show
pop-up,
so
you
have
two
options
here
for
designing
experience.
You
could
open
a
pop-up
and
assign
the
user
in
there
or
you
could
direct
the
user
to
the
azure
id
sign-in
endpoint,
so
I'll
show
this
pop-up
first
and
then
I'm
going
to
show
you
redirect,
because
that
requires
a
bit
more
setup.
C
C
And
now
I'm
signed
in,
of
course,
there's
nothing
on
my
ui
there's
no
indication
and
will
come
to
fix
to
that,
but
I
know
I'm
signed
in
because
I
can
see
that
amsol
has
oops
yeah
there
it
is.
I
can
see
that
amsol
has
stored
the
result
from
my
sign-in
operation.
Now.
What
are
these?
These?
Are
your
tokens
and
some
other
relevant
information
and
we'll
come
to
discuss
that
in
more
detail,
but
let's
first
take
a
moment
to
show
the
redirect
flow.
C
So
if
I
want
to
use
redirect
the
setup
is
a
bit
more
requires
a
bit
more
preparation,
as
always
any
kind
of
login
or
acquire
token
method.
I
can
pass
a
request,
parameter
request,
object
and
you
have
many
options
there.
I
want
users
to
sign
in
to
user
reads:
this
is
the
scope
that
I
need
to
access
a
microsoft
graph
profile
endpoints.
C
C
And
then
end
the
component
to
handle
the
response
in
that
routes.
So
what
azure
id
is?
Does
it's
going
to
send
you
the
authorization
code
to
this
path
and
there
we
need
to
grab
that
code
and
handle
it
and
msl
angular
actually
does
that
for
us.
So
we
only
have
to
pass
this
component
here.
This
is
a
dedicated
redirect
handler
and
also
we
need
to
go
back
to
our
app
module
and
bootstrap
this
component.
Let's
go
ahead
and
import
this,
and
this
component
targets
a
selector
named
aprididec
on
the
page.
C
C
C
And
how
should
I
do
this?
Well,
if
someone
is
signed
in,
if
there's
a
signed
in
account
in
the
cache,
I
should
be
able
to
get
it
from
amsoil
there
we
go.
This
is
the
method
that
I
could
use
to
get
the
active
account,
but
there
needs
to
be
an
active
account
set
in
the
first
place
which
we
didn't
yet,
but
we
will
do
well
in
that
case,
if
there's
no
active
account,
but
there
are
some
accounts
in
the.
C
I
cache
say,
get
all
accounts
and
I
can
check
if
this
is
greater
than
zero.
Well,
in
that
case,
go
ahead
and
make
the
active
account
the
first
account
in
this
array.
This
will
get
you
all
the
accounts
in
the
cache,
but
they
may
not
be
active.
You
have
to
actually
explicitly
mark
them
as
active
and
then
I'm
going
to
use
the
msl
service
to
set
this
as
active
account.
C
And
I'll
go
back
to
my
component
and
now
I
can
use
this
guy,
so
I
want
to
do
this
when
our
component
first
mounts
whenever
our
component
renders
we
want
to
check
the
current
interaction
status
and
to
do
that,
I
need
a
lifecycle
method.
So
I'm
going
to
use
ngon
init,
I'm
also
going
to
tell
angular
I'm
using
it.
C
C
C
So
now
we
can
conditionally
render
these
elements
and
I'll
go
back
to
my
app
and
see:
what's
happened
there?
Okay,
there
we
go
so
our
ui
is
updated.
We
don't
see
the
login
button
anymore.
We
have
the
identifying
the
currently
signed
in
usage
and
so
far
so
good.
Let's
also
add
logouts
just
for
completing
this.
C
C
All
right,
so
one
thing
here
is
that
I
didn't
like
the
way
of
setting
active
account
like
this.
You
may
need
more
complex
logic
here,
I'm
just
getting
the
first
account
from
the
currently
signed
in
accounts
and
setting
this
as
active,
but
the
better
way
to
do
this
is
actually
subscribing
to
msu
events.
C
The
better
way
to
do
this
is
actually
setting
the
active
account
when
the
user
first
signs
in
so
amsoil
allows
you
to
subscribe
to
various
kinds
of
events,
the
msu
fires,
these
events
when
they
occur,
and
then
you
can
take
actions
to
handle
them
or
to
update
ui
or
to
make
an
api
call
or
whatever
you
want,
and
I
want
to
use
this
login
success
event.
I
want
to
subscribe
to
this
and
set
my
active
account
when
this
fires
so
go
back
to
my
app.
C
C
C
There
we
go
now,
there's
one
thing
very
important:
when
you're
subscribing
to
events
you'll
have
to
make
sure
to
unsubscribe
them
when
your
components
unmounts
and
the
way
to
do
this
is
essentially
you're
going
to
need
a
another
life
cycle
event.
So
I'll
just
go
ahead
and
do
this,
so
this
is
important,
especially
for
the
performance
of
your
application.
C
C
So
most
of
you
are
interested
in
how
to
have
the
most
easiest,
sign-on
sign-in
experience
for
your
users,
and
you
want
this
to
be
as
simple
as
possible
for
them.
So
you
probably
don't
want
them
to
enter
their
credentials
again
if
they
are
already
signed
in
and
how
is
how
does
single
sign-on
works?
Is
that?
C
That
will
tell
the
user
to
pick
an
account,
because
azure
ad
cannot
know
which
account
you
want
to
sign
in,
and
there
are
ways
to
bypass
that,
for
instance,
you
can
pass
in
a
login
hint
to
msul
and
that
will
allow
himself
to
pick
the
right
account
and
sign
your
user
directly
in
without
seeing
a
prompt,
so
I'll
take
a
step
back
and
just
show
you
how
this
works.
So
I
have
my
application
and
my
users
signed
in
here
now.
If
I
go
back
to
this
tab,.
C
My
user
is
not
signed
in
in
this
tab
and
we
can
make
this
work
out
of
the
box
very
simple
and
I'll
come
to
that
later
on.
But
since
I
already
have
an
active
session
here,
if
I
click
the
login
button,
I
should
just
sign
in
there
we
go
so
you
just
saw
a
brief,
flickering
and
transition,
and
then
we
immediately
saw
the
ui
updated.
C
However,
this
method
will
not
work
if
you
are
using
a
browser
that
blocks
third-party
cookies.
Why
well?
What
happens
when
you
sign
into
azure
id
is
that
azure
80
places
a
session
cookie
in
your
browser
and
that
cookie
is
associated
with
the
domain
of
azure
id
and
that'll
be
login.microsoftonline.com,
but
that
domain
is
different
than
the
domain
of
your
application,
and
so
that
cookie
is
considered
a
third-party
cookie
and
more
and
more
browsers,
safari.
C
B
C
C
C
B
Questions
into
the
chat
window,
please.
The
next
question
is
what
information
is
present
in
the
session
cookie
that
is
placed
by
azure
id
into
the
browser.
It's
a
server-side
cookie.
It's
it
contains
proprietary
encrypted
information
that
azure
id
uses
to
essentially
assert
certain
everything
from
whether
a
user
should
be
signed
on
using
single
sign-on
to
things
like
that
are
related
to
identity,
protection,
risk
analysis
and
and
things
of
that
nature.
B
C
Sure
the
most
important
aspect,
if
you're
assigning
it
with
b2c,
is
going
to
be
authority
parameter.
This
will
contain
your
tenant
domain.
B2C
tenant
domain,
followed
by
your
your
the
policy
that
you
are
using
to
sign
in
your
users.
We
have
very
many
b2c
samples.
Please
go
ahead
and
take
a
look
at
them.
B
Is
it
possible
to
start
amazon
redirect
from
sign
in
and
redirect
back
to
a
different
url?
So
the
question
here
is
that
azure
ad,
when
you
are
at
azure
id
and
you
want
azure
to
redirect
to
a
certain
url.
Obviously
that's
one
of
the
parameters
that
you
provide,
how
you
manage
it
is
up
to
you,
but
just
remember
this-
that
azure
ad
will
not
redirect
you
to
any
url
that
is
not
registered
or
provided
in
the
redirect
uri
section
of
the
app
registration.
B
C
B
Does
that
answer
your
question?
I
suppose
you
can.
We
can
continue
chatting
about
it.
Next
question
is
from
muralitharan.
Can
we
embed
msulgs
to
build
power
platform
component
framework
controls?
We
don't
have
an
answer
to
this
really
is
mostly
because
you
know
we
are
a
platform
and
we
have
an
authentication
library.
How
does
it
use
get
used
by
various
other
products
within
microsoft
and
from
others
out
there
isn't
necessarily
in
our
control.
B
C
C
C
C
C
If
the
user
belongs
to
some
roles,
you'll
have
that
in
the
claim
you'll
see
the
user's
tenant
id
which
tenant
this
user
belongs
to
and
you'll
have
any
azure
id
rules
if
they
are
assigned
to
the
user,
and
you
can
use
this
information
to
customize
your
ui
in
any
way,
but
you
shouldn't
use
an
id
token
to
access
a
web
api.
That
is
what
an
access
token
is
for
any
particular
questions
about
id
tokens.
B
C
C
C
The
trade-off
here
is
that,
well,
you
make
a
trade-off
between
more
secure
and
better
user
experience,
so
memory
storage
would
be
the
most
secure
one
because
essentially
amsoil
does
not
cache
items
anywhere
else,
but
the
memory
and
at
the
other
end
of
the
spectrum.
You
have
the
local
storage,
which
gives
you
the
best
user
experience,
because
now
your
application,
now
the
instances
of
your
application
running
on
different
tabs
will
have
access
to
the
same
cache.
C
C
It
binds
your
token
to
your
browser,
cryptographically
and
it
cannot
be
used
outside
of
that
browser,
and
then
we
have
continuous
access
evaluations
that
allows
resources
web
apis
to
invalidate
an
access
token
at
any
moment
in
time-
and
this
is
what
we
are
going
to
discuss.
Salman
will
talk
about
in
later.
C
C
Finally,
I
want
to
talk
about
logging,
so
amsoil
allows
you
to
log
whatever
it's
doing
at
any
moment
at
various
levels
of
details,
and
these
logs
are
useful
for
understanding
what's
going
on
and
debugging.
If
anything
goes
wrong
with
your
application
and
likewise
you
configure
this
in
the
public
client
application
instance.
C
B
C
Sure,
okay,
so
let's
continue
so
far,
we
discussed
em
cell
service
and
oops
and
amstel
broadcast
service.
Now,
let's
discuss
the
amsoil
guards.
Remember
we
have
a
route
in
our
application
profile
routes
that
doesn't
require
authentication.
At
this
moment.
I
can
just
sign
out
and
review
this
route,
and
you
don't
want
this.
You
want
to
protect
your
routes
and
allow
only
the
authenticated
user
to
see
that
child
and
it's
very
easy
to
do
with
angular
m
sub
angular.
C
If
you
like,
you
can
add
this
to
your
home
page
as
well,
so
that
means
as
soon
as
the
user
hits
your
application
they
will
have
to
sign
in,
but
importantly,
do
not
add
this
to
your
redirect
uri,
because
this
will
just
break
it,
and
I
then
I
go
to
my
app
module
and
declare
this.
Is
the
provider
oops.
C
C
And
then
return
okay,
so
what
do
I
need
to
return?
Well,
let's
take
a
look
at
the
guard
configuration
here.
I
can
specify
an
interaction
type
if
the
user
is
not
signed
in
and
the
msl
guard
kicks
in.
I
can
specify
what
kind
of
interaction
I
want
the
guard
to
use
so
I'll
go
ahead
and
I'm
going
to
choose
the
direct
here
as
well.
I
like
your
dialect,
let's
import
this
and
then
optionally.
You
can
pass
in
an
authentication
request.
C
So,
for
instance,
you
can
specify
here
what
scopes
the
user
should
consent
to
if
they
hit
the
m
cell
guards,
you
can
specify
more
options
here,
take
a
look
at
those
and
how
you
can
use
that
in
your
application
and
once
I
have
this
factory
emitted,
oops
there's
one
thing:
I'm
missing
here:
okay,
so
now
this
should
just
work.
Let's
try
it
out
I'll
go
to
my
app,
I'm
not
signed
in
I'll
go
to
profile
and
the
guard
kicks
in
and
I'll
sign
in
to
diego.
C
So
if
you're
familiar
with
amsoil
browsers
before
you
can
just
go
ahead
in
your
components
and
use
msul
directly
to
acquire
a
token
but
amsoil
angular
mixed
is
easier
for
you.
It
has
a
interceptor
component
class
that
allows
you
to
intercept
the
outgoing
calls
and
attach
an
access
token.
If
you
specify
that
it's
requiring
that
so
the
way
I
do
this
I'll
go
into
my
providers
here
again.
C
C
Interceptor
configuration
okay,
so
now
this
guy
should
return.
Let's
see
what
it
should
return
an
interaction
type.
Similarly,
so
this
time
I
want
to
use
pop-up
and
then
it
should
have
a
protected
resources
map,
okay,
I'll,
go
ahead
and
create
something
like
that
and
I'll
talk
about
more
and
what
this
is.
C
Okay
and
let's
import
this,
so
this
map
allows
you
to
associate
a
end
point:
for
instance,
the
microsoft
graph
profile
endpoint
with
a
certain
scope
and
amstel
understands
that
to
access
this
endpoint,
I
need
an
access
token,
with
this
scope
or
permission
and
I'll
go
ahead
and
do
this
first.
Let
me
pass
this
guy
here
and
then
the
way
to
do
this
is
oh
okay,
right
here,
yeah.
C
C
C
C
C
C
B
D
D
D
D
D
D
The
first
step
that
we
need
to
do
is
to
configure
and
cell
app
to
declare
it
as
capable
of
handling
claim
challenge.
Then
we
will
grab
the
authenticated
header
from
the
401
response.
After
that
we'll
process
the
header
and
pass
the
claims
to
the
m
cell
as
a
request
parameter
now
we
can
dive
into
the
code
a
little
bit.
Unfortunately,
we
can't
test
ca
live
because
it
takes
around
10
to
15
minutes
to
trigger.
D
D
Thing
that
we
need
to
see
is
the
auth
configuration
file
all
right.
There
we
go
as
you
can
see
in
the
install
configuration
object.
We
set
the
client
capabilities
to
cp1
that
lets
the
resource
owner
know
that
the
client
is
capable
of
handling
clean
challenge.
So
you
need
to
add
this
in
your
configuration
and
then
we'll
go
to
the
profile
components.
D
This
is
the
same
request
that
dugan
did
like
few
minutes
ago
when
calling
graph
api
and
only
difference
here,
we
instantiate
graph
services,
let's
go
to
the
graph
services
class,
as
you
can
see
here
when
we
send
a
request
to
graph
a
me
endpoint.
If
there
is
an
error
with
the
status
401,
we
check
the
header.
If
it's
include
the
authenticated
header,
if
it
does,
we
will
handle
the
claim
challenge.
What
do
we
mean
by
handling
claim
challenge?
D
We're
just
gonna
extract
the
cl
that
claim
challenge
from
the
header
and
then
store
it
in
the
session
storage.
Storing
the
claim
challenge
is
optional.
It's
up
to
you
guys.
How
do
you
want
to
handle
it?
Where
do
you
want
to
save
it,
and
how
do
you
want
to
do
it?
In
your
ui,
after
storing
the
clean
challenge,
we'll
pass
the
claim
challenge
to
the
acquired
token
interaction,
which
is
at
this
point
at
the
data
redirect
it
will
re-authenticate
the
user
and
give
him
a
fresh
new
token.
D
We
also
want
to
look
at
the
interceptor,
because
it's
an
important
step
there.
Next
time,
like
the
user,
like
wants
to
acquire
a
new
token,
we'll
check
the
storage
if
it
includes
the
claim,
if
they
claim
it
exists,
we'll
add
it
to
the
acquired
token
and
we
receive
the
right
access
token,
with
the
required
claims
to
access
the
graph
api.
D
B
We
will
skip
the
deployment
steps.
I
would
suggest
we
go
through
the
tutorial
to
to
understand
that,
because
they're
kind
of
out
of
time
we'll
take
any
remaining
questions.
If
you
have
them-
and
I
did
provide
a
link
to
a
code
that
we
have
ready
for
you
to
to
essentially
handle
cae
so
yeah,
if
you
guys
want
to
basically
have
any
remaining
questions,
so
let's
go
through
those
and
we
can.
We
can
then
close
this
session
we
will
publish
the
powerpoint
slide
on
the
yammer
community
channel
question.
A
So
if
you
see
the
current
slide
right
now,
you
can
just
go
to
those
m365
pnp
videos
which
will
have
the
link
as
well
as
follows
on
those
channels,
365,
dev
and
azure
80.
To
get
these
updates
and
one
quick
request
would
be
to
fill
in
the
survey
because
we
will
need
your
responses.
If
you
think
these
are
great
sessions,
you
would
love
such
sessions.
A
A
So
we
have
our
next
call
coming
up
on
september.
15.,
it's
going
to
be
unclaimed,
so
feel
free
to
tune
into
the
same
calendar.
Invite
or
the
link
that
you
have,
and
you
know
we
would
love
to
host
you
there
as
well
and
take
up
your
questions
or
any
other
information
that
you
need
on
claims,
and
here
is
our
calendar.
Invite
for
folks
who
don't
have
it
feel
free
to
download
that,
and
you
know,
join
in
every
third
thursday
of
the
month
and
kalyan
has
shared
the
tutorial
for
you.
Folks.