Azure DevOps Board Spoke w/OAuth error: "Identity xxx has not been materialized..."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
We tried to Set up the Microsoft Azure DevOps Boards spoke using OAuth. We configured Azure DevOps by using a current app registration, confirming the values were correct and then creating a new secret. We then created a connection as described and were able to receive an Oauth token successfully.
Then we created an Azure DevOps Instance using that connection alias we just created. When we tried to use the 'Connect' button to test the connection, we received the error message, "Error Message: Cannot establish connection. Please refer logs for more details."
When we checked the Azure Devops Logs, we saw an error that started with "Instance : yyy Azure DevOps, Action : Connect, Message : Cannot establish connection. Please refer logs for more details.; JSON = "<!DOCTYPE html >\r\n<html>\r\n <head>\r\n <title>Identity xxx has not been materialized, please use interactive login over the browser first.</title>\r\n "
Looking up this error, we see advice about using an interactive login to 'materialize' this identity, but principals like we are using don't allow interactive logins.
Troubleshooting:
1. We confirmed the app id, tenant id and secret value are all correct.
2. We tried the URL "https://dev.azure.com" instead - Still able to get an OAuth token, but using the 'Connect' button from the instance form then resulted in an error log with the title "Resource not found".
3. We confirmed the permissions for the Azure app were correct.
Has anyone dealt with this issue previously and found a way around this need for login with a service principal on Azure DevOps?
