[DOCS-9191] Ops Manager and Cloud Manager Agents Kerberos environment variables Created: 24/Oct/16 Updated: 06/Mar/17 Resolved: 03/Mar/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Emilio Scalise | Assignee: | Anthony Sansone (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 6 years, 49 weeks, 2 days ago |
| Epic Link: | C/OM Security |
| Story Points: | 0.5 |
| Description |
|
Hi, The Monitoring, Backup and Automation agents can use two OS environment variables to set specific Kerberos parameters:
This is something that should be documented in:
Please note that the KRB5CCNAME should be set to different files (one per Agent process) if there are multiple agents running on the same server. If you are running for example a Monitoring Agent and a Backup Agent on a server, they should use different kerberos cache files by using different KRB5CCNAME values. |
| Comments |
| Comment by Githook User [ 06/Mar/17 ] |
|
Author: {u'username': u'atsansone', u'name': u'Tony Sansone', u'email': u'tony.sansone@mongodb.com'}Message: ( |
| Comment by Githook User [ 06/Mar/17 ] |
|
Author: {u'username': u'atsansone', u'name': u'Tony Sansone', u'email': u'tony.sansone@mongodb.com'}Message: ( |
| Comment by Emilio Scalise [ 09/Feb/17 ] |
|
Hi tony.sansone, Here are the clarifications you requested on this. The krb5ConfigLocation should be equivalent to setting the KRB5_CONFIG environment variable. There is no other way to set a specific Kerberos cache file other than using the KRB5CCNAME environment variable. Kind regards, |