Plugin v1.9.0 using the wrong credentials

[Ewanuk]

Problem: I work for two organizations and I need different credentials for each one.

On my second project when I open settings:

The username is still on the credentials I need for my first project. As a result, I can't check anything in. How do I log into a different account on a per-project basis?

[SRombautsU]

Hello,

The short answer is: this should normally work, but you are not the first one to tell us that sometimes it doesn't work

Would you be able to check with a more recent version of the plugin? I see you are using 1.9.0 coming from UE5.4.

I think that your issue has been reported some time already, it looks like similar to what I tried to fix with
PlasticSCM#105
This fix has been released in 1.10.0 that you can get from the Marketplace https://www.unrealengine.com/marketplace/en-US/product/unity-version-control-plastic-scm (or from Github)

In am not entirely sure because I don't have your logs to see exactly what is going on in your case.

If updating doesn't fix the issue, please submit a ticket for technical support but please provide the log from Unreal and the log from "cm" that are needed if we want to understand your issue (see https://docs.plasticscm.com/technical-articles/kb-enabling-logging-for-plastic-scm-part-i)

Let me know how it goes,
Sébastien

[SRombauts]

I am closing this as I could confirm it working with 1.10.1

[Ewanuk]

I've updated to v1.11.0 and I'm seeing a similar issue.

My username is correct, but I'm still getting invalid credential errors. I've checked my client.conf for Unity Source Control and that is still storing the credentials to the other project I'm working with.

I can use the Unity Source Control client just fine with both credentials, so wherever they're stored locally on my machine is probably correct. Is possible the plugin is still using the wrong credentials or does it store it separately?

[SRombauts]

Hello, I am sorry to hear that, I think that you are hitting a bug that isn't si easy to reproduce

The plugin, and Unreal, aren't storing any credentials and the plugin doesn't handle anything except displaying names in some place

So it means that the issue is somewhere in the Command Line Interface (cm.exe) or in it's configuration (client.conf and profiles.conf)

Ideally you could try to test using the command line on the same workspace and see that it should indeed have the same issue; then you could try to use the configure command to set the proposer credentials

Would you be able to provide me as many logs and files as possible? If you prefer send them to Unity support team as they would treat them with the proper confidentially (and it's not related to the Unreal Plugin itself)

Don't hesitate to ask for help, I can provide more details based on your tests

[Ewanuk]

Copying credentials from profiles.conf into client.conf did the trick. It's hacky but oh well.

Where are the logs stored?

[SRombauts]

Hello,

Have a look at Enable Debug logs in the README

1. You can enable Verbose logs from Unreal, I'd like to know how the Unreal plugins detect and treat the error so perhaps we can handle the error properly and ask for credentials (but that's not the most important thing)
2. You can enable debug log for "cm.exe" command line: this will tell us more if the bug is in the low level layers of Unity Version Control. (I think that this is the more interesting thing to understand the issue)

What do you mean exactly by "copying credentials from profiles.conf into client.conf"?

Thanks a lot!

[SRombautsU]

@Ewanuk can you confirm this?
I understand that what you did was changing the "default profile" in the client.conf, to point directly to the correct profile you need in Unreal:

So for instance, if you have in client.conf

<ClientConfigData xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <Language>en</Language>
  <WorkspaceServer>SRombautsU@cloud</WorkspaceServer>
  <WorkingMode>LDAPWorkingMode</WorkingMode>
  <SecurityConfig>::0:[email protected]:JbU8xxxxxGpD/OcF8KI8z3NHJFPXXXXXFKMdLktQpRX1S8iA2dA==:</SecurityConfig>

and in profiles.conf

<ServerProfileData xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <Profiles>
    <ServerProfile>
      <Name>SRombautsU@cloud_LDAPWorkingMode_724c2568-b499-4703-adda-1e11c83645a1</Name>
      <Server>SRombautsU@cloud</Server>
      <WorkingMode>LDAPWorkingMode</WorkingMode>
      <SecurityConfig>::0:[email protected]:JbU8xxxxxGpD/OcF8KI8z3NHJFPXXXXXFKMdLktQpRX1S8iA2dA==:</SecurityConfig>
      <IsDefault>false</IsDefault>
    </ServerProfile>
    <ServerProfile>
      <Name>local_LDAPWorkingMode_6bb6bff7-d704-403f-9fe1-44d5ec1a9bff</Name>
      <Server>local</Server>
      <WorkingMode>LDAPWorkingMode</WorkingMode>
      <SecurityConfig>::0:[email protected]:JbU8xxxxxGpD/OcF8KI8z3NHJFPXXXXXFKMdLktQpRX1S8iA2dA==:</SecurityConfig>
      <IsDefault>false</IsDefault>
    </ServerProfile>
    <ServerProfile>
      <Name>SebastienRombauts@cloud_LDAPWorkingMode_01853243-d66b-4dc2-b911-8aa9745b4f47</Name>
      <Server>SebastienRombauts@cloud</Server>
      <WorkingMode>LDAPWorkingMode</WorkingMode>
      <SecurityConfig>::0:[email protected]:JbUgl0mXXXpL6NaxQHyWjMJADk+0kYhxxxgJTEb+IPy2/XXXrtPQ==:</SecurityConfig>
      <IsDefault>false</IsDefault>
    </ServerProfile>
  </Profiles>
</ServerProfileData>

You can change in the client.conf to now point to the alternate profile (the 3rd one in this example above):

  <WorkspaceServer>SebastienRombauts@cloud</WorkspaceServer>
  <WorkingMode>LDAPWorkingMode</WorkingMode>
  <SecurityConfig>::0:[email protected]:JbUgl0mXXXpL6NaxQHyWjMJADk+0kYhxxxgJTEb+IPy2/XXXrtPQ==:</SecurityConfig>

[SRombauts]

Hello,

the fix for this issue was finally released as part of 1.12 on Github or on Fab.com

Fix 'cm checkconnection' having authentication issues with multiple accounts by @SRombautsU in PlasticSCM#128
Works best with Unity Version Control 11.0.16.9055

Cheers!