Adobe  I/O Creating a JSON Web Token

Creating a JSON Web Token

A JSON web token for Service Account authentication requires a particular set of claims, and must be signed using a valid digital signing certificate. We recommend that you use one of the publicly available libraries or tools for building your JWT. Examples are provided for some popular languages.

Required Claims for a Service Account JWT

Your JWT must contain the following claims:

Claim Description
exp Required. The expiration parameter is a required parameter measuring the absolute time since 01/01/1970 GMT. You must ensure that the expiration time is later than the time of issue. After this time, the JWT is no longer valid. An expiration period is typically one day.
iss Required. The issuer, your organization ID in the format org_ident@AdobeOrg. Identifies your organization that has been configured for access to the Adobe I/O API.
sub Required. The subject, your API client account ID in the format:
aud Required. The audience for the token, in the format:
configured claims Required. The API-access claim configured for your organization:
jti Optional. A unique identifing string for the token, if configured for your organization. If required, you must use a string created from a decimal number greater than any valued used before, in order to prevent replay attacks. Otherwise, the request fails. To ensure an acceptable value, you can convert the current Unix time (seconds since 1970) to a string.

The following is a sample payload to be signed and encoded.

  "sub": "",
  "iss": "8765432DEAB65@AdobeOrg",
  "exp": 1473901205,
  "aud": "",
  "": true,
  "jti": "1470000000"

Sign and Encode your JWT

The JWT must be signed and base-64 encoded for inclusion in the access request. The JWT libraries provide functions to perform these tasks.

  • The token must be signed using the private key for a digital signing certificate that is associated with your API key. You can associate more than one certificate with an API key. If you do so, you can use the private key of any associated certificate to sign your JWT. For more information, see Public Key Certificates for JWT.
  • Adobe supports RSASSA-PKCS1-V1_5 Digital Signatures with SHA-2. The JWS algorithm ("alg") parameter value can be RS256, RS384, or RS512.

Using JWT Libraries and Creation Tools

Most modern languages have JWT libraries available. We recommend you use one of these libraries (or other JWT-compatible libraries) before trying to hand-craft the JWT.

Other JWT tools are publicly available, such as the JWT decoder, a handy web-based decoder for Atlassian Connect JWTs.

Examples are provided for several popular languages.

JWT Libraries
Language Library Example

atlassian-jwt jsontoken

Creating JWTs for Java Apps


Creating JWTs for Node.js Apps


For an example Python script that creates a JWT, see the User Management Walkthrough.


Additional JWT Libraries and Creation Tools

The following JWT libraries are available, in addition to the Java, Node.js, and Python libraries for which we have provided examples.

JWT Libraries
Language Library
Ruby ruby-jwt
PHP firebase php-jwt luciferous jwt
.NET jwt
Haskell haskell-jwt