Client namespace

This section is optional and only applicable if you want to separate user-related data

Client namespaceClient namespace - Client Namespace is our way of logically separating data. is Minna's way of logically separating data. All user-related data is stored in a client namespace. An access token is always tied to one specific namespace and cannot be used to access data from another namespace. If no namespace is explicitly stated, the default namespace is used. In order to enable the use of client namespace, Minna needs to configure your client keyclient key - When you are registered for the use of Minnas products and services, a ClientKey is inserted in Minnas system to represent you as a customer, specifying for example your access rights and permissions. access and enable this feature.

📘

Note: To enable the usage of client namespaces, please reach out to us.

Client namespace allows you to segment user-related data by whatever criteria you choose (for example, per bank branch). To do this, you can provide the clientNamespace parameter when getting an access token. Then, all resources created with that access token will belong to that client namespace.

Example of JWT body for getting access token, with an explicit namespace:

{
  "aud" : [ "minna.tech" ],
  "exp" : 1574766146,
  "nbf" : 1574766086,
  "clientKeyId" : "<client_key_id>",
  "clientNamespace": "branch1"
}

❗️

Allowed clientNamespace characters

Please note that only alphanumeric characters (a-z or A-Z and 0-9), underscore (_) and hyphen(-) are allowed for clientNamespace.


Did this page help you?