writefreely icon indicating copy to clipboard operation
writefreely copied to clipboard

Password-protected blog doesn't show correctly

Open idelem opened this issue 5 years ago • 4 comments

Describe the bug

I have a password-protected blog which was working as expected a while ago (i.e. tested using different devices and browsers). Today I tried to read the blog from another device, say device A, but I forgot the password. So I logged in on device B and changed the password. But I cannot view the blog from A even when the password is correct.

I think the authentication actually passed, because wrong inputs will prompt "Incorrect Password" on the page, while the page returned doesn't have this section.

I tried with another blog and it failed as well. I wonder what might have been broken, because it used to work a month ago.

Is there any error log I can look into?

Steps to reproduce (if necessary)

Steps to reproduce the behavior:

  1. Switch to passwd-protected mode and set password
  2. Try to input password from elsewhere
  3. Page still shows input form

Expected behavior

What should've happened?

Should've been able to read the blog.

Application configuration

  • Single mode or Multi-user mode? Multi-user mode?
  • Database? sqlite
  • Open registration? no
  • Federation enabled? yes Version or last commit: 0.11

idelem avatar Apr 15 '20 07:04 idelem

Thanks for reporting this! My first instinct is that there's an expiration issue with the cookie that keeps you "logged in" to password-protected blogs. But we'll need to confirm that.

thebaer avatar Apr 15 '20 14:04 thebaer

I tried the steps to reproduce the error & it worked for me (was able to use updated password on new device). Could you reset your cookies for your instance and try this again @idelem? It might very well be a cookie issue that @thebaer mentioned.

cjeller1592 avatar Apr 16 '20 17:04 cjeller1592

@cjeller1592 Yes that worked, thank you!

(I'll leave this open because I still consider it a bug. )

idelem avatar Apr 17 '20 02:04 idelem

You're welcome @idelem! And yes, I agree to leave it open too — the solution is only a temporary fix until a more permanent one can come about.

cjeller1592 avatar Apr 17 '20 13:04 cjeller1592