cancel
Showing results forย 
Search instead forย 
Did you mean:ย 
Data Engineering
Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.
cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

Redirect error in access to web app in Azure Databricks with private front endpoint

FerArribas
Contributor

I have created a workspace with private endpoint in Azure following this guide:

https://learn.microsoft.com/en-us/azure/databricks/administration-guide/cloud-configurations/azure/p...

Once I have created the private link of type browser_authentication and I try to log in to the Web UI and the redirect fails:

AADSTS50011: The redirect URI 'https://centralus-c2.pl-auth.privatelink.azuredatabricks.net/login.html' specified in the request does not match the redirect URIs configured for the application '2ff814a6-3304-4ab8-85cb-cd0e6f879c1d'. Make sure the redirect URI sent in the request matches one added to your application in the Azure portal. Navigate to https://aka.ms/redirectUriMismatchError to learn more about how to fix this.

That redirect url doesn't seem to be allowed in the business application (2ff814a6-3304-4ab8-85cb-cd0e6f879c1d) in Azure AD...

Thanks,

1 ACCEPTED SOLUTION

Accepted Solutions

FerArribas
Contributor

Hi,

We have solved the problem by setting up CNAME type records in our resolver DNS architecture.

Thanks!

View solution in original post

4 REPLIES 4

Debayan
Databricks Employee
Databricks Employee

Hi @Fernando Arribas Jaraโ€‹ , could you please refer to https://learn.microsoft.com/en-us/troubleshoot/azure/active-directory/error-code-aadsts50011-redirec... which talks about the same error.

Anonymous
Not applicable

Hi @Fernando Arribas Jaraโ€‹ 

Hope all is well!

Just wanted to check in if you were able to resolve your issue and would you be happy to share the solution or mark an answer as best? Else please let us know if you need more help. 

We'd love to hear from you.

Thanks!

FerArribas
Contributor

Hi,

We have solved the problem by setting up CNAME type records in our resolver DNS architecture.

Thanks!

flomader
New Contributor II

You don't need a CNAME record.

Go to your private link resource in Azure and click on Settings > DNS Configuration. Make sure you have created private link A records for all the FQDNs listed under 'Custom DNS records'. You have most likely missed one or more of them. 

Connect with Databricks Users in Your Area

Join a Regional User Group to connect with local Databricks users. Events will be happening in your city, and you wonโ€™t want to miss the chance to attend and share knowledge.

If there isnโ€™t a group near you, start one and help create a community that brings people together.

Request a New Group