We have a GitHub Enterprise Server working against an example of TeamCity which has created agents on many servers < To certify, we are currently adding the SSP key manually and referencing them but this is not a scalable solution because we need to add keys to all the build agent boxes < P> Does anyone manage it Sector can imagine a better way?
Note: We can not create a "build" user in the grid and then we can add each of our projects.
If I understand, then I see:
Can I use my organization's LDAP? Directory for managing user access?
Yes GitHub Enterprise supports user authentication via external LDAP or CAS services. The setup process includes a step to configure your organization's LDAP / CAS server information.
By default, GitHub runs in the Authenticated Authentication Mode with the user information stored in the corporate Hit Hub Enterprise Database.
If you can not create the "creation" user in the gitub and then add each of our projects ", it means you can not (or do not want to) do the same Re-use the public / private SSP key for each build server.
This will give you access to LDAP-based credentials with https access instead of SDP address.
Publish / Register on GitHub Enterprise Server Karan There is no SSB key for the field, so this is possible "solution / workaround". But it will leave you with any other problem:
- What are you on each of those servers (actual LDAP)?
- How will you manage password renewal which is mandatory for LDAP accounts every x month?
Comments
Post a Comment