Granting Access to the Secrets Tab

ENTERPRISE

Granting access to the Secrets tab

You can grant users access to the Secrets tab. By default, new users have no permissions.

NOTE: This procedure grants full user access to the Secrets tab. If you want to configure fine-grained user access, see the documentation.

Grant Access by using the UI

Prerequisites:

  • A DC/OS user account without the dcos:superuser permission.
  1. Log into the DC/OS UI as a user with the superuser permission.

    Login

    Figure 1. DC/OS UI login

  2. Select Organization and choose Users or Groups.

  3. Select the name of the user or group to grant the permission to.

    Add user or group for granting permissions Figure 2. Select user or group to grant permissions to

  4. From the Permissions tab, click ADD PERMISSION.

  5. Click INSERT PERMISSION STRING to toggle the dialog.

    Add permission

    Figure 3. Insert Permission String

    Disabled

    1. dcos:adminrouter:secrets full
    2. dcos:secrets:list:default:/ read
  6. Copy and paste the permission in the Permissions Strings field. Choose the permission strings based on your security mode and click ADD PERMISSIONS and then Close.

    Permissive

    1. dcos:adminrouter:secrets full
    2. dcos:secrets:list:default:/ read

    Strict

    1. dcos:adminrouter:secrets full
    2. dcos:secrets:list:default:/ read

Granting Access by using the API

Prerequisites:

Tips:

  • Service resources often include / characters that must be replaced with %252F in curl requests, as shown in the examples below.
  • When using the API to manage permissions, you must create the permission before granting it. If the permission already exists, the API will return an informative message and you can continue to assign the permission.

Permissive

  1. Create the permission.

    1. curl -X PUT --cacert dcos-ca.crt \
    2. -H "Authorization: token=$(dcos config show core.dcos_acs_token)" \
    3. -H 'Content-Type: application/json' \
    4. $(dcos config show core.dcos_url)/acs/api/v1/acls/dcos:adminrouter:secrets \
    5. -d '{"description":"Grants access to the contents of the Secrets tab"}'
  2. Grant the following privileges to the user uid.

    1. curl -X PUT --cacert dcos-ca.crt \
    2. -H "Authorization: token=$(dcos config show core.dcos_acs_token)" \
    3. $(dcos config show core.dcos_url)/acs/api/v1/acls/dcos:adminrouter:secrets/users/<uid>/full

NOTE: To grant this permission to a group instead of a user, replace /users/"uid" with /groups/"gid".

Strict

  1. Create the permission.

    1. curl -X PUT --cacert dcos-ca.crt \
    2. -H "Authorization: token=$(dcos config show core.dcos_acs_token)" \
    3. -H 'Content-Type: application/json' \
    4. $(dcos config show core.dcos_url)/acs/api/v1/acls/dcos:adminrouter:secrets \
    5. -d '{"description":"Grants access to the contents of the Secrets tab"}'
  2. Grant the following privileges to the user uid.

    1. curl -X PUT --cacert dcos-ca.crt \
    2. -H "Authorization: token=$(dcos config show core.dcos_acs_token)" \
    3. $(dcos config show core.dcos_url)/acs/api/v1/acls/dcos:adminrouter:secrets/users/<uid>/full

NOTE: To grant this permission to a group instead of a user, replace /users/"uid" with /groups/"gid".