NS1 Status

Articles in this section

Managing operator users

  • Updated
Follow

After bootstrapping, you can add additional operator users to the system. An operator user has full access to every operation and all system data.

NOTE
NS1 highly recommends adding a second operator user. Otherwise, if there are no other operators and the original operator's API key is lost, the system is rendered unmanageable and a new instance must be deployed.

Logging in for the first time as an operator user

In the same way an operator can use the API on behalf of the organization, they can also sign into the Private DNS/DDI portal by adding an exclamation mark (!) and organization ID to the operator username on the login page (https://$CORE_CONTAINER). Use your operator password created during setup. For example:

Username: $OPERATOR_USERNAME!$ORG_ID

An operator signing into the portal on behalf of an organization is required to provide a two-factor authentication (2FA) token. This secret token was returned in response to creating the operator. The token is generated via any six-digit TOTP generator that refreshes at 30-second intervals.

Viewing operators

curl -k -X GET \
https://$CORE_HOST_IP/v1/ops/operators/$OPERATOR_ID \
-H "X-NSONE-Key: $OPERATOR_KEY"

Adding an operator

curl -X PUT \
https://$CORE_HOST_IP/v1/ops/operators \
-H "X-NSONE-Key: $OPERATOR_KEY" \
-d '{
"user": "operator",
"name": "Operator Name",
"email": "ops@email.com",
"password": "mypassword"
}'

Updating operator settings

curl -k -X POST \
https://$CORE_HOST_IP/v1/ops/operators/$OPERATOR_ID \
-H "X-NSONE-Key: $OPERATOR_KEY" \
-d '{
"name": "Updated Name",
"email": "updated_name@email.com"
}'

Deleting an operator

curl -k -X DELETE \
https://$CORE_HOST_IP/v1/ops/operators/$OPERATOR_ID \
-H '"X-NSONE-Key: $OPERATOR_KEY"

 

NOTE
Operators cannot delete their own accounts from the system. Bootstrapping system users is a one-time event.

Related articles