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
Comments
@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? |
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). |
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 |
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 |
I think this should do it: username: |
It looks like this needs two distinct steps:
|
This should be done but it's not a priority right now. Moving out of the milestone. |
@browndav is this still in progress, or completed already? |
Closing as ancient. |
This would save one extra step of configuration when setting up a Standard instance.
The text was updated successfully, but these errors were encountered: