ipsec: mobile page needs migration to MVC/API and/or split of legacy feature set #8349
Closed
2 tasks done
Comments
|
As reference, this is how mobile users are set up in Connections without the mobile users page necessary: |
|
The reason for migration is mostly for the extensions, which are used for both. |
AdSchellevis
added a commit
that referenced
this issue
Feb 26, 2025
AdSchellevis
added a commit
that referenced
this issue
Feb 27, 2025
AdSchellevis
added a commit
that referenced
this issue
Feb 27, 2025
…ings" for #8349 Rename previous "advanced settings" to "mobile & advanced settings" to guide people into the right direction, strongswan.conf contains both sets of data. Keep legacy page for settings that are only relevant for the old components. Since our pam authenticator hooks into the configuration, refactor to use the model as well. Cleanup code in the model that was only used in the legacy glue.
AdSchellevis
added a commit
that referenced
this issue
Feb 28, 2025
…ings" for #8349 (#8380) Rename previous "advanced settings" to "mobile & advanced settings" to guide people into the right direction, strongswan.conf contains both sets of data. Keep legacy page for settings that are only relevant for the old components. Since our pam authenticator hooks into the configuration, refactor to use the model as well. Cleanup code in the model that was only used in the legacy glue.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Is your feature request related to a problem? Please describe.
Since the legacy components move to a plugin the mobile page needs some attention of what most stay in core and what doesn't.
Describe the solution you like
Migrate or split
vpn_ipsec_mobile.php.Describe alternatives you considered
Removing the code or keeping as is. Not a great plan.
Additional context
#8348
The text was updated successfully, but these errors were encountered: