Can i disable the new password to shutdown "feature?"

Get Help
1

latest octoprint update added a thing where when i click shutdown in the browser it goes "please reauthenticate! blah blah" and i gotta put my password in and click the button to perform the command.

this is an unwelcome change after years of not needing to do this, but i cannot for the life of me find if there is an option to turn this "feature" off - adhd makes reading 1000000 boring options almost impossible and it never hurts to just ask someone else who already knows where it is.

cheers

2

I second that.. even my bank account is less secured than current Octoprint.

i tried to add the option for

defaultReauthenticationTimeout: 8000

or
defaultReauthenticationTimeout: 0

in config.yaml
NO LUCK , still asks for it on several actions like plugin search or shutdown

i do not need all that stuff.. okay for those who want it..but my printers are not connected to the internet nor will there by anyone in my rooms to cope with.

Harald

3

That would be a reason to change my bank if I were you, just saying :wink:

It should be

accessControl:
  defaultReauthenticationTimeout: 0

in config.yaml. Setting it to 0 should disable the reauthentication requirement altogether, and I just tested this successfully too.

Other than that, currently there's no more configuration options here, but I'll take this feedback with me and see that I add some more granular control, and also expose that on the UI. That will have to wait until 2026 however, I'm wrapping up for the year and am in desperate need of a vacation and coding break.

4

I tried again and found :

It works when the default.... line is the FIRST line after the access... line

accessControl:
  defaultReauthenticationTimeout: 0
  autologinAs: blabla
  autologinHeadsupAcknowledged: true
  autologinLocal: true
  enabled: false
  localNetworks:
  - 192.168.1.0/24
  - 127.0.0.0/8
  - ::1/128
api:
...

it did not work when the line was further down in that yaml branch

..solved...

5

The location of the line in the block shouldn't make a difference at all, and that's also not something that is checked in any way, the whole yaml file is read in by the yaml library, parsed, and returned as a whole. But whitespace masters a lot here and can easily cause issues.

Hence my promise to expose this config on the UI in 1.12.0.