DevOps : Non-Interactive login in new DevOps(TFS) not working getting error 'TF30063: You are not authorized to access



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








6















I am trying to connect to Azure DevOps previously known as TFS using c#. I want to connect to it without the login screen of azure DevOps. I am currently trying the following code but some how it is not working



 NetworkCredential netCred = new NetworkCredential("test@hotmail.com", "test");
Uri tfsuri = new Uri("https://dev.azure.com/test10");
VssBasicCredential bsCred = new VssBasicCredential(netCred);
VssCredentials vssCred = new VssClientCredentials(bsCred);

TfsTeamProjectCollection collection = new TfsTeamProjectCollection(tfsuri, vssCred);

collection.Authenticate();

var witClient = collection.GetClient<ProjectHttpClient>();
var listOfProjects = witClient.GetProjects().Result;


libraries I am using



using Microsoft.TeamFoundation.Client;
using Microsoft.TeamFoundation.Core.WebApi;
using Microsoft.VisualStudio.Services.Client;
using Microsoft.VisualStudio.Services.Common;
using Microsoft.VisualStudio.Services.Operations;
using Microsoft.VisualStudio.Services.WebApi;
using Microsoft.TeamFoundation.WorkItemTracking.Client;
using Microsoft.TeamFoundation.WorkItemTracking.WebApi;


The code prompts a login screen, on which if I enter the password the auth still does not work. I dont want the login screen to appear and only want to connect with the username and password.



With alternate credentials this method is working but it is not my requirement and I can not use alternate credentials.



I have tried following the samples from the official site but no solution is working for the new DevOps.



Any Solution how can I authenticate with usernanme/password in the new DevOps without the login screen










share|improve this question






























    6















    I am trying to connect to Azure DevOps previously known as TFS using c#. I want to connect to it without the login screen of azure DevOps. I am currently trying the following code but some how it is not working



     NetworkCredential netCred = new NetworkCredential("test@hotmail.com", "test");
    Uri tfsuri = new Uri("https://dev.azure.com/test10");
    VssBasicCredential bsCred = new VssBasicCredential(netCred);
    VssCredentials vssCred = new VssClientCredentials(bsCred);

    TfsTeamProjectCollection collection = new TfsTeamProjectCollection(tfsuri, vssCred);

    collection.Authenticate();

    var witClient = collection.GetClient<ProjectHttpClient>();
    var listOfProjects = witClient.GetProjects().Result;


    libraries I am using



    using Microsoft.TeamFoundation.Client;
    using Microsoft.TeamFoundation.Core.WebApi;
    using Microsoft.VisualStudio.Services.Client;
    using Microsoft.VisualStudio.Services.Common;
    using Microsoft.VisualStudio.Services.Operations;
    using Microsoft.VisualStudio.Services.WebApi;
    using Microsoft.TeamFoundation.WorkItemTracking.Client;
    using Microsoft.TeamFoundation.WorkItemTracking.WebApi;


    The code prompts a login screen, on which if I enter the password the auth still does not work. I dont want the login screen to appear and only want to connect with the username and password.



    With alternate credentials this method is working but it is not my requirement and I can not use alternate credentials.



    I have tried following the samples from the official site but no solution is working for the new DevOps.



    Any Solution how can I authenticate with usernanme/password in the new DevOps without the login screen










    share|improve this question


























      6












      6








      6


      3






      I am trying to connect to Azure DevOps previously known as TFS using c#. I want to connect to it without the login screen of azure DevOps. I am currently trying the following code but some how it is not working



       NetworkCredential netCred = new NetworkCredential("test@hotmail.com", "test");
      Uri tfsuri = new Uri("https://dev.azure.com/test10");
      VssBasicCredential bsCred = new VssBasicCredential(netCred);
      VssCredentials vssCred = new VssClientCredentials(bsCred);

      TfsTeamProjectCollection collection = new TfsTeamProjectCollection(tfsuri, vssCred);

      collection.Authenticate();

      var witClient = collection.GetClient<ProjectHttpClient>();
      var listOfProjects = witClient.GetProjects().Result;


      libraries I am using



      using Microsoft.TeamFoundation.Client;
      using Microsoft.TeamFoundation.Core.WebApi;
      using Microsoft.VisualStudio.Services.Client;
      using Microsoft.VisualStudio.Services.Common;
      using Microsoft.VisualStudio.Services.Operations;
      using Microsoft.VisualStudio.Services.WebApi;
      using Microsoft.TeamFoundation.WorkItemTracking.Client;
      using Microsoft.TeamFoundation.WorkItemTracking.WebApi;


      The code prompts a login screen, on which if I enter the password the auth still does not work. I dont want the login screen to appear and only want to connect with the username and password.



      With alternate credentials this method is working but it is not my requirement and I can not use alternate credentials.



      I have tried following the samples from the official site but no solution is working for the new DevOps.



      Any Solution how can I authenticate with usernanme/password in the new DevOps without the login screen










      share|improve this question
















      I am trying to connect to Azure DevOps previously known as TFS using c#. I want to connect to it without the login screen of azure DevOps. I am currently trying the following code but some how it is not working



       NetworkCredential netCred = new NetworkCredential("test@hotmail.com", "test");
      Uri tfsuri = new Uri("https://dev.azure.com/test10");
      VssBasicCredential bsCred = new VssBasicCredential(netCred);
      VssCredentials vssCred = new VssClientCredentials(bsCred);

      TfsTeamProjectCollection collection = new TfsTeamProjectCollection(tfsuri, vssCred);

      collection.Authenticate();

      var witClient = collection.GetClient<ProjectHttpClient>();
      var listOfProjects = witClient.GetProjects().Result;


      libraries I am using



      using Microsoft.TeamFoundation.Client;
      using Microsoft.TeamFoundation.Core.WebApi;
      using Microsoft.VisualStudio.Services.Client;
      using Microsoft.VisualStudio.Services.Common;
      using Microsoft.VisualStudio.Services.Operations;
      using Microsoft.VisualStudio.Services.WebApi;
      using Microsoft.TeamFoundation.WorkItemTracking.Client;
      using Microsoft.TeamFoundation.WorkItemTracking.WebApi;


      The code prompts a login screen, on which if I enter the password the auth still does not work. I dont want the login screen to appear and only want to connect with the username and password.



      With alternate credentials this method is working but it is not my requirement and I can not use alternate credentials.



      I have tried following the samples from the official site but no solution is working for the new DevOps.



      Any Solution how can I authenticate with usernanme/password in the new DevOps without the login screen







      tfs azure-devops devops azure-devops-rest-api






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 15 '18 at 13:00







      Student

















      asked Nov 13 '18 at 21:09









      StudentStudent

      748




      748






















          1 Answer
          1






          active

          oldest

          votes


















          2














          The class TfsTeamProjectCollection is from the old .Net libraries, try the new Azure DevOps .Net libraries, and you can authenticate in a few ways:



          NTLM



          The most basic one is constructing a VssCredentials instance with no parameter at all and what you’ll be using is simply put integrated authentication / NTLM:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssCredentials());


          Basic Authentication



          VSTS and TFS also provide means to utilize Basic authentication (HTTP AUTH) which you need to create and enable first (see VSTS guidelines) and once you’ve done so, you can use them via the API like this:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssBasicCredential(username, password));


          Personal Access Tokens



          Next up are Personal Access Tokens (PAT) which you can easily create following the VSTS guidelines and those PATs are a means of authenticating separately from your actual credentials with a fine-grained & per access token scopes of security. Simply put it allows you to create a PAT for every use-case or even application and thereby enabling a secure and clearly separated way of giving an application or 3rd party access to your VSTS or TFS system on your behalf.



          To use these via the API, you use the exact same mechanism as via Basic Authentication but you simply don’t provide any username (well – an empty one to be precise), and the PAT itself is used as the password:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssBasicCredential(string.Empty, pat));


          Visual Studio Sign-in Prompt



          Moreover, another way of authenticating is using the standard VS Sign-In prompt which is similarly easy and exposed via the VssClientCredentials class:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssClientCredentials());


          OAuth Authentication



          OAuth is a widely used but a slightly more tedious authorization protocol to implement but luckily there’s a thorough sample application available at CodePlex specifically for VSTS / VSO (which also works for on-premises).



          Once you have the corresponding access token, you can use it to VSTS / TFS utilizing the VssOAuthCredential class:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssOAuthCredential(accessToken));


          Azure Active Directory Authentication



          Last but not least you can utilize Azure Active Directory identities to authenticate against a VSTS or TFS system via the VssAadCredential class:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssAadCredential(username, password));





          share|improve this answer























          • Thank you for your response. I want to use Basic Authentication but if I put my email and password in the VssBasicCredential(username, password). It does not authenticate the connection. I dont want to use alternate credentials for this

            – Student
            Nov 14 '18 at 9:37











          • what do you mean not authenticate the connection, do you get an error?

            – Shayki Abramczyk
            Nov 14 '18 at 9:54











          • I tired that VssConnection connection = new VssConnection(tfsuri, new VssBasicCredential(netCred)); WorkItemTrackingHttpClient witClient = connection.GetClient<WorkItemTrackingHttpClient>(); and I get the following error rosoft.VisualStudio.Services.Common.VssUnauthorizedException: 'VS30063: You are not authorized to access dev.azure.com.'

            – Student
            Nov 14 '18 at 9:58












          • Did you try without netCred, just put strings?

            – Shayki Abramczyk
            Nov 14 '18 at 10:01






          • 1





            In second thought I not sure azure devops support basic, maybe only TFS, try to check the contractors of VssCredentials.

            – Shayki Abramczyk
            Nov 14 '18 at 10:14











          Your Answer






          StackExchange.ifUsing("editor", function ()
          StackExchange.using("externalEditor", function ()
          StackExchange.using("snippets", function ()
          StackExchange.snippets.init();
          );
          );
          , "code-snippets");

          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "1"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53289522%2fdevops-non-interactive-login-in-new-devopstfs-not-working-getting-error-tf3%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          2














          The class TfsTeamProjectCollection is from the old .Net libraries, try the new Azure DevOps .Net libraries, and you can authenticate in a few ways:



          NTLM



          The most basic one is constructing a VssCredentials instance with no parameter at all and what you’ll be using is simply put integrated authentication / NTLM:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssCredentials());


          Basic Authentication



          VSTS and TFS also provide means to utilize Basic authentication (HTTP AUTH) which you need to create and enable first (see VSTS guidelines) and once you’ve done so, you can use them via the API like this:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssBasicCredential(username, password));


          Personal Access Tokens



          Next up are Personal Access Tokens (PAT) which you can easily create following the VSTS guidelines and those PATs are a means of authenticating separately from your actual credentials with a fine-grained & per access token scopes of security. Simply put it allows you to create a PAT for every use-case or even application and thereby enabling a secure and clearly separated way of giving an application or 3rd party access to your VSTS or TFS system on your behalf.



          To use these via the API, you use the exact same mechanism as via Basic Authentication but you simply don’t provide any username (well – an empty one to be precise), and the PAT itself is used as the password:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssBasicCredential(string.Empty, pat));


          Visual Studio Sign-in Prompt



          Moreover, another way of authenticating is using the standard VS Sign-In prompt which is similarly easy and exposed via the VssClientCredentials class:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssClientCredentials());


          OAuth Authentication



          OAuth is a widely used but a slightly more tedious authorization protocol to implement but luckily there’s a thorough sample application available at CodePlex specifically for VSTS / VSO (which also works for on-premises).



          Once you have the corresponding access token, you can use it to VSTS / TFS utilizing the VssOAuthCredential class:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssOAuthCredential(accessToken));


          Azure Active Directory Authentication



          Last but not least you can utilize Azure Active Directory identities to authenticate against a VSTS or TFS system via the VssAadCredential class:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssAadCredential(username, password));





          share|improve this answer























          • Thank you for your response. I want to use Basic Authentication but if I put my email and password in the VssBasicCredential(username, password). It does not authenticate the connection. I dont want to use alternate credentials for this

            – Student
            Nov 14 '18 at 9:37











          • what do you mean not authenticate the connection, do you get an error?

            – Shayki Abramczyk
            Nov 14 '18 at 9:54











          • I tired that VssConnection connection = new VssConnection(tfsuri, new VssBasicCredential(netCred)); WorkItemTrackingHttpClient witClient = connection.GetClient<WorkItemTrackingHttpClient>(); and I get the following error rosoft.VisualStudio.Services.Common.VssUnauthorizedException: 'VS30063: You are not authorized to access dev.azure.com.'

            – Student
            Nov 14 '18 at 9:58












          • Did you try without netCred, just put strings?

            – Shayki Abramczyk
            Nov 14 '18 at 10:01






          • 1





            In second thought I not sure azure devops support basic, maybe only TFS, try to check the contractors of VssCredentials.

            – Shayki Abramczyk
            Nov 14 '18 at 10:14















          2














          The class TfsTeamProjectCollection is from the old .Net libraries, try the new Azure DevOps .Net libraries, and you can authenticate in a few ways:



          NTLM



          The most basic one is constructing a VssCredentials instance with no parameter at all and what you’ll be using is simply put integrated authentication / NTLM:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssCredentials());


          Basic Authentication



          VSTS and TFS also provide means to utilize Basic authentication (HTTP AUTH) which you need to create and enable first (see VSTS guidelines) and once you’ve done so, you can use them via the API like this:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssBasicCredential(username, password));


          Personal Access Tokens



          Next up are Personal Access Tokens (PAT) which you can easily create following the VSTS guidelines and those PATs are a means of authenticating separately from your actual credentials with a fine-grained & per access token scopes of security. Simply put it allows you to create a PAT for every use-case or even application and thereby enabling a secure and clearly separated way of giving an application or 3rd party access to your VSTS or TFS system on your behalf.



          To use these via the API, you use the exact same mechanism as via Basic Authentication but you simply don’t provide any username (well – an empty one to be precise), and the PAT itself is used as the password:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssBasicCredential(string.Empty, pat));


          Visual Studio Sign-in Prompt



          Moreover, another way of authenticating is using the standard VS Sign-In prompt which is similarly easy and exposed via the VssClientCredentials class:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssClientCredentials());


          OAuth Authentication



          OAuth is a widely used but a slightly more tedious authorization protocol to implement but luckily there’s a thorough sample application available at CodePlex specifically for VSTS / VSO (which also works for on-premises).



          Once you have the corresponding access token, you can use it to VSTS / TFS utilizing the VssOAuthCredential class:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssOAuthCredential(accessToken));


          Azure Active Directory Authentication



          Last but not least you can utilize Azure Active Directory identities to authenticate against a VSTS or TFS system via the VssAadCredential class:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssAadCredential(username, password));





          share|improve this answer























          • Thank you for your response. I want to use Basic Authentication but if I put my email and password in the VssBasicCredential(username, password). It does not authenticate the connection. I dont want to use alternate credentials for this

            – Student
            Nov 14 '18 at 9:37











          • what do you mean not authenticate the connection, do you get an error?

            – Shayki Abramczyk
            Nov 14 '18 at 9:54











          • I tired that VssConnection connection = new VssConnection(tfsuri, new VssBasicCredential(netCred)); WorkItemTrackingHttpClient witClient = connection.GetClient<WorkItemTrackingHttpClient>(); and I get the following error rosoft.VisualStudio.Services.Common.VssUnauthorizedException: 'VS30063: You are not authorized to access dev.azure.com.'

            – Student
            Nov 14 '18 at 9:58












          • Did you try without netCred, just put strings?

            – Shayki Abramczyk
            Nov 14 '18 at 10:01






          • 1





            In second thought I not sure azure devops support basic, maybe only TFS, try to check the contractors of VssCredentials.

            – Shayki Abramczyk
            Nov 14 '18 at 10:14













          2












          2








          2







          The class TfsTeamProjectCollection is from the old .Net libraries, try the new Azure DevOps .Net libraries, and you can authenticate in a few ways:



          NTLM



          The most basic one is constructing a VssCredentials instance with no parameter at all and what you’ll be using is simply put integrated authentication / NTLM:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssCredentials());


          Basic Authentication



          VSTS and TFS also provide means to utilize Basic authentication (HTTP AUTH) which you need to create and enable first (see VSTS guidelines) and once you’ve done so, you can use them via the API like this:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssBasicCredential(username, password));


          Personal Access Tokens



          Next up are Personal Access Tokens (PAT) which you can easily create following the VSTS guidelines and those PATs are a means of authenticating separately from your actual credentials with a fine-grained & per access token scopes of security. Simply put it allows you to create a PAT for every use-case or even application and thereby enabling a secure and clearly separated way of giving an application or 3rd party access to your VSTS or TFS system on your behalf.



          To use these via the API, you use the exact same mechanism as via Basic Authentication but you simply don’t provide any username (well – an empty one to be precise), and the PAT itself is used as the password:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssBasicCredential(string.Empty, pat));


          Visual Studio Sign-in Prompt



          Moreover, another way of authenticating is using the standard VS Sign-In prompt which is similarly easy and exposed via the VssClientCredentials class:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssClientCredentials());


          OAuth Authentication



          OAuth is a widely used but a slightly more tedious authorization protocol to implement but luckily there’s a thorough sample application available at CodePlex specifically for VSTS / VSO (which also works for on-premises).



          Once you have the corresponding access token, you can use it to VSTS / TFS utilizing the VssOAuthCredential class:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssOAuthCredential(accessToken));


          Azure Active Directory Authentication



          Last but not least you can utilize Azure Active Directory identities to authenticate against a VSTS or TFS system via the VssAadCredential class:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssAadCredential(username, password));





          share|improve this answer













          The class TfsTeamProjectCollection is from the old .Net libraries, try the new Azure DevOps .Net libraries, and you can authenticate in a few ways:



          NTLM



          The most basic one is constructing a VssCredentials instance with no parameter at all and what you’ll be using is simply put integrated authentication / NTLM:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssCredentials());


          Basic Authentication



          VSTS and TFS also provide means to utilize Basic authentication (HTTP AUTH) which you need to create and enable first (see VSTS guidelines) and once you’ve done so, you can use them via the API like this:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssBasicCredential(username, password));


          Personal Access Tokens



          Next up are Personal Access Tokens (PAT) which you can easily create following the VSTS guidelines and those PATs are a means of authenticating separately from your actual credentials with a fine-grained & per access token scopes of security. Simply put it allows you to create a PAT for every use-case or even application and thereby enabling a secure and clearly separated way of giving an application or 3rd party access to your VSTS or TFS system on your behalf.



          To use these via the API, you use the exact same mechanism as via Basic Authentication but you simply don’t provide any username (well – an empty one to be precise), and the PAT itself is used as the password:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssBasicCredential(string.Empty, pat));


          Visual Studio Sign-in Prompt



          Moreover, another way of authenticating is using the standard VS Sign-In prompt which is similarly easy and exposed via the VssClientCredentials class:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssClientCredentials());


          OAuth Authentication



          OAuth is a widely used but a slightly more tedious authorization protocol to implement but luckily there’s a thorough sample application available at CodePlex specifically for VSTS / VSO (which also works for on-premises).



          Once you have the corresponding access token, you can use it to VSTS / TFS utilizing the VssOAuthCredential class:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssOAuthCredential(accessToken));


          Azure Active Directory Authentication



          Last but not least you can utilize Azure Active Directory identities to authenticate against a VSTS or TFS system via the VssAadCredential class:



          var visualStudioServicesConnection = new VssConnection(new Uri(baseUri), new VssAadCredential(username, password));






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 14 '18 at 7:29









          Shayki AbramczykShayki Abramczyk

          4,45731130




          4,45731130












          • Thank you for your response. I want to use Basic Authentication but if I put my email and password in the VssBasicCredential(username, password). It does not authenticate the connection. I dont want to use alternate credentials for this

            – Student
            Nov 14 '18 at 9:37











          • what do you mean not authenticate the connection, do you get an error?

            – Shayki Abramczyk
            Nov 14 '18 at 9:54











          • I tired that VssConnection connection = new VssConnection(tfsuri, new VssBasicCredential(netCred)); WorkItemTrackingHttpClient witClient = connection.GetClient<WorkItemTrackingHttpClient>(); and I get the following error rosoft.VisualStudio.Services.Common.VssUnauthorizedException: 'VS30063: You are not authorized to access dev.azure.com.'

            – Student
            Nov 14 '18 at 9:58












          • Did you try without netCred, just put strings?

            – Shayki Abramczyk
            Nov 14 '18 at 10:01






          • 1





            In second thought I not sure azure devops support basic, maybe only TFS, try to check the contractors of VssCredentials.

            – Shayki Abramczyk
            Nov 14 '18 at 10:14

















          • Thank you for your response. I want to use Basic Authentication but if I put my email and password in the VssBasicCredential(username, password). It does not authenticate the connection. I dont want to use alternate credentials for this

            – Student
            Nov 14 '18 at 9:37











          • what do you mean not authenticate the connection, do you get an error?

            – Shayki Abramczyk
            Nov 14 '18 at 9:54











          • I tired that VssConnection connection = new VssConnection(tfsuri, new VssBasicCredential(netCred)); WorkItemTrackingHttpClient witClient = connection.GetClient<WorkItemTrackingHttpClient>(); and I get the following error rosoft.VisualStudio.Services.Common.VssUnauthorizedException: 'VS30063: You are not authorized to access dev.azure.com.'

            – Student
            Nov 14 '18 at 9:58












          • Did you try without netCred, just put strings?

            – Shayki Abramczyk
            Nov 14 '18 at 10:01






          • 1





            In second thought I not sure azure devops support basic, maybe only TFS, try to check the contractors of VssCredentials.

            – Shayki Abramczyk
            Nov 14 '18 at 10:14
















          Thank you for your response. I want to use Basic Authentication but if I put my email and password in the VssBasicCredential(username, password). It does not authenticate the connection. I dont want to use alternate credentials for this

          – Student
          Nov 14 '18 at 9:37





          Thank you for your response. I want to use Basic Authentication but if I put my email and password in the VssBasicCredential(username, password). It does not authenticate the connection. I dont want to use alternate credentials for this

          – Student
          Nov 14 '18 at 9:37













          what do you mean not authenticate the connection, do you get an error?

          – Shayki Abramczyk
          Nov 14 '18 at 9:54





          what do you mean not authenticate the connection, do you get an error?

          – Shayki Abramczyk
          Nov 14 '18 at 9:54













          I tired that VssConnection connection = new VssConnection(tfsuri, new VssBasicCredential(netCred)); WorkItemTrackingHttpClient witClient = connection.GetClient<WorkItemTrackingHttpClient>(); and I get the following error rosoft.VisualStudio.Services.Common.VssUnauthorizedException: 'VS30063: You are not authorized to access dev.azure.com.'

          – Student
          Nov 14 '18 at 9:58






          I tired that VssConnection connection = new VssConnection(tfsuri, new VssBasicCredential(netCred)); WorkItemTrackingHttpClient witClient = connection.GetClient<WorkItemTrackingHttpClient>(); and I get the following error rosoft.VisualStudio.Services.Common.VssUnauthorizedException: 'VS30063: You are not authorized to access dev.azure.com.'

          – Student
          Nov 14 '18 at 9:58














          Did you try without netCred, just put strings?

          – Shayki Abramczyk
          Nov 14 '18 at 10:01





          Did you try without netCred, just put strings?

          – Shayki Abramczyk
          Nov 14 '18 at 10:01




          1




          1





          In second thought I not sure azure devops support basic, maybe only TFS, try to check the contractors of VssCredentials.

          – Shayki Abramczyk
          Nov 14 '18 at 10:14





          In second thought I not sure azure devops support basic, maybe only TFS, try to check the contractors of VssCredentials.

          – Shayki Abramczyk
          Nov 14 '18 at 10:14



















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53289522%2fdevops-non-interactive-login-in-new-devopstfs-not-working-getting-error-tf3%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          𛂒𛀶,𛀽𛀑𛂀𛃧𛂓𛀙𛃆𛃑𛃷𛂟𛁡𛀢𛀟𛁤𛂽𛁕𛁪𛂟𛂯,𛁞𛂧𛀴𛁄𛁠𛁼𛂿𛀤 𛂘,𛁺𛂾𛃭𛃭𛃵𛀺,𛂣𛃍𛂖𛃶 𛀸𛃀𛂖𛁶𛁏𛁚 𛂢𛂞 𛁰𛂆𛀔,𛁸𛀽𛁓𛃋𛂇𛃧𛀧𛃣𛂐𛃇,𛂂𛃻𛃲𛁬𛃞𛀧𛃃𛀅 𛂭𛁠𛁡𛃇𛀷𛃓𛁥,𛁙𛁘𛁞𛃸𛁸𛃣𛁜,𛂛,𛃿,𛁯𛂘𛂌𛃛𛁱𛃌𛂈𛂇 𛁊𛃲,𛀕𛃴𛀜 𛀶𛂆𛀶𛃟𛂉𛀣,𛂐𛁞𛁾 𛁷𛂑𛁳𛂯𛀬𛃅,𛃶𛁼

          Edmonton

          Crossroads (UK TV series)