Summary
The VPN UI currently assumes that visible VPN entries always come from importable VPN profiles.
If the backend reports an active VPN or tunnel connection that does not have a corresponding importable profile entry, the popout and settings UI can still show an empty state such as "No VPN profiles", even though a connection is active.
Steps to reproduce
- Have DMS report an active VPN or tunnel connection through the network service.
- Ensure that active connection is not present in
network.vpn.profiles.
- Open the VPN popout or the VPN section in Settings.
Actual behavior
The UI shows the empty "No VPN profiles" state even while an active VPN or tunnel connection exists.
Expected behavior
Active VPN or tunnel connections should still be shown in the UI even when they are not backed by an importable profile.
Entries that are not importable or manageable profiles should also avoid showing edit, delete, or expand actions intended for imported VPN configs.
Notes
This appears to affect both the popout VPN list and the Settings VPN list, since both currently render from the profiles model only.
Summary
The VPN UI currently assumes that visible VPN entries always come from importable VPN profiles.
If the backend reports an active VPN or tunnel connection that does not have a corresponding importable profile entry, the popout and settings UI can still show an empty state such as "No VPN profiles", even though a connection is active.
Steps to reproduce
network.vpn.profiles.Actual behavior
The UI shows the empty "No VPN profiles" state even while an active VPN or tunnel connection exists.
Expected behavior
Active VPN or tunnel connections should still be shown in the UI even when they are not backed by an importable profile.
Entries that are not importable or manageable profiles should also avoid showing edit, delete, or expand actions intended for imported VPN configs.
Notes
This appears to affect both the popout VPN list and the Settings VPN list, since both currently render from the profiles model only.