Set Perforce Security Level

There is Security level on Perforce

The Perforce server security levels and their effects on the behavior of Perforce applications are defined below.

Security level	Server behavior
0 (or unset)	Legacy support: passwords are not required. If passwords are used, password strength is not enforced. Users with passwords can use either their P4PASSWD setting or the p4 login command for ticket-based authentication. Users of old Perforce applications are unaffected.
1	Legacy support: Strong passwords are required for users of post-2003.2 Perforce applications, but existing passwords are not reset. Pre-2003.2 Perforce applications can set passwords with p4 passwd or in the p4 user form, but password strength is not enforced. Users with passwords can use either their P4PASSWD setting or the p4 login command for ticket-based authentication. The dm.password.minlength configurable can be set to enforce a minimum password length.
2	Legacy support: All unverified strength passwords must be changed. Users of pre-2003.2 Perforce applications cannot set passwords. Users at release 2003.2 or higher must usep4 passwd and enter their passwords at the prompt. Setting passwords with the p4 user form or thep4 passwd -O oldpass -P newpass command is prohibited. On Windows, passwords are no longer stored in (or read from) the registry. (Storing P4PASSWD as an environment variable is supported, but passwords set with p4 set P4PASSWD are ignored.) Users who have set strong passwords with a 2003.2 or higher Perforce application can use either their P4PASSWDsetting for password-based authentication, or the p4 login command for ticket-based authentication. The dm.password.minlength configurable can be set to enforce a minimum password length.
3	All password-based authentication is rejected. Users must use ticket-based authentication (p4 login). If you have scripts that rely on passwords, use p4 login to create a ticket valid for the user running the script, or use p4 login -p to display the value of a ticket that can be passed to Perforce commands as though it were a password (that is, either from the command line, or by setting P4PASSWD to the value of the valid ticket). The dm.password.minlength configurable can be set to enforce a minimum password length.
4	Authenticated service users must be used for all replica server and remote depot connections to this server.

if you run the command p4 configure show, it'll show the current configuration.
Problem:
 p4 configure set security=3

Resolution:
We ran p4 -ztag info, gives us the ServerID as "servername"

To reset the security level
we found the Perforce Root,
[/var/libp4d] p4d -r /var/lib/p4d -J /var/lib/p4d/journal/journal.jnl "-cset p4server4#security=1"