Description

This article provide API details to add single sign-on tenant user using OSS Tenant ID attribute. 

 

Symptoms

Single Sing-on server already added at tenant / Opco / global scope level in CSO portal.  Refer to https://supportportal.juniper.net/s/article/CSO-How-to-add-Single-Sign-on-server-in-Contrail-Service-orchestration-portal for more details. 

 

Solution

  • Article KB80853 [juniper.net] explains how to create a Single Sign-on server using tenant identifier as "Use OSS Tenant ID" .
  • Update 'OSS Tenant ID' attribute for the tenant  . As show in below screenshot 'Demo' tenant under 'SSOTEST" opco has 'OSS TENANT ID' updated with "ABCD1234". 



image.png







image.png
 
  • Below API can be used to create tenant user through Restful API client. 

URL : https://CSO PORTAL IP/iamsvc/create-user

Method: POST 

X-AUTH-TOKEN [ Header ] :  Opco token / Tenant token . Refer to KB36596 [juniper.net]  for additional details

Body [ raw JSON] : 

{
   "input":{
      "name":"[email protected]",
      "project_role":[
         {
            "oss_tenant_id":"ABCD1234",
            "role_name":"Tenant Admin",
            "project_name":"INTERNAL TESTING"
         }
      ],
      "extra":[
         {
            "str_value":"juniper",
            "name":"last_name"
         },
         {
            "str_value":"test",
            "name":"first_name"
         }
      ]
   }
}

Note: Here predefined role "Tenant Admin" is used to create user. Depending on user requirements, Custom roles need to be created prior to creating user. 
  • Here is the screenshot of Restful API client (Postman) response  once API executed successfully.

image.png
  • Finally verify user created successfully in CSO portal under tenant. 
image.png

NOTE: In Production environments when user created through IDP portal , API with similar format will be sent to the CSO and can be analyzed through Kibana logs. 

Modification History

V1