Hi Halil Kerimi ,

If the issue is related to identifying whether or not the AddCredential function (also) updates an existing credential with the same uri.  Then why not manage that process yourself?

Plaese make reference to Class TranslationProviderCredentialStore. It enables you to get, add, remove and clear credentials.

Maybe first check if the credential exists for provider uri and then remove it before adding a new one?

Example

var myCredential = credentialStore.GetCredential(translationProviderUri);
if (myCredential != null)
{
    credentialStore.RemoveCredential(translationProviderUri);
}

var newCredential = new TranslationProviderCredential(credential: "credential string", persist: false);
credentialStore.AddCredential(translationProviderUri, newCredential);

Thank you Patrick Andrew Hartnett  for the suggestion!
The point is that I am adding credentials in the FileBasedProject object like this:

public void SetTMCredentialsOnly(FileBasedProject project, string username, string password, bool useWindowsSecurity = false)
{
    var credentialStore = new TranslationProviderCredentialStore();
    var allTranslationProviders = new List<TranslationProviderCascadeEntry>();
    TranslationProviderConfiguration translationProviderConfiguration = project.GetTranslationProviderConfiguration();
    allTranslationProviders.AddRange(translationProviderConfiguration.Entries);

    foreach (var lang in project.GetProjectInfo().TargetLanguages)
    {
        var langProviders = project.GetTranslationProviderConfiguration(lang);
        foreach (var prov in langProviders.Entries)
        {
            // Check whether the provider has already been added
            var exists = allTranslationProviders.Any(p => p.MainTranslationProvider.Uri.ToString()
                .Equals(prov.MainTranslationProvider.Uri.ToString()));
            if (exists)
            {
                continue;
            }
            else
            {
                allTranslationProviders.Add(prov);
            }
        }
    }

    foreach (var provider in allTranslationProviders)
    {
        Uri uri = provider.MainTranslationProvider?.Uri;
        if (!uri.ToString().StartsWith("sdltm.http"))
        {
            continue;
        }
        string type = useWindowsSecurity ? "WindowsUser" : "CustomUser";
        string credentials = $"user={username};password={password};type={type}";
        project.Credentials.AddCredential(uri, credentials);
    }
}

Key Clarification:

• Here, I retrieve all the providers from the project template, filter only the GroupShare providers (sdltm.http*), and then add credentials using the FileBasedProject.Credentials property.
• The credentials are passed as parameters (username, password, etc.) and added directly to the project.

My Question:

If I use the following line:

var myCredential = credentialStore.GetCredential(translationProviderUri);

Will it reference the same credential store that FileBasedProject.Credentials uses?

I’m trying to understand if TranslationProviderCredentialStore and FileBasedProject.Credentials work with the same underlying store. If not, I might have to manage credential removal and re-adding more explicitly as you suggested.

Thanks again for your help! 

Hi Halil Kerimi ,  When you create a new instance of `TranslationProviderCredentialStore`, it operates independently and does not reference the credentials managed by the `FileBasedProject.Credentials`. This means any credentials added to your separate instance won't be recognized by the project or persisted across sessions.
It'll only live in memory, a bit like my dream to go on vacation in Hawaii this year!

The `FileBasedProject.Credentials` interfaces with the primary `TranslationProviderCredentialStore` managed by Trados Studio. This store is typically located in the user’s roaming directory:

C:\Users\<YourUsername>\AppData\Roaming\Trados\Trados Studio\Studio18\TranslationProviderCredentialStore.bin#

Trados Studio manages this store to save and load credentials, ensuring they persist and are accessible across different projects and sessions.

Recommend

To ensure that credentials are properly managed and persisted, In yr case I would recommend that you interact directly with the project's credential store (`FileBasedProject.Credentials`). This ensures consistency and leverages Trados Studio's built-in credential management.

Example

public void SetTMCredentialsOnly(FileBasedProject project, string username, string password, bool useWindowsSecurity = false)
{
    var credentialStore = project.Credentials; // Use the project's credential store
    var allTranslationProviders = new List<TranslationProviderCascadeEntry>();
    TranslationProviderConfiguration translationProviderConfiguration = project.GetTranslationProviderConfiguration();
    allTranslationProviders.AddRange(translationProviderConfiguration.Entries);

    foreach (var lang in project.GetProjectInfo().TargetLanguages)
    {
        var langProviders = project.GetTranslationProviderConfiguration(lang);
        foreach (var prov in langProviders.Entries)
        {
            // Avoid adding duplicate providers
            if (!allTranslationProviders.Any(p => p.MainTranslationProvider.Uri.Equals(prov.MainTranslationProvider.Uri)))
            {
                allTranslationProviders.Add(prov);
            }
        }
    }

    foreach (var provider in allTranslationProviders)
    {
        Uri uri = provider.MainTranslationProvider?.Uri;
        if (uri == null || !uri.ToString().StartsWith("sdltm.http", StringComparison.OrdinalIgnoreCase))
        {
            continue;
        }

        string type = useWindowsSecurity ? "WindowsUser" : "CustomUser";
        string credentials = $"user={username};password={password};type={type}";

        
        // Add/Update the new credential
        credentialStore.AddCredential(uri, credentials);
    }
}

let me know how it goes.

Thank you Patrick Andrew Hartnett  for the detailed explanation and the suggestions!

I’m currently using Trados 2022, and I’ve noticed that the ProjectCredentials class in:

var credentialStore = project.Credentials;

doesn’t provide public methods like GetCredential(uri) or RemoveCredential(uri).

This makes it impossible to directly check for existing credentials or remove them before adding new ones.

Do you have any recommendations or workarounds for handling this limitation in Trados 2022?

Thanks again for your support!

Hi Halil Kerimi , you're right, Just checked also for 2024 and only see AddCredential exposed for the Sdl.ProjectAutomation.FileBased.ProjectCredential as it updates the existing credential if it exists, otherwise adds a new one.

But I don't think it's a blocker for your right? So, to answer your very first question at the beginning of this thread, will AddCredential also update it if it already exists: "Yes, for the FileBasedProject.Credentials"; RemoveCredential is not exposed from the Sdl.ProjectAutomation.FileBased.ProjectCredential

Let me know how it goes, sorry confusion; this is also a surprise for me!

The sample code I provided above (with get and remove) will only work for the Credential Store exposed from the Translation Provider API.

Note: I've updated the sample provided in the prevous post to avoid confusion; thx for checking this!!! appreciated

Thank you Patrick Andrew Hartnett  for clarifying and updating your previous post!

Actually, I believe my issue lies in the fact that when adding credentials again, it doesn't seem to update the old credentials.

Since I cannot remove credentials from FileBasedProject.Credentials, I’ve been using:

var credentialStore = new TranslationProviderCredentialStore();

This works in the sense that it retrieves credentials and allows the pre-translation task to run.

Issue Details:

I’ve been testing the tool by creating two projects to analyze the behavior:

1. First Project:
   1. The tool adds credentials and authenticates correctly (throws an error if the password is wrong).
   2. It creates the project successfully, and the pre-translation is filled from the TM matches.
2. Second Project:
   1. The tool removes the old credentials, adds new credentials (same URL and username but with a wrong password).
   2. Credentials are added without even attempting to authenticate—no error is thrown.
   3. Surprisingly, the second project is processed correctly, and the pre-translation is filled from the TM matches, even with the wrong credentials.

I also tried your updated example and this version of the code:

public void SetTMCredentialsOnly(FileBasedProject project, string username, string password, bool useWindowsSecurity = false)
{
    var credentialStore = new TranslationProviderCredentialStore();
    var allTranslationProviders = new List<TranslationProviderCascadeEntry>();
    TranslationProviderConfiguration translationProviderConfiguration = project.GetTranslationProviderConfiguration();
    allTranslationProviders.AddRange(translationProviderConfiguration.Entries);

    foreach (var lang in project.GetProjectInfo().TargetLanguages)
    {
        var langProviders = project.GetTranslationProviderConfiguration(lang);
        foreach (var prov in langProviders.Entries)
        {
            // Check whether the provider has been added
            var exists = allTranslationProviders.Any(p => p.MainTranslationProvider.Uri.ToString()
                .Equals(prov.MainTranslationProvider.Uri.ToString()));
            if (exists)
            {
                continue;
            }
            else
            {
                allTranslationProviders.Add(prov);
            }
        }
    }

    foreach (var provider in allTranslationProviders)
    {
        Uri uri = provider.MainTranslationProvider?.Uri;
        if (!uri.ToString().StartsWith("sdltm.http"))
        {
            continue;
        }

        string type = useWindowsSecurity ? "WindowsUser" : "CustomUser";
        string credentials = $"user={username};password={password};type={type}";

        var myCredential = credentialStore.GetCredential(uri);
        if (myCredential != null)
        {
            credentialStore.RemoveCredential(uri);
        }

        var newCredential = new TranslationProviderCredential(credential: credentials, persist: false);
        credentialStore.AddCredential(uri, newCredential);
    }
}

I believe I’ve identified the root cause of the issue.

While debugging my code, I found that when running the automatic task Sdl.ProjectApi.AutomaticTasks.Translate, it eventually calls ServerBasedTranslationMemoryFactory to retrieve a TranslationProviderServer in the namespace Sdl.LanguagePlatform.TranslationMemoryApi.

Here’s the relevant code:

private TranslationProviderServer GetCachedServer(string serverUri, UserCredentials userCredentials)
{
    if (_cachedServer != null && _cachedServer.Uri.AbsoluteUri.Equals(serverUri))
    {
        return _cachedServer;
    }
    if (userCredentials.UserType == UserManagerTokenType.Saml2User)
    {
        _cachedServer = new TranslationProviderServer(new Uri(serverUri), userCredentials.UserName, userCredentials.AuthToken, userCredentials.ExpirationDate);
    }
    else
    {
        _cachedServer = new TranslationProviderServer(new Uri(serverUri), userCredentials);
    }
    _cachedServer = new TranslationProviderServer(new Uri(serverUri), userCredentials);
    return _cachedServer;
}

Observations:

As you can see, the code first checks if _cachedServer already exists and has the same URL (serverUri). If it does, it simply returns the cached server without verifying if the credentials actually match.

This behavior seems to explain why tasks continue to succeed with outdated or incorrect credentials—it’s reusing the cached instance of the TranslationProviderServer.

Question:

I’m not sure if this behavior is a bug or if it’s intentional. However, being able to clear the _cachedServer would be very helpful in scenarios where credentials need to be updated or refreshed.

What are your thoughts on this?