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

Include a gateway user in Standard configuration by default #3151

Closed
alxndrsn opened this issue Feb 23, 2017 · 11 comments
Closed

Include a gateway user in Standard configuration by default #3151

alxndrsn opened this issue Feb 23, 2017 · 11 comments
Labels
Won't fix: Ancient Too old to investigate

Comments

@alxndrsn
Copy link
Contributor

This would save one extra step of configuration when setting up a Standard instance.

@nice-snek nice-snek added the Status: Blocked waiting for triage Blocked waiting for prioritisation label Mar 28, 2017
@SCdF
Copy link
Contributor

SCdF commented Apr 3, 2017

@alxndrsn what is involved here? Standard configuration is a collection of app settings and forms right? How could we include a default user? Or are you suggesting we write a migration script / init check to add a gateway user if it doesn't already exist?

@alxndrsn
Copy link
Contributor Author

alxndrsn commented Apr 3, 2017

I'm not fussed how it's implemented, but I think there should be a gateway user set up out-of-the-box or as part of the initial setup process (I think there is a wizard for this).

@SCdF
Copy link
Contributor

SCdF commented Apr 3, 2017

@abbyad / @browndav do you two have any thoughts about this? It's hard to tell where it should live: it is something we should be adding to the standard setup script? Or is this something medic-os is supposed to do somehow?

I'm not sure how our current single admin user is setup honestly.

@SCdF SCdF assigned ghost and abbyad Apr 3, 2017
@abbyad
Copy link
Contributor

abbyad commented Apr 4, 2017

Doing this via a script is not ideal since creating users with medic-api also creates a Place and Person for the user -- it was not designed for creating gateway users.

If we want to create the gateway user automatically then it could be done by concierge. @browndav can provide more details on that.

Alternatively we could just have a seed image for Standard that is a snapshot of an instance that is already configured, and includes a gateway user. cc @henokgetachew

@abbyad abbyad removed their assignment Apr 4, 2017
@ghost
Copy link

ghost commented Apr 4, 2017

I'd prefer we not use images of preconfigured instances; that'll cause reuse of (locally-configured) service account passwords and host keys. We already create a number of CouchDB users for use by local services; it wouldn't be that hard to add a gateway user via concierge if we can document the requirements here.

@SCdF
Copy link
Contributor

SCdF commented Apr 6, 2017

@alxndrsn can you document the requirements for @browndav. It sounds easy and like a nice thing to smooth over, so scheduled.

@SCdF SCdF removed their assignment Apr 6, 2017
@SCdF SCdF added 1 - Scheduled and removed Status: Blocked waiting for triage Blocked waiting for prioritisation labels Apr 6, 2017
@alxndrsn
Copy link
Contributor Author

alxndrsn commented Apr 6, 2017

I think this should do it:

username: gateway
role: gateway

@alxndrsn alxndrsn removed their assignment Apr 11, 2017
@ghost
Copy link

ghost commented Apr 18, 2017

It looks like this needs two distinct steps:

  • Patch concierge to add the appropriate gateway user on first run
  • Backpatch existing machines by creating the account via shell script (and I have one)

@garethbowen garethbowen modified the milestones: May 23 - June 6, June 6 - June 20 Jun 6, 2017
@garethbowen
Copy link
Member

This should be done but it's not a priority right now. Moving out of the milestone.

@garethbowen garethbowen removed this from the June 26 - July 10 milestone Jul 10, 2017
@abbyad
Copy link
Contributor

abbyad commented Jun 25, 2018

@browndav is this still in progress, or completed already?

@garethbowen
Copy link
Member

Closing as ancient.

@garethbowen garethbowen added the Won't fix: Ancient Too old to investigate label Jul 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Won't fix: Ancient Too old to investigate
Projects
None yet
Development

No branches or pull requests

5 participants