Generate Intemporal token

Unlike regular tokens, which expire after a set duration, intemporal tokens remain valid indefinitely, making them especially valuable for integrations and third-party systems.

WARNING

In order to generate an intemporal token you need to have the permission token:generate or be a system user.

TIP

It's advisable to create a new user for each third-party system instead of consistently using the same user account.

1. Authenticate with a user that has priviledges for that:

# request
curl --location --request POST 'https://<server>/recordm/security/auth' \
--header 'Content-Type: application/json' \
--data-raw '{
    "username": "<your_username>",
    "password": "<your_password>"
}'

# response
{
    "securityToken": "abc123....."
}

2. Request a intemporal token for a user:

Specify the user you want to assign an intemporal token to in the payload.

# request
curl --location --request POST 'https://<server>/recordm/security/token' \
--header 'Content-Type: application/json' \
--header 'Cookie: cobtoken=abc123.....' \
--data-raw '{
    "username": "<the_user_for_the_intemporal_token>"
}'

# response with an intemporal token
{
    "securityToken": "intemporal token for another_username ..."
}

The token returned in the second request is an intemporal token that will be associated to the provided user.

WARNING

It's not possible to invalidate intemporal tokens. Invalidating an intemporal token means that you need to disable the associated user.