cancel
Showing results for 
Search instead for 
Did you mean: 
Machine Learning
cancel
Showing results for 
Search instead for 
Did you mean: 

Registered models - edit creator

thibault
Contributor

Hi!

I'm using MLFlow API to log and load models in Databricks. When we created a dedicated workspace for models registry, one person created multiple models, and for some reason now all models are logged with this person as the creator.

This person no longer exists in Databricks and we removed their user. All jobs using these models failed with a 403 error so we restored the user. Is there a way to change the creator of models in Databricks to, e.g., a service principal?

1 ACCEPTED SOLUTION

Accepted Solutions

Kaniz
Community Manager
Community Manager

Hi @thibault , Hello! It seems you’re dealing with a situation where the original creator of multiple models in your Databricks workspace no longer exists, and you’d like to change the creator to a service principal.

 

Let’s address this step by step:

 

Create a Databricks Service Principal:

  • In your Databricks workspace, click your username in the top bar and select “Manage account.”
  • Alternatively, you can directly go to your Databricks account console at this link.
  • Sign in to your Databricks account if prompted.
  • Navigate to “User management” and click on the “Service principals” tab.
  • Add a new service principal by providing a name for it.
  • Optionally, assign account-level permissions to the service principal.

Add the Service Principal to Your Databricks Workspace:

  • Once you’ve created the service principal, add it to your target Databricks workspace.
  • Ensure that the service principal has the necessary workspace permissions.

Assign Workspace-Level Permissions to the Service Principal:

  • Specify the roles and permissions that the service principal should have within the workspace.

Generate a Databricks Personal Access Token (PAT):

  • This token will allow the service principal to represent itself programmatically in calls from tools, scripts, and SDKs.
  • Use the service principal to generate its own Databricks PAT.

By following these steps, you’ll be able to use the service principal effectively for model management and avoid any issues related to the original user who no longer exists. Remember that using a service principal provides benefits such as independent resource access, better token protection, and easier management. Good luck! 🚀🔑

View solution in original post

1 REPLY 1

Kaniz
Community Manager
Community Manager

Hi @thibault , Hello! It seems you’re dealing with a situation where the original creator of multiple models in your Databricks workspace no longer exists, and you’d like to change the creator to a service principal.

 

Let’s address this step by step:

 

Create a Databricks Service Principal:

  • In your Databricks workspace, click your username in the top bar and select “Manage account.”
  • Alternatively, you can directly go to your Databricks account console at this link.
  • Sign in to your Databricks account if prompted.
  • Navigate to “User management” and click on the “Service principals” tab.
  • Add a new service principal by providing a name for it.
  • Optionally, assign account-level permissions to the service principal.

Add the Service Principal to Your Databricks Workspace:

  • Once you’ve created the service principal, add it to your target Databricks workspace.
  • Ensure that the service principal has the necessary workspace permissions.

Assign Workspace-Level Permissions to the Service Principal:

  • Specify the roles and permissions that the service principal should have within the workspace.

Generate a Databricks Personal Access Token (PAT):

  • This token will allow the service principal to represent itself programmatically in calls from tools, scripts, and SDKs.
  • Use the service principal to generate its own Databricks PAT.

By following these steps, you’ll be able to use the service principal effectively for model management and avoid any issues related to the original user who no longer exists. Remember that using a service principal provides benefits such as independent resource access, better token protection, and easier management. Good luck! 🚀🔑

Welcome to Databricks Community: Lets learn, network and celebrate together

Join our fast-growing data practitioner and expert community of 80K+ members, ready to discover, help and collaborate together while making meaningful connections. 

Click here to register and join today! 

Engage in exciting technical discussions, join a group with your peers and meet our Featured Members.