Set up OAuth2.0 connection to Workfront for the HTTP modules | Community
Skip to main content
lgaertner
lgaertner
Level 9
February 17, 2025
Solved

Set up OAuth2.0 connection to Workfront for the HTTP modules

  • February 17, 2025
  • 1 reply
  • 608 views

Hello,

I am quite sure, that I successfully did this long time ago, but currently it is not working as expected:


For testing purposes, I would like to set up an OAuth2.0 connection to Workfront for the HTTP modules.
Unfortunately I need some help on setting this up to let the HTTP modules use the access token within their calls.

 

In the connection setup I defined:

Token placement: In the header
Header token name: sessionID


Unfortunately the Fusion DevTools just show

Authorization: "***",

in the header and the API call fails due to an AuthenticationException.


What am I doing wrong?


Thanks in advance.

Regards
Lars

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by monicacardoso

Hi @lgaertner, 

 

Thank you for your question! Can I ask, is there a specific reason that you are using an HTTP connector to connect to Workfront? I am asking because you can use OAuth with the native Workfront modules. If this is because your instance has been migrated to the Adobe Admin Console, you can configure an OAuth app at https://developer.adobe.com/ and use the Authorization header instead of sessionID.

 

https://developer.adobe.com/developer-console/docs/guides/authentication/ServerToServerAuthentication/implementation/ 

 

To explain further, typically the HTTP connector for Workfront doesn't work successfully as it expects the token to be passed in the sessionID header, whereas we follow the standard of passing the token in the Authorization header.

 

However, the good news is that there is a workaround to solve this. You can send the header as a query string (this is an option in the advanced settings when creating the HTTP OAuth connection). 

 

1. Start creating a new HTTP OAuth connection
2. Click Show advanced settings
3. In the Token Placement dropdown, select In the query string
4. For the Query string parameter name, enter sessionID

 

I have included screenshots of my configuration below. Hope this helps! 

 

- Monica

1 reply

M
Adobe Employee
monicacardosoAdobe EmployeeAccepted solution
Adobe Employee
February 27, 2025

Hi @lgaertner, 

 

Thank you for your question! Can I ask, is there a specific reason that you are using an HTTP connector to connect to Workfront? I am asking because you can use OAuth with the native Workfront modules. If this is because your instance has been migrated to the Adobe Admin Console, you can configure an OAuth app at https://developer.adobe.com/ and use the Authorization header instead of sessionID.

 

https://developer.adobe.com/developer-console/docs/guides/authentication/ServerToServerAuthentication/implementation/ 

 

To explain further, typically the HTTP connector for Workfront doesn't work successfully as it expects the token to be passed in the sessionID header, whereas we follow the standard of passing the token in the Authorization header.

 

However, the good news is that there is a workaround to solve this. You can send the header as a query string (this is an option in the advanced settings when creating the HTTP OAuth connection). 

 

1. Start creating a new HTTP OAuth connection
2. Click Show advanced settings
3. In the Token Placement dropdown, select In the query string
4. For the Query string parameter name, enter sessionID

 

I have included screenshots of my configuration below. Hope this helps! 

 

- Monica

_Manish_Singh
_Manish_Singh
Level 9
July 31, 2025

Hello @monicacardoso, Is it possible to establish the connection on behalf of another user / service account, let's say 'Integration Bot'?

Terms & ConditionsAccessibility statement

Loading footer...