starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Importing IKE proposal without authentication method is not possible #9099

New Issue
Closed
opened 2025-12-29 20:45:26 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:45:26 +01:00
Owner
Copy Link

Originally created by @markkuleinio on GitHub (Jan 17, 2024).

Originally assigned to: @jeremystretch on GitHub.

Deployment Type

Self-hosted

NetBox Version

v3.7.0

Python Version

3.11

Steps to Reproduce

Go to VPN - IKE Proposals - Add

  1. Name = GUITEST
  2. Authentication method = PSK
  3. Encryption algorithm = 256-bit AES (GCM)
  4. Group = Group 20
  5. Create

(= is successful)

Go to VPN - IKE Proposals - Import, use the same fields as above:

name,authentication_method,encryption_algorithm,group
IMPORTTEST,preshared-keys,aes-256-gcm,20

Expected Behavior

IKE proposal is imported successfully.

Observed Behavior

Error is shown:

Record 1 authentication_algorithm: This field is required.

In the import field options the authentication_algorithm field is shown as required even though it is not required in GUI.

Also, in the authentication_algorithm value list there is no "empty" option to use, thus it is not possible to import IKE proposals that use GCM, unless you fake the algorithm during the import.

Also note that if authentication algorithm is nevertheless set and you want to remove it, you have to single-edit the proposal: it is not possible to select all proposals in the list and use Edit Selected, as it is not possible to clear the field there.

Related to #14499 where GUI requirement for the authentication method was relaxed.

Originally created by @markkuleinio on GitHub (Jan 17, 2024). Originally assigned to: @jeremystretch on GitHub. ### Deployment Type Self-hosted ### NetBox Version v3.7.0 ### Python Version 3.11 ### Steps to Reproduce Go to **VPN - IKE Proposals - Add** 1. Name = GUITEST 2. Authentication method = PSK 3. Encryption algorithm = 256-bit AES (GCM) 4. Group = Group 20 5. Create (= is successful) Go to **VPN - IKE Proposals - Import**, use the same fields as above: ``` name,authentication_method,encryption_algorithm,group IMPORTTEST,preshared-keys,aes-256-gcm,20 ``` ### Expected Behavior IKE proposal is imported successfully. ### Observed Behavior Error is shown: **Record 1 authentication_algorithm: This field is required.** In the import field options the `authentication_algorithm `field is shown as required even though it is not required in GUI. Also, in the `authentication_algorithm `value list there is no "empty" option to use, thus it is not possible to import IKE proposals that use GCM, unless you fake the algorithm during the import. Also note that if authentication algorithm is nevertheless set and you want to remove it, you have to **single-edit** the proposal: it is not possible to select all proposals in the list and use **Edit Selected**, as it is not possible to clear the field there. Related to #14499 where GUI requirement for the authentication method was relaxed.
adam added the type: bugstatus: acceptedseverity: medium labels 2025-12-29 20:45:26 +01:00
adam closed this issue 2025-12-29 20:45:26 +01:00
adam commented 2025-12-29 20:45:26 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 17, 2024):

Seems like this was an oversight during the work on #14499.

@jeremystretch commented on GitHub (Jan 17, 2024): Seems like this was an oversight during the work on #14499.
adam commented 2025-12-29 20:45:27 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 17, 2024):

A similar discrepancy exists with the encryption_algorithm and authentication_algorithm fields on the IPSec proposal bulk import form.

@jeremystretch commented on GitHub (Jan 17, 2024): A similar discrepancy exists with the `encryption_algorithm` and `authentication_algorithm` fields on the IPSec proposal bulk import form.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label severity: medium status: accepted type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#9099
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?