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

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

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

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.

2 Likes

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...

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.

1 Like

I have no accessControl section

api:
key: ZRpIwYwAdyf7hQibRAxfukwyZuAfJ_7QQVVpGp7BSJ4
plugins:
announcements:
_config_version: 1
classicwebcam:
_config_version: 1
snapshot: http://127.0.0.1:8080/?action=snapshot
stream: /webcam/?action=stream
cura:
cura_engine: null
discovery:
publicPort: 80
upnpUuid: d2c153cc-5a26-491e-b1c0-3de1cf32c758
errortracking:
unique_id: 1512d295-0e6a-4ca8-a81d-7dbab333e795
gcodeviewer:
_config_version: 1
softwareupdate:
_config_version: 9
tracking:
unique_id: f21a048c-0ca4-4e07-9a38-5ac87912c155
virtual_printer:
_config_version: 1
printerProfiles:
default: _default
server:
commands:
serverRestartCommand: sudo service octoprint restart
systemRestartCommand: sudo shutdown -r now
systemShutdownCommand: sudo shutdown -h now
secretKey: 10033c39cd83a5030f6c5187abbfc027f6dd1b024ed40a45b7ec9886dd396d25
seenWizards:
file_check: 1
webcam:
ffmpeg: /usr/bin/ffmpeg

you can add it.

Is it just me, or is vi weird in octopi?

Personally I use nano. The base for OctoPi is Pi OS, so whatever vi is included with that is what you are experiencing.

vi works for me (but I'm not very good with it). I'm much better with nano.

What is "weird" about it? What terminal interface are you using?

Using Putty to SSH in.

For example the up arrow key types a "A"

vi is what I've been using on headless RHEL based servers for something like 15 years so ubderstanably it's what I try first.

I'm using PuTTY (64-bit) v0.83 on Windows 11 and SSH into multiple RPi systems. The up arrow key works as expected in vi.

I also tried the Windows 11 Terminal app and Windows 11 ssh command and the arrow keys worked there as well. I also checked with nano and the arrow keys also work as expected.

I'm guessing its not a "vi" issue but a keyboard mapping issue. What does localectl show?

Mine shows:

pi@octopi:~ $ localectl
System Locale: LANG=en_GB.UTF-8
    VC Keymap: (unset)
   X11 Layout: us
    X11 Model: pc105

niamh@octopi-test:~ $ localectl
System Locale: LANG=en_GB.UTF-8
VC Keymap: (unset)
X11 Layout: gb
X11 Model: pc105

Another thing is when I press insert it doesn't show "-- INSERT -- " on the bottom line

Thanks, I was going crazy about this new password question that came with recent update and was also looking through all settings twice. I considered to post here, and luckily found the solution before.

(I use random passwords and the OctoPrint password is stored in the cookie after first login. So having this password prompt was a nightmare for me; as only reason is to keep linux happy. The power switch for the Raspberry is just next to me, but I prefer graceful shutdown).