scmuser created the topic: Need innovative Idea in Perforce Server Administration
Hi,
I have one scenario and I am looking for solution in Configuration Tools such as Perforce. Can you please let me know is there any common solution available in Perforce or i will have to developed a new application.
Scenario: I have 50 Perforce Server Instance running and i would like to minimize the time spending on admin work such a user creation and deletion.
Is there any ways where i can centralize all perforce server following activities…
1. User Creation /Deletion
2. Group Creation/ Deletion
3. Assigning Depot Access to group such as modifying protect table
rajeshkumar replied the topic: Re: Need innovative Idea in Perforce Server Administration
Answer found from Perforce Support – The feature (centralised server) you are looking for has been available undocumented for several years. However since the 2010.2 release, it is now fully supported and documented:
Most organizations use only one Perforce Server for the entire organization, but over time, as organizations grow and merge, or as different groups within an organization need to share data, an organization can find itself with multiple Perforce Servers across a common user base.
If you are running multiple Perforce servers, you can configure them to retrieve protections and licensing data from a centralized authorization server. By using a centralized server, you are freed from the necessity of ensuring that all your servers contain the same users and protections entries.
If a user does not exist on the central authorization server, that user does not appear to exist on the outer server. If a user exists on both the central authorization server and the outer server, the most permissive protections of the two lines of the protections table are assigned to the user.
You can use any existing Perforce Server in your organization as your central authorization server. The license file for the central authorization server must be valid, as it governs the number of licensed users that are permitted to exist on outer servers. To configure a Perforce Server to use a central authorization server, set P4AUTH before starting the server, or specify it on the command line when you start the server.
If your server is making use of a centralized authorization server, the following line will appear in the output of p4 info:
…
Authorization Server: host:port
Where host:port refer to the host and port number of the central authorization server.
In the following example, an outer server (named server2) is configured to use a central authorization server (named central). The outer server listens for user requests on port 1999 and relies on the central server’s data for user, group, protection, review, and licensing information. It also joins the protection table from the server at central:1666 to its own protections table.
For example:
p4d -In server2 -a central:1666 -p 1999
When you configure a central authorization server, outer servers forward the following commands to the central server for processing:
group, groups, passwd, review, reviews, user, users, protect, protects, login, logou
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn
- DevOps Certified Professionals (DCP)
- Site Reliability Engineering Certified Professionals (SRECP)
- Master in DevOps Engineering (MDE)
- DevSecOps Certified Professionals (DSOCP)
URL - https://www.devopsschool.com/certification/
My Linkedin - https://www.linkedin.com/in/rajeshkumarin
- What is DevContainer? - December 20, 2024
- Top 10 Website Development Companies in Vadodara - December 20, 2024
- Compare SAST, DAST and RASP & its Tools for DevSecOps - December 19, 2024
