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
change password via UI #2130
Comments
Hi @alanpaulkwan, could you add a bit more context please? :) @keithCuniah has been looking at OAuth measures, but for now this is scoped to our cloud offering. If you need help setting things up, we can also schedule a calendly meeting. |
Hi yes, sorry.
I could either try this when running Argilla, or export it first locally then start Argilla under that user. I can't log in, it doesn't seem like the password has changed. Maybe I'm doing something wrong but it is a bit difficult to figure out. The user interface would be easier. |
Could it potentially be caused by this issue . I initially also had a problem with this. @frascuchon do you think we could possibly integrate this workflow in the Argilla package. This would allow us to add a check for |
I think is a great idea to have this workflow as an util of the package. I got this question very often and even had issues myself too 😃 |
@alanpaulkwan I created a feature request for this. #2196 could you provide some input on what you think might work best? |
wow, thank you for following up. at the very extreme, Apache Superset is a great example. they create two constructs: roles + users. they pre-define both. when you start it, you use the default password and can at the top right, there is a "User Management" page where you can
For roles, there is Admin, Alpha, Gamma, etc. I guess if you wanted to be fully featured, I would imagine one would could imagine a user who can administer users, a user who can write to datasets, a user who can annotate, a user who can override other annotations etc. |
This issue is stale because it has been open for 90 days with no activity. |
This issue was closed because it has been inactive for 30 days since being marked as stale. |
I have tried EXPORT $ARGILLA.... and following the example closely, but to no avail. I am wondering if it would be better to just allow people to change their password/add users via a webform.
The text was updated successfully, but these errors were encountered: