Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Permissions Explanation #100

Open
cinderblock opened this issue Sep 13, 2016 · 0 comments
Open

Permissions Explanation #100

cinderblock opened this issue Sep 13, 2016 · 0 comments

Comments

@cinderblock
Copy link

I'm trying to understand guvnor's permission model.

In particular, I'd like each app I run to be run as a separate user and control all of the apps from my guvnor-web main user. I'd also like to be able to create other web accounts to enable access/control to specific apps or servers.

At first, I assumed that adding all of my servers' remoteconfigs to guvnor-web-hosts with the root user and secret would simply enable "root" access to all of my servers. Of course, this is not true.

I see that in guvnor-web-users, there are hashed passwords for a user for logging into the web interface, and "secrets" for the per-user-host configurations.

Setting the user and secret to match each remote machine's (not running guvnor-web) guvnor instance's guv remoteconfig enabled me to control the other server. I had to play around with this a bunch to get this to work. It was not clear from the documentation where each password/secret needs be used.

Is this the expected way to enable control from guvnor-web? This doesn't seem to enable any level of granularity on the permissions for other guvnor-web users accessing restricted sets of apps on other servers.

I'm probably missing some trick to make this all work well. Any clarification would be greatly appreciated. The documentation available on this subject is quite confusing and seemingly incomplete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant