Sign in to Azure DevOps
The https://dev.azure.com URL redirects to the landing page for the Azure DevOps product. I used to promote this as an URL to use to login to the product. Since this year the page is missing the "Already have an account? Sing in to Azure DevOps" link. As far as I can see there is no way to login to Azure DevOps trough this interface now. There is the usual "sing in" in the top right, which will redirect you to the azure portal (or at least for me it does). How are we supposed to login to Azure DevOps? Old login:
Azure Sign-In Filed: Error code: AADSTS50139
Hi All, When I attempt to authenticate into Azure, I receive the Error code: AADSTS50139. The Error message: AADSTS50139: Session is invalid due to missing an external refresh token. I do not have access to Azure AD and the resolution, I believe, is beyond my capacity. I have contacted Microsoft at (800)-642-7676, Microsoft Support and Azure Support on X, utilized the Azure self help portal, and attempted various login attempts. This probably needs to be resolved by a live representative, but I cannot connect with or get any live support. Does anyone have any suggestions? Thanks, Michael Here are some potential causes and solutions: Mismatched Redirect URI: Cause: The redirect URI provided in the request does not exactly match the one registered in Azure AD for the application. Solution: Ensure that the redirect URI in the application configuration matches exactly with what is registered in Azure AD, including the scheme (http/https), domain, path, and port. Incorrect Configuration in Azure AD: Cause: The application is not correctly configured in Azure AD, or the redirect URI is missing or incorrect in the Azure AD app registration. Solution: Check the Azure AD app registration and make sure the correct redirect URIs are listed under the "Authentication" section. Add the correct URI if it's missing. Case Sensitivity: Cause: Azure AD is case-sensitive for the redirect URI. Solution: Make sure that the case of the redirect URI in the application matches exactly with what is registered in Azure AD. Application Type Mismatch: Cause: The type of application (web, mobile, etc.) may not be set up correctly. Solution: Verify that the application type in Azure AD matches the type of application you are developing. For example, ensure that it's set to "Web" for web applications and "Native" for mobile or desktop applications. Invalid or Missing Permissions: Cause: The application may not have the correct permissions or scopes configured in Azure AD. Solution: Check the API permissions under the Azure AD app registration and ensure that the necessary permissions are granted and admin-consented if required.
Microsoft login page freezes while executing selenium tests in chrome browser
Hi, According to this guide: https://docs.microsoft.com/en-us/azure/app-service/configure-authentication-provider-aad We have created an app registration and configured our application to login with Microsoft. As far as the normal usage is concerned, everything works fine. However, if we are using the login in our automated selenium test suite, we are running into the following problem: We have few test classes that are added in a Azure pipeline as jobs and each of the test classes starts by logging into Microsoft account in a chrome browser to open the application under test. When this pipeline is triggered, one or the other test class fails inconsistently to locate the element(either while entering password/user/clicking on a Sign-in button). Error message: org.openqa.selenium.TimeoutException: Expected condition failed: waiting for visibility of element located by By.id: i0118 (tried for 20 second(s) with 500 milliseconds interval) From the captured screenshot(attached file), we got to know that the login page freezes and never let the test class to run further even if the waiting time is increased. The Microsoft login window shows without rendering any input fields. It doesn't mean that the issue occurs only when the pipeline is triggered, it also occurs when we run the test locally through IDE(IntelliJ). Note: This issue occurs once in a blue moon and if it occurs, it will be consistent over time.
