- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
MIT principal and keytab management via Amabari 2.1.2
- Labels:
-
Apache Ambari
Created 12-01-2015 10:23 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can I use Ambari 2.1.2 (API or other) to manage principals and keytab deployments for non-ambari controlled services?
Created 12-01-2015 10:26 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No, this is not supported.
Created 12-01-2015 10:26 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No, this is not supported.
Created 12-01-2015 10:37 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Created 12-03-2015 08:53 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ambari can only manage the principals and keytabs for the services managed by it. The pricipal and keytabs are actually provided as part of the configuration files with the stack definition.
For e.g. for Storm, looking at the stack , you can see -
.... "name": "storm_components", "principal": { "value": "${storm-env/storm_user}-${cluster_name}@${realm}", "type": "user", "configuration": "storm-env/storm_principal_name" }, "keytab": { "file": "${keytab_dir}/storm.headless.keytab", "owner": { "name": "${storm-env/storm_user}", "access": "r" }, ....
Ambari does not support managing principals and keytabs of other components that are outside its purview.
