Change the wizards and profile creation to allow working mode and credentials to be changed/overridden
You used to be able to specify the working mode and credentials (username & password) when configuring the client and creating profiles. Now, if the server is set to ADWorkingMode it forces the client to also use ADWorkingMode and forces th userid & password to the local domains credentials. This makes connecting to plastic server from remote locations problematic and rather difficult to achieve. If you could still simply change the client to LDAPWorkingMode and profile username/password it would be much easier to accomplish this.
Murray Wilson
shared this idea
-
Kent Miller
commented
+100 - this is a huge problem when the office is configured for ADworkingMode, but working from home, the CLIENT needs to be configured for LDAP working mode, since the home machine is not domain joined.
-
Murray Wilson
commented
Also, we are completely unable to create a profile in LDAP mode from a windows machine not in the same AD domain as the plastic server, we have to use clconfigureclient to set the plastic "server" to the remote server.
-
Murray Wilson
commented
Unfortunately, Our biggest problem is using plasticscm windows machines from outside the AD domain, especially if they are joined to a different AD domain. So we still have the issue. We can work around it by using the clconfigureclient command to configure the client, but it seems that from time to time AD mode gets forced back on and we have fiddle around with clconfigureclient and updating plastic and losing several hours :(
So far, the linux machine has always stayed in LDAP mode and has nevber switched to AD mode by itself like windows machines do.
-
We've just fixed this for Linux, where it was an issue for some releases.
Will this get the problem fixed?
Thanks,
pablo
