[07:36:15]
<Maranda> kts: it does store hashes differently possibly, Metronome stores hashes for SHA1, SHA256 and SHA512
[07:36:56]
<kts> Interesting -- any reason why using mirandactl generated plaintext? I don't recall prosodyctl doing that, but I'll admit it has been years since I manually had to use that tool
[07:37:43]
<Maranda> I'm not sure I don't use that tool
[07:38:51]
<Maranda> Did you perhaps load the correct authentication backend?
[07:39:46]
<Maranda> Aka internal_hashed
[07:40:13]
<kts> Let me double-check -- I believe that is the default
[07:41:07]
<kts> Hmm, it would seem not. Is there any place where that is documented?
[07:41:23]
<Maranda> Also auth configuration directives will be ignored in the global section
[07:42:02]
<Maranda> And Metronome defaults to internal_plain not internal_hashed
[07:42:24]
<kts> Good to know
[07:43:53]
<Maranda> Set the auth directive in the VirtualHost / Host section
[07:44:25]
<kts> I have done so and have successfully logged into an account from prosody
[07:44:31]
<kts> Thank you
[07:46:36]
<Maranda> I suggest you to change your password once logged so that Metronome generates all hashes
[07:46:55]
<Maranda> (you can change it to the same one)
[13:19:38]
<Maranda> You can find documentation here btw: https://metronome.im/documentation
[13:59:18]
<kts> I've been referencing that