Support user password resets #198
Labels
No labels
Android
CS::needs customer feedback
CS::needs follow up
CS::needs on prem installation
CS::waiting
Chrome
Design:: Ready
Design:: in progress
Design::UX
E2EE
Edge
Firefox
GDPR
Iteration 13 IM
Linux
MacOS
Need::Discussion
Need::Steps to reproduce
Need::Upstream fix
Needs:: Planning
Needs::Dev-Team
Needs::More information
Needs::Priority
Needs::Product
Needs::Refinement
Needs::Severity
Priority::1-Critical
Priority::2-Max
Priority::3-Impending
Priority::4-High
Priority::5-Medium
Priority::6-Low
Priority::7-None
Progress::Backlog
Progress::Review
Progress::Started
Progress::Testing
Progress::Triage
Progress::Waiting
Reporter::Sentry
Safari
Target::Community
Target::Customer
Target::Internal
Target::PoC
Target::Security
Team:Customer-Success
Team:Design
Team:Infrastructure
Team:Instant-Messaging
Team:Product
Team:Workflows
Type::Bug
Type::Design
Type::Documentation
Type::Feature
Type::Improvement
Type::Support
Type::Tests
Windows
blocked
blocked-by-spec
cla-signed
conduit
contribution::advanced
contribution::easy
contribution::help needed
from::review
iOS
p::ti-tenant
performance
product::triage
proposal
refactor
release-blocker
s: dart_openapi_codegen
s::Famedly-Patient
s::Org-Directory
s::Passport-Generator
s::Requeuest
s:CRM
s:Famedly-App
s:Famedly-Web
s:Fhiroxide
s:Fhiroxide-cli
s:Fhiroxide-client
s:Fhirs
s:Hedwig
s:LISA
s:Matrix-Dart-SDK
s:Role-Manager
s:Synapse
s:User-Directory
s:WFS-Matrix
s:Workflow Engine
s:dtls
s:famedly-error
s:fcm-shared-isolate
s:matrix-api-lite
s:multiple-tab-detector
s:native-imaging
severity::1
severity::2
severity::3
severity::4
technical-debt
voip
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Matthias/conduit#198
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It seems that currently if a user forgets their password, there is no way to do anything about it. It's certainly a good thing that the password can't be recovered, but it would be nice, from server administrator point of view, to be able to reset it (to allow the user to log in from another device, for example).
assigned to @jfowl
Currently, there is no "official" way to do this.
What you can do, is edit the database and change the password manually.
In the sqlite database file is a table called
userid_password
where theValue
is an argon2 hash.You can use something like https://argon2.online/ to create a hash for a temporary password, overwrite the old hash with it and then change the password from within your client again.
unassigned @jfowl
Thanks for confirming this!
I wouldn't mind doing this at all, but unfortunately I don't think I'm using an SQLite database, I think the
db
file in mydatabase_path
directory must be a sled database (at least it's definitely not an SQLite one). Is it possible to edit this one interactively? I couldn't find any tool for doing it for sled databases (assuming this is what it is).Unless you explicitly changed something, you are using SQLite. Assuming you are running Linux, would you mind installing sqlite3 and try run
sqlite3 conduit.db
? You can confirm the presence of the user table with this queryI didn't change anything in the default config, but it's a version from a few months ago (
eeb0b59b76
), so maybe the defaults have changed since then?In any case, I'm pretty sure this is not an SQLite database, I know how those look like and this is not it:
So assuming you are using the sled database, maybe try to use https://github.com/ShadowJonathan/conduit_toolbox to convert it to a SQLite database, edit it and continue to use it with Conduit v0.2.0.
Some ideas:
emergency_password
to Conduit.tomlWhen the emergency password is in the config, a warning will be sent into the admin room on each restart.
Thanks, (1) seems like exactly what I've been looking for but, and sorry if I'm missing something obvious, what exactly is the command to use? I don't see anything relevant in
/help
output except, potentially,/verify
, but I don't really know how to use it. Thanks again!P.S. Also thanks for the conduit toolbox link, Jonas, this will surely be useful when I finally migrate the server to a newer version. But the fact is that it has been working so well without any intervention on my part so far that I have almost no motivation to touch it. Job too well done, guys :-)
There might have been a misunderstanding: These are only ideas, nothing that is currently implemented.
Oops, sorry, I've indeed misunderstood, thanks for clearing this up. All I can say is that a new admin command for doing this would seem to be a useful addition.
changed title from {-Possibility to reset a password for the user?-} to {+Support user password resets+}
I did this, and ended up with a panic the next time conduit started (as it seems to have not stored the
UPDATE
asBLOB
) - filed as #250:assigned to @M0dEx
So how would we do 1)?
Have a command for the administrator where they could set the password and then send it to the user?
Perhaps have a switch to automatically generate it, so the administrator does not have to?
created branch
198-support-user-password-resets
to address this issuementioned in merge request !339
Yeah I'd say
@conduit password-reset @userid
and then @conduit replies with a random passwordmentioned in issue #252
mentioned in commit
9e29dc808f