Github user arunmahadevan commented on a diff in the pull request:
https://github.com/apache/storm/pull/2081#discussion_r113686513
--- Diff: docs/SECURITY.md ---
@@ -423,16 +423,18 @@ nimbus.impersonation.acl:
### Automatic Credentials Push and Renewal
Individual topologies have the ability to push credentials (tickets and
tokens) to workers so that they can access secure services. Exposing this to
all of the users can be a pain for them.
-To hide this from them in the common case plugins can be used to populate
the credentials, unpack them on the other side into a java Subject, and also
allow Nimbus to renew the credentials if needed.
-These are controlled by the following configs. topology.auto-credentials
is a list of java plugins, all of which must implement IAutoCredentials
interface, that populate the credentials on gateway
-and unpack them on the worker side. On a kerberos secure cluster they
should be set by default to point to
org.apache.storm.security.auth.kerberos.AutoTGT.
-nimbus.credential.renewers.classes should also be set to this value so
that nimbus can periodically renew the TGT on behalf of the user.
+To hide this from them in the common case plugins can be used to populate
the credentials, unpack them on the other side into a java Subject, and also
allow Nimbus to renew the credentials if needed. These are controlled by the
following configs.
+
+`topology.auto-credentials` is a list of java plugins, all of which must
implement the `IAutoCredentials` interface, that populate the credentials on
gateway
--- End diff --
Gateway is the host from where the topology is submitted.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
