Jump to content

How to get rid of security enabled and LDAP requirement?

  • Please log in to reply
1 reply to this topic

#1 wdstest



  • Members
  • Pip
  • 2 posts

Posted 19 June 2019 - 11:15 PM

After restoring a consultant’s perforce backup [ Depot(folder), Checkpoint.1234, Checkpoint.1234.md5] into its own server, I cannot seem to add user or really do anything else:

C:\Program Files\Perforce\Server>p4 -ztag info
... userName *unknown*
... clientName *unknown*
... clientCwd c:\Program Files\Perforce\Server
... clientHost WDS-01VM64W10
... clientCase insensitive
... peerAddress
... clientAddress
... serverName Perforce
... monitor enabled
... security enabled
... serverAddress WDS-01VM64W10:1666
... serverRoot C:\Program Files\Perforce\Server
... serverDate 2019/06/19 15:23:07 -0700 Mountain Standard Time
... tzoffset -25200
... serverUptime 00:00:04
... serverVersion P4D/NTX64/2018.1/1799738 (2019/05/07)
... serverServices standard
... serverLicense none
... caseHandling insensitive
... allowPush 2
... allowFetch 2
... maxParallel 5

C:\Program Files\Perforce\Server>p4 users
No such user(s).

C:\Program Files\Perforce\Server>p4 user
Perforce password (P4PASSWD) invalid or unset.
Attempting login for user 'Administrator' against server '1666'
Cannot login until LDAP authentication is enabled.

I try some other operation but all error with ‘Cannot login until LDAP authentication is enabled’. From what I can tell using my own working server, I don’t want “security enabled” or any of the LDAP stuff. How to I turn those off (I can't seem to add or login on this system), or how do I simply just get this thing working?

#2 Dave Foglesong

Dave Foglesong


  • Members
  • PipPip
  • 14 posts

Posted 20 June 2019 - 03:36 PM

You can adjust the configuration settings directly with p4d (you don't need to start the server), see this KB:

"Accessing Server Configuration Variables"

This should let you change the auth.default.method from LDAP to Perforce, and lower the security setting.

And if you weren't already aware of this, if you delete db.protect it clears all protections so the next person who runs "p4 protect" has super access. You may need to do this to grant your new account super access.

"Regaining Super User Access to Your Perforce Database"

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users