Specflow + Living Doc Azure DevOps Login error

[mpgalo]

SpecFlow Version

0.6.964

Which test runner are you using?

SpecFlow+ Runner

Test Runner Version Number

0.6.964

.NET Implementation

.NET 6.0

Project Format of the SpecFlow project

Sdk-style project format

.feature.cs files are generated using

SpecFlow.Tools.MsBuild.Generation NuGet package

Test Execution Method

TFS/VSTS/Azure DevOps – Task – PLEASE SPECIFY THE NAME OF THE TASK

SpecFlow Section in app.config or content of specflow.json

No response

Issue Description

I am trying to access the SpecFlow + LivingDocs plugin on Azure DevOps, but I am unable to authenticate. I have tried using my corporate account and personal account.

Steps to Reproduce

1. Click on Specflow + LivingDoc on Overview Menu on Azure DevOps
2. Click on Sigin with microsoft
3. Inform corporate or personal microsoft account.

Link to Repro Project

No response

[alesacchi]

Hi! I'm having the same issue

[rzuurmond]

I have the same problem today. (08 november 2024). Probably a bug? Saw that the app succeeded to register with my personal microsoft account. But in Azure Devops still have the error.

[jeztaylor01]

Following, I'm also seeing this issue.

[rzuurmond]

Fixed the issue by creating an account manually (not via the microsoft button) via this url:
https://account.specflow.org/Identity/Account/Register?returnUrl=%2F

[timvanelst]

Fixed the issue by creating an account manually (not via the microsoft button) via this url: https://account.specflow.org/Identity/Account/Register?returnUrl=%2F

I ran into the same error, but first login in with a username/ password and then returning to DevOps worked for me too.

[dhansak79]

I am also experiencing this issue and the workaround did not work either.

[mpgalo]

Fixed the issue by creating an account manually (not via the microsoft button) via this url: https://account.specflow.org/Identity/Account/Register?returnUrl=%2F

It doesn’t solve the problem, but it’s a way to work around it. Thank you!

[jameslin-nsp]

We are also experiencing this in our org after not having had an issue for the last year. Any update on this other than the workaround?

[KriTh07]

Hi, has there been any fix for the issue. Multiple users in our org has reported the same!

[sdasa15]

People in my org are experiencing the same and the workaround did not help