Nick Antonelli

I appreciate the help, thank you! (Sorry for the delay in responding, got sidetracked elsewhere.)

My team, at some point this year, will have to move our various tools from using LDAP to Active Directory. When reading up in the PlasticSCM admin guide, I noticed this line in the section pertaining to available authentication mechanisms: I just want to verify now, before we have to do any work, that the Active Directory authentication option does not work when the PlasticSCM server is running on a Linux-based OS. I haven't tried it personally yet, just looking for confirmation. Thank you!

Carlos, Thanks so much for the help! Recovery is underway.

Thanks for the response Carlos! One clarification, there is only one PlasticSCM server in this setup; I am merely trying to restore commits that were lost on the server by making use of clients that have the latest changesets. Based on that, is the sync view in the GUI still able to do what I want? Also, would `cm sync` be the appropriate command if we decided to run that from our build agent?

Hello! We had our PlasticSCM data wiped accidentally, but thankfully we have a backup. We restored from the backup, and all the files that the backup had are present (thankfully!) We are trying to restore the remaining changesets to our `main` branch that took place between the backup and the server deletion. A number of people have local copies, but we have a build server that has all the commits that we want to restore. The one problem is that I do not know what `cm` command to use in order to push those changesets to the server. `cm push` is the closest I've seen to that, but I do not know that it will do what I want. Specifically, it looks like that merely copies a branch from one server to another, which is not what I want. Other setup information to note: our server is on-prem (on AWS), and the build agent that has the commits is also on-prem on AWS. Both servers are running Ubuntu 18.04. The build agent only has the client packages installed. Is there any way to push the remaining changesets easily with `cm`?

Carlos, Thank you! I grabbed one of our PlasticSCM power users and was able to resolve the issue with them. I appreciate the help

I am attempting to sync an on-prem PlasticSCM server with a Plastic Cloud account using the sync view functionality. One of the repos gives me the following error message when I attempt the sync: An error occurred during the replication: The source branch has two heads. Merge from cs:xxxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx to br:/main to unify the heads. I know from some research (here in these forums and Stack Overflow) that this is an issue where there are two HEADs in the repo, and that I need to merge one into the other in order for this to get fixed, but I am unsure how to identify the offending changeset. Playing around with the Linux app, I believe that the `cs:xxxxxxx-...` is the GUID of the changeset I care about, but I am unsure if this is the case. Am I correct in that assumption? A second question, which is not terribly important (mostly curious), is what `cm` command(s) would be able to help me identify the second HEAD?

I tried to call `cm lu` from the command line recently and I've been getting an odd error message. Specifically, I get this: Our PlasticSCM instance is reachable and is running. It is sitting on an instance behind a VPN. I can access its webadmin portal, and other commands, like 'cm showacl repserver:ssl://my.domain.com:8088', work perfectly fine. I see that there is a slider for Udt on our server (also running Ubuntu Linux, like me). I tried setting it but it didn't seem to help at all. My local `cm` version is 9.0.16.4437, and the server version of `cm` is 9.0.16.4107. Is it possible that I need to update the server to make this (and possibly other commands) work?

That did it! Installing the server component installed the proper p4api.net.dll file. Might be good to include that with just the client installation as well. Appreciate the help, thank you!

I downloaded it off of the plasticscm website, since it was a fresh install on AWS. I think I clicked on the Enterprise version. Now that you mention it, I don't know if I installed the server component - I definitely installed the client for Plastic. Let me reinstall and I'll get back to you.

Hello, I am attempting to sync a Perforce stream with our PlasticSCM installation. I spun up a Windows 2019 Base install on AWS and installed PlasticSCM, then I setup the command per the documentation. I had downloaded the 2018.3 p4api.net.dll from Perforce's website and placed it in the same directory as the `cm` command. When I execute `cm synchronize`, I get the following: I have tried looking for an earlier version of the DLL, both on Perforce's website and elsewhere, but I have not been able to locate a copy. Are there any plans to use an updated DLL for the porting of Perforce code to PlasticSCM? Is there any workaround that can mitigate the issue? It's not the end of the world if we can't migrate this stream, but I would prefer to do so if possible. Thanks!

Carlos, Thanks for the reply! I figured that was the case, just wanted to confirm it. We actually do use the `add_up` mode and it works like a charm for groups. Thanks again!

Our organization uses LDAP to authenticate people to PlasticSCM. For our CI/CD servers, I have been looking into using a separate user. Ideally I would like it to be a user local to the PlasticSCM server rather than one from LDAP; since we use a Directory-as-a-Service provider for our LDAP configuration, each new user has an additional cost, so I'd like to not incur that cost if possible. I suspect that one cannot mix authentication modes as I've described, but I would like confirmation either way on this. Thanks for the help!

Sorry for the late response! I actually ended up getting it working - I don't quite remember what I was doing wrong, but I think it was a permissions issue with my groups.conf file. I was also able to roll out the change slowly so that it didn't cause too much of an issue for the other teams. I appreciate the response :).

Hello, I've been having issues configuring permissions for groups. We are set up using LDAP for our users. Ideally I would use our pre-existing LDAP groups, yet, when I add those groups using the `cm acl` command, developers in their respective groups do not get the permissions. When doing research, I came upon the fact that LDAP users can be added to PlasticSCM groups. I created the groups, per the documentation. Users still are not getting permissions set as intended. My groups.conf file looks like this: My server.conf as well is set up per the documentation: I'm not sure what is going wrong, and would appreciate any help. Thank you!