Github user revans2 commented on the issue:
https://github.com/apache/storm/pull/2915
@liu-zhaokun Currently the only way that the user name is transmitted from
the client to the server is through authentication because authentication is
secure and we didn't want to accidentally enable a false sense of security when
auth is disabled. We set the owner of the topology to the name of the user
running nimbus because that is who the topology was truly running as.
If you really want to make this happen you will need to do one of two
things. Either
1. install some type of authentication, could be digest which would not be
too difficult to get working, or
2. modify the clients to set a config with the user they want the topology
to run as and then have nimbus honor it.
If you do the second option I would want a config to enable this new
behavior. Something like
```java
/**
* If true nimbus will honor the config user.name from the topology
conf, and set it as the
* owner of the topology. This only has an impact when authentication
is disabled. Be
* very careful when using this when supervisor.run.worker.as.user is
enabled as any user
* can become nearly any user on the box.
*/
@isBoolean
public static final String NIMBUS_USE_UNSAFE_USER_CONFIG =
"nimbus.use.unsafe.user.config";
```
Just so you know `user.name` is the name of the system property that java
sets with the name of the unix user your java process is running as, but it is
not safe to assume it is always correct because it can be modified/overwritten.
---
