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

Add default ETL user to OpenSRP deployments #312

Open
gstuder-ona opened this issue Jan 27, 2021 · 2 comments
Open

Add default ETL user to OpenSRP deployments #312

gstuder-ona opened this issue Jan 27, 2021 · 2 comments
Assignees

Comments

@gstuder-ona
Copy link

gstuder-ona commented Jan 27, 2021

When the canopy team is asked to integrate OpenSRP with the canopy platform, one of the most time-consuming steps is often just getting credentials for an ETL user for a particular OpenSRP instance. We generally can't use a generic test user, as those users don't have permission for the "getAll" endpoint, so we're forced to find the owner of the OpenSRP instance and do a bunch of back-and-forth to have the owner manually create our user. Often the instance gets redeployed at some point (maybe weeks later), and I suspect the etl-user configuration isn't stored anywhere so it just "disappears" and our ETL flows just stop pulling data at what appears to be a random point in time.

It'd be nice if, out of the box, OpenSRP was setup with a default ETL user so that all that would be required would be the opensrp send a password (and keycloak credentials) for that particular instance. If there's another solution that achieves this or I misunderstand how opensrp credentials are configured that'd be cool to know too.

@gstuder-ona
Copy link
Author

@pld just attaching you as this is a cross-team issue - not super high priority, but we've seen credentials disappear enough times that I think it's worth addressing

@pld
Copy link
Member

pld commented Jan 27, 2021

k assigning to @manutarus, this sounds like it'd fit into the k8s work on OpenSRP

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

3 participants