Github user revans2 commented on the pull request:
https://github.com/apache/incubator-storm/pull/190#issuecomment-49372008
I really guess I didn't explain things very well in the JIRA. So the
current way IAutoCredentials and ICredentialsRenewer work with nimbus are.
IAutoCredentials will run on the gateway as the topology user. It gets
handed a map that it can place any credentials in needs into.
Those credentials are uploaded to nimbus, which places them in zookeeper.
Periodically nimbus will download the serialized credentials and hand them
to ICredentialsRenewer which will run as the nimbus user. If it modifies the
the credentials they are pushed to zookeeper.
At the same time the worker running as the topology user will download the
credentials from zookeeper and pass them to IAutoCredentials to the passed in
Subject with them. This repeats any time the credentials change in zookeeper.
What I would like to see is something where IAutoCredentials has an option
of not running on the gateway, or it is a noop on the gateway. Instead after
the credentials are submitted to nimbus, something similar to, or an extended
version of ICredentialsRenewer would run as the nimbus user and get the
credentials on behalf of the topology user.
The rest of the process would stay the same, except if a token is about to
expire completely. In that case it would fetch a brand new token.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
