User doesn't see consent screen after login and also no profile data for Adobe Stock Integration

Apr 22, 2020

Copy link to clipboard

Copied

Hi,

We have created an Adobe Stock integration using OAuth2 in console.adobe.io. And we followed this tutorial - https://www.adobe.io/authentication/auth-methods.html#!AdobeDocs/adobeio-auth/master/OAuth/OAuth.md

 

But after login, the user doesn't see any consent screen and Adobe goes directly to the finish redirect uri with the code parameter. Also in the token call which we execute immediately after, we don't receive user profile data - there is no "email" or "name" fields. The response to https://ims-na1.adobelogin.com/ims/token/ call is: {"access_token":".....","refresh_token":".....","sub":".....@AdobeID","token_type":"bearer","expires_in":86399984}.

As you can see there are no user profile data fields at all. But in the above tutorial there are such fields.

 

Also the user doesn't see the connected integration in the connected applications list in his profile.

 

What could be the reason for these 3 issues? Otherwise the tokens work and we can retrieve user's licensed images - but issues are there is no consent screen, there is no user profile data returned and the integration is not shown in connected apps lists in user's profile.

 

Thank you in advance!

Hi!

 

This is a relatively complex topic, so I will try to break down what you are seeing. But the short answer is that you need to create a "Creative SDK" integration instead of an "Adobe Stock" integration in Adobe IO. Or you can edit your existing integration and add Creative SDK to it. This should resolve everything. 

 

Furthermore, I suggest you look at the specific OAuth workflow guide I created for Adobe Stock. It also addresses some of your questions:

https://github.com/adobe/stock-api-docs/blob/master/supplemental/Stock-Authorization-Code-Workflow.pdf

 

  • User doesn't see consent screen.
    • This is expected because the Adobe Stock integration does not support this workflow, only the Creative SDK integration type does. The Stock integration should not be used if you need to give/revoke permission. It is mainly there only for search integrations (not for authentication).
  • User profile not received.
    • Stock integration does not have the necessary scopes to access a user's profile, because that data resides outside Adobe Stock. In OAuth, you must specify the permissions you need to access. The Creative SDK has a "metascope" that includes not only permissions for Adobe Stock, it gives access to all Creative Cloud applications and the user profile. This information is not available with the Stock integration type alone.
  • Integration not listed under user's profile.
    • Again, the Adobe Stock integration type does not have any link to the user profile, only the Creative SDK scope has this ability. So it does not show up in the user's Adobe profile, and therefore cannot be revoked (because it also cannot ask for permission).

 

If your use case is 100% internal to your company, then the Adobe Stock integration type is okay to use, because you can get user permission and data from them through other means. But if your use case requires you to sign in users who are not part of your company, then the Creative SDK type is what you should use instead.

 

If you have additional questions, please email stockapis@adobe.com.

 

Thanks,

Christopher

TOPICS
Troubleshooting

Views

153

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

User doesn't see consent screen after login and also no profile data for Adobe Stock Integration

Apr 22, 2020

Copy link to clipboard

Copied

Hi,

We have created an Adobe Stock integration using OAuth2 in console.adobe.io. And we followed this tutorial - https://www.adobe.io/authentication/auth-methods.html#!AdobeDocs/adobeio-auth/master/OAuth/OAuth.md

 

But after login, the user doesn't see any consent screen and Adobe goes directly to the finish redirect uri with the code parameter. Also in the token call which we execute immediately after, we don't receive user profile data - there is no "email" or "name" fields. The response to https://ims-na1.adobelogin.com/ims/token/ call is: {"access_token":".....","refresh_token":".....","sub":".....@AdobeID","token_type":"bearer","expires_in":86399984}.

As you can see there are no user profile data fields at all. But in the above tutorial there are such fields.

 

Also the user doesn't see the connected integration in the connected applications list in his profile.

 

What could be the reason for these 3 issues? Otherwise the tokens work and we can retrieve user's licensed images - but issues are there is no consent screen, there is no user profile data returned and the integration is not shown in connected apps lists in user's profile.

 

Thank you in advance!

Hi!

 

This is a relatively complex topic, so I will try to break down what you are seeing. But the short answer is that you need to create a "Creative SDK" integration instead of an "Adobe Stock" integration in Adobe IO. Or you can edit your existing integration and add Creative SDK to it. This should resolve everything. 

 

Furthermore, I suggest you look at the specific OAuth workflow guide I created for Adobe Stock. It also addresses some of your questions:

https://github.com/adobe/stock-api-docs/blob/master/supplemental/Stock-Authorization-Code-Workflow.pdf

 

  • User doesn't see consent screen.
    • This is expected because the Adobe Stock integration does not support this workflow, only the Creative SDK integration type does. The Stock integration should not be used if you need to give/revoke permission. It is mainly there only for search integrations (not for authentication).
  • User profile not received.
    • Stock integration does not have the necessary scopes to access a user's profile, because that data resides outside Adobe Stock. In OAuth, you must specify the permissions you need to access. The Creative SDK has a "metascope" that includes not only permissions for Adobe Stock, it gives access to all Creative Cloud applications and the user profile. This information is not available with the Stock integration type alone.
  • Integration not listed under user's profile.
    • Again, the Adobe Stock integration type does not have any link to the user profile, only the Creative SDK scope has this ability. So it does not show up in the user's Adobe profile, and therefore cannot be revoked (because it also cannot ask for permission).

 

If your use case is 100% internal to your company, then the Adobe Stock integration type is okay to use, because you can get user permission and data from them through other means. But if your use case requires you to sign in users who are not part of your company, then the Creative SDK type is what you should use instead.

 

If you have additional questions, please email stockapis@adobe.com.

 

Thanks,

Christopher

TOPICS
Troubleshooting

Views

154

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Apr 22, 2020 0
Adobe Employee ,
Apr 22, 2020

Copy link to clipboard

Copied

Hi!

 

This is a relatively complex topic, so I will try to break down what you are seeing. But the short answer is that you need to create a "Creative SDK" integration instead of an "Adobe Stock" integration in Adobe IO. Or you can edit your existing integration and add Creative SDK to it. This should resolve everything. 

 

Furthermore, I suggest you look at the specific OAuth workflow guide I created for Adobe Stock. It also addresses some of your questions:

https://github.com/adobe/stock-api-docs/blob/master/supplemental/Stock-Authorization-Code-Workflow.p...

 

  • User doesn't see consent screen.
    • This is expected because the Adobe Stock integration does not support this workflow, only the Creative SDK integration type does. The Stock integration should not be used if you need to give/revoke permission. It is mainly there only for search integrations (not for authentication).
  • User profile not received.
    • Stock integration does not have the necessary scopes to access a user's profile, because that data resides outside Adobe Stock. In OAuth, you must specify the permissions you need to access. The Creative SDK has a "metascope" that includes not only permissions for Adobe Stock, it gives access to all Creative Cloud applications and the user profile. This information is not available with the Stock integration type alone.
  • Integration not listed under user's profile.
    • Again, the Adobe Stock integration type does not have any link to the user profile, only the Creative SDK scope has this ability. So it does not show up in the user's Adobe profile, and therefore cannot be revoked (because it also cannot ask for permission).

 

If your use case is 100% internal to your company, then the Adobe Stock integration type is okay to use, because you can get user permission and data from them through other means. But if your use case requires you to sign in users who are not part of your company, then the Creative SDK type is what you should use instead.

 

If you have additional questions, please email stockapis@adobe.com.

 

Thanks,

Christopher

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 22, 2020 1
Apr 22, 2020

Copy link to clipboard

Copied

Hi,

Thank you very much, Christopher! It works now 🙂

As a suggestion -> Maybe your detailed pdf could be linked in the official docs below, cause as a newcomer to the API, I found it very hard to understand that I need to create a CreativeSDK, and not an AdobeStock.

https://www.adobe.io/authentication/auth-methods.html#!AdobeDocs/adobeio-auth/master/OAuth/OAuth.md

https://www.adobe.io/authentication/auth-methods.html#!AdobeDocs/adobeio-auth/master/OAuth/Scopes.md

 

Thanks again and have a nice day!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 22, 2020 0
Resources
Buy Adobe Stock
Getting Started