Azure Question posted in
The official documentation to get you started can be found here.

Azure – why we need to create a token before applying Token permissions in databricks

We want to enable the access for the users to create token.

Now, I have logged in to the databricks account using the admin access, and I go to "Access Control" -> "Personal Access Tokens" and I want to enable the access to the users so that they can create token. But I see that button to enable the settings is disabled and it shows a msg on hovering that "Token permissions can be set only if at least one token has been created in the workspace."

enter image description here

Now, my question is why this sort of pre-condition is added. When all I have to do is enable my users to be able to use token, then why do I need to create a token first which is of no use.

Is this a bug or a desired functionality. If yes, then whats the reason behind it.

Tags:

2

Answers


  1. 0

    There might be quite a few reasons for this,the requirement to create at least one token before enabling token permissions is mostly for a design choice to ensure that the token creation process is functional, trackable for auditing purposes. it can make sure that only authorized admin user with enough privileges are enabling token permissions as a security measure.

    Login or Signup to reply.
  2. 0

    Yes, that is due to Testing and Verification of tokens.

    Before allowing token creation for other users, the system want to confirm that the token creation process functions properly. By requiring the creation of at least one token, it ensures that the system has been tested and operates as anticipated.

    Initially, it will ask you to create the token. Afterwards, even if you revoke the token, you can still use Permission Settings.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search