• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

OAuth credentials not linked as paid subscription after migration

Community Beginner ,
Sep 21, 2023 Sep 21, 2023

Copy link to clipboard

Copied

We have a paid PDF Service API license subscribed via AWS Marketplace and been using Node SDK and JWT credentials to make API calls. This is the original code before migration:

const credentials =
  PDFServicesSdk.Credentials.serviceAccountCredentialsBuilder()
    .withClientId(JWT_CLIENT_ID)
    .withClientSecret(JWT_CLIENT_SECRET)
    .withOrganizationId(ORG ID)
    .withAccountId(ACCOUNT_ID)
    .withPrivateKey(PRIVATE_KEY)
    .build();

Using the servicePrincipalCredentialsBuilder() is the "new" way based from the sample code provided so we used this together with the OAuth Server-to-Server credentials and our code now looks like this:

// NEW_CLIENT_ID and NEW_CLIENT_SECRET came from the new OAuth Server-to-Server Credentials
 const credentials =
    PDFServicesSdk.Credentials.servicePrincipalCredentialsBuilder()
      .withClientId(NEW_CLIENT_ID)
      .withClientSecret(NEW_CLIENT_SECRET)

However, after a few days we started to receive this error "Either quota for this operation is not available or Free Tier quota is exhausted. Please visit (www.adobe.com/go/pdftoolsapi_home) to start using Free Tier quota or (www.adobe.com/go/pdftoolsapi_err_quota) to upgrade to paid credentials." which appears that the OAUTH credentials is linked as a Free Tier and was not associated to the paid license.

 

Shouldn't the credentials be tied under the registered Adobe email? Also, is my understanding correct that we should discontinue using the JWT_CLIENT_ID and JWT_SECRET_KEY?

Screenshot 2023-09-15 142511.png

Please advise.

TOPICS
Document Generation API , Node.js SDK , PDF Services API , Sales and Licensing

Views

310

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
community guidelines
Community Beginner ,
Oct 04, 2023 Oct 04, 2023

Copy link to clipboard

Copied

anyone?

Votes

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
community guidelines
Adobe Employee ,
Oct 05, 2023 Oct 05, 2023

Copy link to clipboard

Copied

Your original way of paying us, via AWS, is no longer supported. If you need more transactions than the free tier supports, you have to contact sales for a contract. You can do so here: https://developer.adobe.com/document-services/pricing/contact/sales/

Votes

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
community guidelines
Community Beginner ,
Oct 05, 2023 Oct 05, 2023

Copy link to clipboard

Copied

@Raymond Camden the issue is that the OAuth Server-to-Server credentials is under free tier but the Service Account (JWT) isn't but both are under the same adobe id.

Votes

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
community guidelines
Adobe Employee ,
Oct 06, 2023 Oct 06, 2023

Copy link to clipboard

Copied

I'm not sure what you mean. Both sets of credentials can be free tier or paid, depending on how set up. You need to make _new_ credentials, and I'd recommend OAuth as the JWT is deprecated. You also need to reach out to sales to get a new contract.

Votes

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
community guidelines
Community Beginner ,
Oct 08, 2023 Oct 08, 2023

Copy link to clipboard

Copied

@Raymond Camden that is correct. JWT is going to be deprecated by January 2025 so we wanted to switch to OAuth this year. We are getting billed thru AWS by $0.05 per api call to the AWS PDF Service API and do not encounter any limits with JWT. We are assuming that using OAuth should still continue to work and be billed per api call under the existing AWS subscription. Is that correct?

Votes

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
community guidelines
Adobe Employee ,
Oct 09, 2023 Oct 09, 2023

Copy link to clipboard

Copied

LATEST

No, that is not correct. To be clear, AWS billing is gone. You cannot pay that way. 


You must either use the free tier, or switch to a new sales contract.

Votes

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
community guidelines
Resources