Page MenuHomeVyOS Platform

Trying to commit an OpenConnect configuration without any local users results in an exception
Closed, ResolvedPublicBUG

Description

If you set OpenConnect authentication mode to local but don't create any users, the script crashes.

# set vpn openconnect authentication mode local password
[edit]
foo_admin@vyos# commit
[ vpn openconnect ]
VyOS had an issue completing a command.

We are sorry that you encountered a problem while using VyOS.
There are a few things you can do to help us (and yourself):
- Contact us using the online help desk if you have a subscription:
  https://support.vyos.io/
- Make sure you are running the latest version of VyOS available at:
  https://vyos.net/get/
- Consult the community forum to see how to handle this issue:
  https://forum.vyos.io
- Join us on Slack where our users exchange help and advice:
  https://vyos.slack.com

When reporting problems, please include as much information as possible:
- do not obfuscate any data (feel free to contact us privately if your 
  business policy requires it)
- and include all the information presented below

Report time:      2024-01-10 10:48:47
Image version:    VyOS 1.5-rolling-202401080717
Release train:    current

Built by:         [email protected]
Built on:         Mon 08 Jan 2024 09:07 UTC
Build UUID:       6254ca59-32a0-4f18-935f-7fee2267e11c
Build commit ID:  92195009af863c

Architecture:     x86_64
Boot via:         livecd
System type:      KVM guest

Hardware vendor:  innotek GmbH
Hardware model:   VirtualBox
Hardware S/N:     0
Hardware UUID:    33d93ca6-9d47-de4a-bb49-85ed5101970c

Traceback (most recent call last):
  File "/usr/libexec/vyos/conf_mode/vpn_openconnect.py", line 287, in <module>
    verify(c)
  File "/usr/libexec/vyos/conf_mode/vpn_openconnect.py", line 94, in verify
    if not ocserv["authentication"]["local_users"]:
           ~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^
KeyError: 'local_users'



[[vpn openconnect]] failed
Commit failed

Details

Difficulty level
Unknown (require assessment)
Version
1.4.0-rc1
Why the issue appeared?
Will be filled on close
Is it a breaking change?
Perfectly compatible
Issue type
Bug (incorrect behavior)