Read-only users cannot change preferences or their password

[nblumhardt]

          This seems to still occur with `Seq 2023.1.9162`

This is a login with the User (read-only) role

Originally posted by @CumpsD in #739 (comment)

[nblumhardt]

We originally decided "read-only" would mean strictly read-only, i.e., disallow access to any write endpoints. This isn't a great choice for how read-only accounts are used in the majority of cases. It's unexpected by customers, so I'll mark this as a bug.

This ticket proposes to allow read-only accounts to update their own user preferences and password (if username/password authentication is in use).

I've also marked this as a breaking change, because there's a faint possibility that customers today are relying on the current behavior for some unforeseen use cases.

[nblumhardt]

As of 2023.2, read-only users will be able to change their own:

• Account trivia (display name and email)
• Password
• Theme
• Display preferences
• Query timeout

[CumpsD]

2023.2 is not yet on dockerhub, right?

[liammclennan]

@CumpsD That is correct. 2023.2 has not been released.

[CumpsD]

@CumpsD That is correct. 2023.2 has not been released.

When is the release planned?

[nblumhardt]

Aiming for next Tuesday (6th June), but still a few loose ends to tie up so may need a little extra time depending on how it all comes together :-)

[CumpsD]

Thanks!