►
Description
The following improvements and additions to Magento Adobe Stock Integration are demoed in this video:
- Instant test connection
- Expanded image view frontend
- Asset repository WebAPI
The recording contains a presentation of login to Adobe IMS via OAuth
A
A
Okay,
now
I
suppose
you
can
see
my
screen
right
yeah,
we
do
oh
nice,
so,
okay,
what
do
we
have
so
configuration
settings
now
we
have
a
test
connection
button
which
allows
us
to
just
our
API
key,
which
we
have,
which
we
generated
the
other
integration
page
so
how
it
works.
For
example,
let's
assume
that
this
okay,
which
we
already
have
the
API
key,
it's
valid,
so
we
decided
to
test
it.
We
press
the
test
connection
and
just
we
sent
a
request
to
that
double
service
and
let's
just
wait
for
yep.
A
A
Yes,
it's
about
the
correct
results
and
again
we
insert
the
correct
one
and
connection
is
successful.
So,
with
this
functionality
we
provide
for
admin
users,
nice
chance
to
validate
I
pick
it
before
saving
it
and
just
prevent
the
incorrect
behavior
and
the
any
other
page
where
we
will
include
how
functional
chain
so
maybes.
It's
also
mean
I.
B
B
C
A
C
There
is
a
potential
drawback
of
it,
for
instance,
if
he
puts
a
make
a
key,
which
is
when
you
were
saving.
It
was
success,
but
then
later
it
was
revoked
or
invalid
on
the
other
side
and
then,
for
instance,
it
goes
to
the
image
upload
configuration
actually
do
another
section,
a
group
and
trying
to
change
something
there.
This
will
get
potentially
API
key
validation
and
that's
a
question
if
you
want
to
have
such
behavior
or
not
that
we
need
to
consider
like
a
several
use
cases
where,
when
we
we
may
get
this
kind
of
message.
B
A
C
B
A
Okay,
yes,
and
please
head
me
into
this
issue:
I
just
want
to
precipitate
and
I
implement
some
change
requested
ended!
Oh
great!
Thank
you.
Yeah
thanks
thanks,
yeah
I
was
sorry
guys.
One
last
question
maybe
just
had,
but
what
about
having
this
check?
I
mean
this.
That
I
other
be
API
key
or
access.
Token
is
invalid,
for
example,
in
a
log
in
when
admin
begins
to
them.
Magento
admin.
Yes,
just
we
show
at
the
regular
message
that
Samsung
crunk
with
the
Adobe
settings
like
the
same
kind
of
message
as
cache
is
invalid
or
indexers
in.
D
B
A
B
E
A
A
C
Tricky
point
here
is
that
we
have
similar
functionality,
for
instance,
for
the
payment
methods.
Well,
where
you
put
your
credentials
public
these
priorities,
whatever
else
I
have
the
question
is:
do
we
do
the
same
kind
of
validation
on
the
admin
Morgan?
If
not,
should
not
do
the
same
for
the
should
not
introduce
something
called
standing.
B
Yeah
I
agree
with
that.
So
I
doubt
that
we
need
to
kind
of
resist
the
identification.
The
way
we
persisted
about
taxes
about
shipping,
because
definitely
the
use
cases
not
that
critical
doesn't
affect
that.
Like
shopper
experience
at
all,
because
the
kind
of
the
reason
why
we
show
that
message,
taxes
or
shipping
methods
is
because
if
something
is
invalid,
it
will
affect
shopping
experience,
but
with
Adobe
stock.
It's
not
like
that.
So
definitely
the
message
needs
to
be
displayed
on
there
in
the
configuration
area
and
in
media
gallery
when
we
have
either
the
stock
integration.
A
Yeah
actually
another
drawback
that
we
can
have
from
displaymessage
no
pages.
This
performance
goes
to
show,
get
API
keys
and
we'll
it.
We
have
to
perform
request
and
yeah.
So
in
this
case
we
will
have
a
bit
of
a
performance
degradation
just
on
this
stores
configuration
page
and
that
we
are
loading,
movies,
Adobe,
stock
integration,
settings
and
this
it.
D
D
D
In
here
we
do
have
an
assertion
Adobe
stock
and
whenever
we
yeah,
whenever
we
click
on
other
stock,
we
click
on
any
image
and
we
want
to
save
it
though
we
just
click
on
it
and
save
it.
It
closes
the
third
shot
of
a
stock.
It
closes
the
insert,
insert
image
widget,
and
we
see
this
the
only
this
pop-up
for
inserting
an
image.
D
Currently,
it's
actually
inserting
the
preview
image,
though
I
think
this
behavior
should
be
changed
in
the
future,
but
and
and
also
when
you
like,
edit
it
or
something
it's
like
opening
the
standard
magenta
one
instead
of
Adobe.
Maybe
this
is
also
something
to
think
of
and
yeah.
So
one
moment,
I
will
show
you
the
UI
how
it's
working,
mm-hmm,
I,
don't
know
what
my
actually
it's
rewarding
every
time
soon,.
D
So
we
do
have
here
buttons
for
the
next
and
previous.
Basically,
they
are
just
opening
the
next
one
image.
Also,
we
have
a
feature
like
whenever
we
click,
for
example,
for
a
bottom
one
image.
It
automatically
scrolls
you
to
this
image
using
native
functionality
of
browsers.
If
it
doesn't
support
it,
it
will
be
without
the
smooth
effect,
but
it
will
work
the
close
button
and
yeah
on
the
last
one
image.
We
don't
have
a
nice
button
as
well,
so
it
actually
works
with
the
pagination
as
well
with
the
custom
with
static
recognition.
D
So
yeah
I
think
this.
Is
it
from
my
side
not
sure
if
everything
is
correct,
yeah
and
this
this
one?
Actually,
information
is
taken
from
from
the
image
itself.
Currently,
it's
empty
from
admin
panels
from
back
and
sorry.
So
this
is
why
it's
actually
like
the
title
and
by
author
instead
of
actual
informations.
It's
absolutely.
D
A
A
Behavior,
according
to
requirement
so
we'll
implement
our
API
for
saving
image
this
safe
and
he
has
this
a
problem.
They
premature
functionality
will
also
get
some
attributes
required
for
the
front-end
parts.
I
mean
just
tight,
so
it's
about
some
category
name
and
creator,
information
and
yes
well
so
they'll
save
it,
and
so
you
control
can
use
it.
So.
D
C
D
B
D
B
D
It
actually
saves
this
image
this
one
image
in
the
grid.
It
has
a
lower
resolution
that
this
one
image
in
preview.
It
has
a
bit
higher
resolution,
but
we
have
an
original
image
which
is
actually
not
safe
for
now,
because
I'm
pretty
sure
that
I
saw
in
source
codes,
I
saw
that
they
are
coming
with
and
gates,
and
they
are
for
4k
screens
for
5k
screens
and
etc,
and
I'm
pretty
sure
that
instead,
that
this
is
not
the
4k
screen,
so
then
this
is
actually
for
a
preview.
All
this
is
and.
B
The
question
yes
so
and
that
that
is
correct
because
you
save
the
preview.
You
don't
save
the
full
resolution
much
here
so
just
to
understand.
When
you
save
that
image,
it
is
saved
locally
to
magenta
media
knowledge,
whether
it's
like
local,
magenta,
folder
or
CDN,
whatever
is
set
up
or
whatever
actually.
A
B
C
D
A
A
C
A
F
During
the
world
of
this
of
this
pull
request,
I
also
notice
in
the
ACL
permissions.
We
used
to
have
this
item
in
here,
which
belong
to
Adobe
stock
image
Tina's
something
ie
I
had
in
a
previous
pull
request,
so
I
took
time
to
fix
it
and
since
I
was
modifying
all
these
of
this
area,
I'd
change
it
to
to
be
inside
system,
Adobe,
stock
actions,
and
now
it's
part
of
of
the
actions,
no
view
anymore.
F
Thus,
that's
basically
what
these
pull
request
is
about
to
provide
web
api
for
that
obey,
Allah,
bestow
story
as
a
repository
save
as
a
repository
delete
and
they
be
actually
delete
by
ID,
because
we
decided
later
that
belief
was
a
bit
redundant
if
we
have
delete
by
lady
and
we
have
saved
us.
That's
enough!
F
E
Yeah,
first
of
all,
I
working
on
the
issue
is
removing
the
global
label
for
the
text.
Connection
bottom
support
classes
already
market,
there's
a
little
changes.
You
can
check
it
here
so
and
the
second
issue.
This
saves
a
grid
and
spotted
image
state.
So
I
started
working
on
this
issue
and
for
now
it's
in
progress,
so
I
decided
to
reduce
default
Magento
bookmarks,
which
which
about
to
save
the
great
state
in
UI
bookmark,
table
Sao
Paulo
it
works,
but
it
doesn't
save
the
salt,
so
I
need
to
recheck
it
all.
E
E
A
H
A
G
I
think
next,
the
next
big,
the
next
two
milestones
or
that
that
involves
licensing
and
downloading
of
the
licensed
asset
are
going
to
require
some
new
some
new
code
to
be
introduced.
It's
going
to
require
authentication
against
the
Adobe
system,
which,
which
is
not
something
specific
to
stock,
but
is
required
for
pretty
much
accessing
any
any
other
Adobe
service.
G
Now
this
I
recommend
you
know
anyone
who's
interested
in
this
look
at
this.
However,
this
is
again
it's
not
specific
to
stock
and
unfortunately
they
don't
have
sample
code
here
for
PHP,
so
I
created
my
own
documentation
for
stock
and
I
created
some
PHP
sample
code
as
well.
So
some
of
these
things
are
I'll.
Show
you
the
kind
of
out
of
order,
just
know
that
they're
available
and
we'll
figure
out
some
way
to
put
all
the
resources
together
in
one.
G
Maybe
I'll
post
it
to
the
to
the
wiki,
so
you
know
where
to
go
so
this
is
the
general
documentation
in
github
under
the
stock
API
Docs
I
have
a.
This
is
a
document
that
I
created
here
called
stock
authorization
code
workflow
it's
a
PDF,
and
this
takes
goes
through
the
specific
process
of
everything
that
needs
to
be
done
at
a
high
level.
G
What
needs
to
happen
is
and
I'm
not
sure
if
there's
any
model
for
this
in
Magento
today-
and
maybe
some
maybe
you
have
other
integrations
that
do
this,
but
basically
the
man
here
you
said
it
at
a
high
level.
There's
gonna
have
to
be
some
server.
Some
login
page,
the
login
page,
is
going
to
redirect
the
end-user
to
Adobe
to
Adobe
IMS
R,
which
is
our
identity
management
system.
Ims
is
going
to
then
allow
the
person
to
sign
in
and
then
at
when
the
sign-in
is
successful.
G
It'll
it'll
redirect
them
back
to
you
back
to
your
application
and
also
give
you
a
token
that
will
be
good
for
24
hours.
There's
also
a
scheme
for
renewing
the
token,
but
for
your
immediate
need
that
token
can
be
used
to
authorize
that
user.
So
I
have
a
library
is
not
here
and,
as
they
say,
I'll
share
all
these
links
later
I
have
a
bit
bucket
repository
that
has
the
the
actual
PHP
code
and
I
have
an
open
demo
here.
G
So
once
you
install
the
demo
and
you
you
fire
it
up,
you
would
start
here
and
so
what
I'm
going
to
do,
and
actually
what
I'm
going
to
do
here
in
the
side
is
open.
My
console,
because
I'm
also
using
some
PHP
browser
logging,
you
can
see
something
happening
or
see
if
there's
errors,
they'll
say
login
a
Creative
Cloud
and
it
has
now
ordered
me
to
IMS.
G
G
G
In
this
case,
it
didn't
ask
me
for
permission,
because
I
had
already
used
that
I'd
already
given
permission
with
that
email
address
before
now
that
I'm
logged
in
I-
and
you
can't
really
tell
anything
other
than
the
buttons
up
here.
I'm
gonna
prove
that
I'm
logged
in
by
asking
to
get
the
my
stock
quota.
Now,
if
I
were
to
go
to
the
stock
website,
we
can
just
check
that
in
advance
to
make
sure
see
to
see
what
I
will
expect
to
see.
G
G
So
when
I
request
my
quota
from
my
demo
page,
it
should
tell
me
I
have
96
image
credits
available,
I'm
gonna
go
over
here,
I'm
gonna
click
get
quote
up,
it
should
fire
off
a
request,
and
there
it
is
so
in
the
background,
it's
using
that
token
that
I
generated
through
this
login
process
for
the
purpose
of
this
demo
I'm
actually
storing
it
as
a
as
an
HTTP
cookie.
But
these
are
some
designs
that
you
guys
I,
think
particular
Magento
team
may
have
to
think
about
how
this
kind
of
you
know
would
integrate.
G
It
is
using
some
server-side
pieces
to
post
and
do
the
forwarding
to
Adobe
any
to
the
Adobe
IMS
system,
and
you
know
such
such
things
as
like,
where
the
token
is
going
to
be
stored
for
security
purposes.
You
don't
want.
You
know
it
can't
get
out,
because
otherwise
a
user
could
spoof
another
user,
but
yeah
I'm,
I'm
thinking.
G
Perhaps
maybe
you
know
your
UI
designer
may
want
to
take
a
look
at
this
and
try
to
figure
out
what
might
be
best
or
maybe
you
guys
know
if
there's
some
existing
login
patterns
that
you
guys
have
with
other
third-party
integrations
that
you
might
be
able
to
reuse
but
I'm
happy
to
help
with
all
this,
because
this
is
a
more
complex
piece.
I
think,
though,
once
once
it
gets
solved,
it'll
really
help
you
move
quickly,
yeah,
that's
that's
what
I
wanted
to
share.
A
A
Here
so
we
at
the
moment,
we
don't
really
have
any
weapons,
almost
almost
no
open
tasks
in
our
repository
in
the
project,
however,
we're
going
to
add
them
soon,
I
guess
and
we
have
a
lot
of
tasks
in
progress.
The
call
of
the
touch
that
we
have
are
in
progress
given
to
the
work
alone
on
login
implementation
and
saving
a
preview
image.
We
have
big
backlog
of
MMF
TF,
just
coverage
though,
and
it's
available
for
just
to
pick
up
and
work
on
it
and
we,
as
we
are
completing
the
first
milestone
of
project
development.