Documentation

Sub-Account Creation

Please be aware, that you need a license to use this feature and create sub-accounts. Only using an admin user in the SSO token will allow to use this function.
 
Below you see a token payload example:
 

{
 "iss": "org",
 "aud": "",
 "jti": "9xSRwHnWjyAAo06_iHlxbw",
 "iat": 1611828320,
 "sub": "admin@customer.com",
 "userType": "ADMIN"
 }

 

URL:

 

https://datapine.com/organization/{organization_id}/accounts/register?token=eyJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJvcmciLCJhdWQiOiIiLCJqdGkiOiI5eFNSd0huV2p5QUFvMDZfaUhseGJ3IiwiaWF0IjoxNjExODI4MzIwLCJzdWIiOiJhZG1pbkBjdXN0b21lci5jb20iLCJ1c2VyVHlwZSI6IkFETUlOIn0.rLbAzqQ_eonMr05bYfWJ25AN8dXrG1GgvRurArKJAJc

 

Method: POST
Request parameters: token

Request Body:

 

{
    "accountConfig": {
        "user": "client1@customer.com",
        "password": "XXXXXXX",
        "organizationName": "client1"
    },
    "planConfig": {
        "numberOfUsers": 5,
        "numberOfViewers": 15,
        "numberOfPowerViewers": 5
    },
    "ssoConfig": {
        "remoteLoginUrlMap": {
            "default": "https://customer/remote/login/sso"
        }
    }
}

 

The payload is divided into 3 sections:
 
1. accountConfig: Configuration related to the new datapine account and admin access: user, password, and organization name.

 

2. planConfig: Configuration related licenses in the new account. Here you can specify the number of users (admins & editors), number of viewers, and number of power viewers.

 

3. ssoConfig: The external application has an intranet portal where the datapine application has been embedded. The objective is that logged in users  in the external portal can access datapine without being prompted with a login form, leveraging, therefore, an SSO authentication. If the new account has a different SSO endpoint to get the token, you can set it up in this section. Just change the value in default for the new URL.

 

Request Response:

 

{
    "accountConfig": {
        "user": "client1@customer.com",
        "password": "XXXXXXX",
        "organizationName": "client1"
    },
    "planConfig": {
        "numberOfUsers": 5,
        "numberOfViewers": 15,
        "numberOfPowerViewers": 5
    },
    "ssoConfig": {
        "remoteLoginUrlMap": {
            "default": "https://customer/remote/login/sso"
        }
    }
}

 

In case you configure SSO for the new account, we return the secret which is, by default, the same as in your main account and the new iframe link.