Using Postman with Maskinporten JWT-grants

This is short how-to on using Postman towards APIs secured by Maskinporten, includingDigitaliseringsdirektoratets self-service APIs. A small standalone tool is used to generate the JWT-grant and exchange it for an access token. This access token is then used as a bearer token in Postman.

Postman is a great tool, but it does not support the JWT authorization grants per RFC 7523 required by Maskinporten.

The general process to use Postman towards an API secured with Maskinporten is:

  1. Use a standalone tool to generate a JWT and exchange it for an access token
  2. Paste this token into Postman as a bearer token before performing API operations

1. Configure the generator

Download the JWT grant generator from

Create a keystore (JKS) holding your business certificate (“virksomhetssertifikat”) keypair. Both the certificate and private key should be included in the JKS. The certificate should be the one use for signing (not non-repuditation). The JKS should look similar to the figure below in Keytool Explorer: keytool screenshot.

Configure the properties file with correct settings, ie passwords to the keystore and private key, your clientid, and the ìdentifier of Maskinporten for the environment you’re using.

Configure the properties file with the scope for the API you want to access (ForDigitaliseringsdirektoratets self-service APIs, the relevant scopes are idporten:dcr.write and for integration management, and idporten:scopes.write for API management).

2. Obtain access token

Run the generator - it will generate a JWT, send it to Maskinporten, and return an access token

run_generator screenshot

(note that on this platform, the padding character is escaped.)

If the call fails, Maskinporten will in most cases return an explanatory error message.

More obscure errors are typical coming from using the wrong certificate, or trying to use the public key instead of the private key for signing the JWT (keystore.alias pointing to wrong alias)

3. Configure Postman

Open Postman and create a new Collection. Set the Authorization type to Bearer token and paste in the access token returned by the generator (note that you might need to replace \u00d3 with the equal sign = on some platforms):

configure collection screenshot

Under the new Collection, create a new Request:

new request screenshot

Make sure the request inherits the authenication settings from the parent Collection:

request detail screenshot

You shall now be able to use the API.