Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

IPSec-Proposal optional field is required when sending HTTP Post request via API #18271

Open
Toosaman opened this issue Dec 25, 2024 · 0 comments · May be fixed by #18272
Open

IPSec-Proposal optional field is required when sending HTTP Post request via API #18271

Toosaman opened this issue Dec 25, 2024 · 0 comments · May be fixed by #18272
Assignees
@jeremystretch
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@Toosaman
Copy link

Deployment Type

Self-hosted

Triage priority

N/A

NetBox Version

v4.1.10

Python Version

3.10

Steps to Reproduce

  1. Trying to send HTTP POST request to API endpoint:
    /api/vpn/ipsec-proposals/
{
'name': 'aes-192-gcm_3600',
'encryption_algorithm': 'aes-192-gcm',
'sa_lifetime_seconds': '3600'
}

Expected Behavior

Got HTTP status code 201, which means that the object was successfully created.

Observed Behavior

Got the error:

  allow: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS
  api_version: '4.1'
  connection: close
  content: '{"authentication_algorithm":["This field is required."]}'
  json:
    authentication_algorithm:
    - This field is required.
@Toosaman Toosaman added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Dec 25, 2024
@Toosaman Toosaman changed the title IPSec-Proposal optional field is required when sending post request via API IPSec-Proposal optional field is required when sending HTTP Post request via API Dec 25, 2024
@jeremystretch jeremystretch self-assigned this Dec 27, 2024
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation severity: low Does not significantly disrupt application functionality, or a workaround is available and removed status: needs triage This issue is awaiting triage by a maintainer labels Dec 27, 2024
jeremystretch added a commit that referenced this issue Dec 27, 2024
@jeremystretch
Fixes #18271: Require only encryption OR authentication algorithm whe…
f8ffdfe 
…n creating an IPSec proposal via REST API
@jeremystretch jeremystretch linked a pull request Dec 27, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jeremystretch jeremystretch

Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Milestone
No milestone
2 participants
@jeremystretch @Toosaman