JWT to OAuth | Community
Skip to main content
V
VinceCa3
New Participant
May 10, 2024
Question

JWT to OAuth

  • May 10, 2024
  • 3 replies
  • 1393 views

Received an email stating Adobe is deprecating the Service Account (JWT) credentials in favor of the OAuth Server-to-Server credentials, and that we have a project affected by this and the (JWT) credentials need to be migrated to use the OAuth Server-to-Server credential.

 

I completed step 1 to add an equivalent OAuth server-to-server credential to my project, then generated a required access token.  However, the application I'm trying to connect to Adobe from is asking for a Private Key.  And I don't see anything under credential details for this.

 

Where do I find this last piece so I can test?

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

3 replies

tmj
tmj
Employee
May 27, 2024

Hello, could you specify which of your integration or application uses the Service Account (JWT) credential? Without this information we are unable to guide you. 

V
VinceCa3Author
New Participant
May 28, 2024

Ivanti Neurons for Discovery

tmj
tmj
Employee
May 28, 2024

We recommend you contact the vendor (Ivanti) to ask them when they'll support OAuth Server-to-Server credentials. Adobe cannot do much more to help. 

 

Also, read our documentation on migrating vendor applications.

Thanks
Manik

abhinavpuri
abhinavpuri
New Participant
May 15, 2024

Hi @vinceca3 - 

Since you've haven't shared details on the Application that is asking for Private key I can share generic context - 
We have recently migrated 50+ Adobe IO integrations from JWT credentials to OAuth credentials and noticed that some integrations were configured in developer console to work with third-part Apps (Example Google Search Ads 360 also known as SA360), these integrations are built and maintained by Vendor and can only support OAuth 2.0 credentials once they have this feature/capability released/developed. In these case the dependency is on third-party platform to support new credentials system. 

    D
    DuanePf
    New Participant
    May 13, 2024

    I found out I just need to call ServicePrincipalCredentialsBuilder() instead of ServiceAccountCredentialsBuilder() to use the new OAuth method:

     

    Credentials credentials = Credentials.ServicePrincipalCredentialsBuilder() .WithClientId(ClientID) .WithClientSecret(ClientSecret) .Build(); // Credentials credentials = Credentials.ServiceAccountCredentialsBuilder() // .WithPrivateKey(@"-----BEGIN RSA PRIVATE KEY----- // " + adobeKey + @" // -----END RSA PRIVATE KEY-----") // .WithClientId(ClientID) // .WithClientSecret(ClientSecret) // .WithOrganizationId(OrgID) // .WithAccountId(AccountID) // .Build();

     

      Terms & ConditionsAccessibility statement

      Loading footer...