Can't integrate Rider with Azure DevOps and TFS
I have been using Visual Studio which has a complete integration with TFS. My projects are managed using TFVC. I want to migrate to Rider. I followed the following instruction, to integrate TFS with Rider: https://rider-support.jetbrains.com/hc/en-us/articles/360000335099-How-to-use-Visual-Studio-s-TFV%D0%A1-local-workspace-in-Rider
I installed TEE, added it to my PATH env variable and set it up. When I execute `tf.cmd workspaces`, I can see all my workspaces and the server URL.
I installed Azure DevOps plugin on Rider.
I went to Settings → Version Control → TFVC and verified that both paths are correct.
When I open some project in Rider, I am prompt to login into Azure DevOps:
However, due to my company policy, I can't login using this flow (OAuth). I need to use a personal access token instead.
How can I use my username and PAT to authenticate the plugin?
Please sign in to leave a comment.
Hello Ido Doron ,
Thank you for reaching Rider Forum.
Could you please try authenticating in Settings | Version Control | Azure DevOps Services / TFS > Username and password? It should have PAT option.
Looking forward to hearing from you soon.
It is already set on `Username and password`
Still, when I open a project it asks me to go through the OAuth flow instead of simply providing my credentials (username + PAT).
Is there a workaround or something?
Hello Ido,
I assume you are running this known issue: Cannot use username/password authentication.
There is a workaround mentioned in the thread. You might want to give it a try.
Unfortunately, I have no other options to suggest.
Have a nice day!
Hi, thanks for your help. It is a little unclear where I should put the downloaded file. I am running Windows. The path $HOME/.swt/swt-x86_64.jar is a Unix path.
I tried to put it in %USERPROFILE%/.swt but it didn't work
Hello Ido,
Unfortunately, I have no other workaround to suggest. As far as I understand, the Azure DevOps plugin auto-default to Device Flow if the library is unavailable.
You might want to try placing swt.jar as C:/Users/<user>/.swt/swt.jar. If that doesn't help, try renaming swt.jar into swt-x86_64.jar as mentioned on the GitHub page.