• State Suggested Answer
  • Replies 10 replies
  • Answers 5 answers
  • Subscribers 4 subscribers
  • Views 5307 views
  • Users 0 members are here
Options
Related

Unable to publish FileBasedProject with windows username+password authentication

Tamas Meszaros

Hi,

I'm happy to see that I can already authenticate with windows username+password when creating a new instance of TranslationProviderServer(). I can read TMs, add them to the project etc. (Here I specify: useWindowsAuthentication=false)

However, it seems, that using the same credentials, I cannot publish the project to a GS 2017 server like:

var result = project.PublishProject(new Uri(server), useWindowsAuthentication = false, windowsUserName, windowsPassword, targetOrganization, (sender, args) => { });

I keep getting an "Authentication failed" error. If I use a non-windows SDL account, then it works. But not with a windows account.

(using useWindowsAuthentication=true I get "value cannot be null")

Can you please help? Is this supported at all? I remember that in the old times, TranslationProviderServer didn't work with explicit windows credentials either. But it seems to work now. That's why I was hoping that publishing also works.

I have Studio 2017 SR1 14.1.10011.20356, and GS: 14.2.7902.0 - SR1.

Thanks,

Tamas
Rate translation
×
Suggest better translation
×
Parents
  • 0

    I think the following is related to this, I cannot add translation providers to a project when using Windows authentication, see the lines below:

    // use Windows authentication by setting the type parameter to Windows, user name and password left empty, because the current Windows user should be used -> Error

    _project.Credentials.AddCredential(new Uri(tmUri), true, "", "");

    // use Windows authentication by setting the type parameter to Windows, user name and password of the Windows user explicitly stated as string parameters -> Error

    _project.Credentials.AddCredential(new Uri(tmUri), true, "domain/user", "password");

     

    // use this method for Windows authentication by setting the boolean Windows parameter to false -> OK

    _project.Credentials.AddCredential(new Uri(tmUri), false, "sa", "sa");
Reply
  • 0

    I think the following is related to this, I cannot add translation providers to a project when using Windows authentication, see the lines below:

    // use Windows authentication by setting the type parameter to Windows, user name and password left empty, because the current Windows user should be used -> Error

    _project.Credentials.AddCredential(new Uri(tmUri), true, "", "");

    // use Windows authentication by setting the type parameter to Windows, user name and password of the Windows user explicitly stated as string parameters -> Error

    _project.Credentials.AddCredential(new Uri(tmUri), true, "domain/user", "password");

     

    // use this method for Windows authentication by setting the boolean Windows parameter to false -> OK

    _project.Credentials.AddCredential(new Uri(tmUri), false, "sa", "sa");
Children