Producing jwt using postman

First, you need to create an authentication token for a user. You need the login credentials for the user, as well as the API key and secret that you can find by using the ./cells config list command.

Below is an example of an authentication token request on the pydio demo website (login / password: admin / admin, api key / secret : cells-front / cells-front)

  • Create a new POST request to
  • In the Authorization tab, choose Basic Auth and enter cells-front as username and cells-front as password.
  • In the Headers tab, add a header Cache-Control of value no-cache.
  • In the Body tab, choose x-www-form-urlencoded and enter the following fields:
    • grant_type: password
    • username: admin
    • password: admin
    • scope: email profile pydio offline
    • nonce: nonce

Upon success, the request returns a JSON object containing :

  • An access token,
  • A token type,
  • An expiry time,
  • A refresh token,
  • An ID token.

The ID token will be used for subsequent requests to the REST APIs.

Below is an example a REST API request to the config API to list the services running on the system.

  • Create a new GET request to
  • In the Authorization tab, choose Bearer Token and enter the ID token retrieved previously in the Token field.
  • In the Headers tab, add a header Cache-Control of value no-cache.

Automate the token process

First you need to create a environment on postman, follow the screenshots below for detailed steps.

  • Edit Environment: put a name for this env variable

  • Key: put a key for this env like the one used on the screenshot dex_token otherwise you can name it as you wish but you must respect variable naming therefore do not make use of whitespaces and such.

  • Value: You don't have to fill this one, the goal of those steps is to facilitate this process.

You can now put the script that will generate the token and then allocate it to the env variable.

pm.test("Update environment", function () {
    var jsonData = pm.response.json();
    pm.environment.set("dex_token", jsonData.id_token);

Now that our environment variable is created and that the script is associated with the env variable, we need to enable it on the current workspace and to do so select it as seen in this screenshot, the script must be added to the api request for the token, http://<your-cells>/auth/dex/token

Now you have two options to make use of this env variable, change on each of your requests the Bearer token value to {{dex_token}} or you can even automate this a step further and for that follow the steps below.

First add a collection,

now give a name to your collection and configure it to make use of the token env variable previously created,

You need to add your api requests in the collection to be able to make use of the feature.

  • click on the arrow on the right of the word save and choose save as...

then choose the collection previously created and add it into it, when done click on save.

To use the variable for requests and therefore facilitating this step(because you had to copy paste it each time), use the inherit auth from parent in the Authorization tab for each request that you have or will be created within this collection.

And now you just need to run once the token request. Beware this step is mandatory because the token expires after a certain amount of time. It will now be shared with all of your requests abstracting you from copying and pasting everytime.

Back to top