Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • NetworkManager-openconnect NetworkManager-openconnect
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 59
    • Issues 59
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOMEGNOME
  • NetworkManager-openconnectNetworkManager-openconnect
  • Issues
  • #53
Closed
Open
Issue created May 06, 2021 by Aaron Barany@here-abarany

usergroup not forwarded from the auth-dialog to NetworkManager for the VPN connection

When a usergroup is provided with the gateway address (e.g. vpn.company.com/usergroup), it is used for the initial connection made in the auth-dialog, but isn't forwarded to NetworkManager for the final VPN connection used by the system. As a result, the second connection either fails or registers as connected and doesn't operate properly.

The usergroup is provided by the urlpath in OpenConnect, and can be added to the NM_OPENCONNECT_KEY_GATEWAY as a path to the URL constructed with the hostname and port.

Assignee
Assign to
Time tracking