Require HTTPS API server configurations to include at least one key if key-based auth is used
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	dmbaturin
	Nov 22 2023, 12:26 AM

Description

Right now it's possible to commit an HTTPS API server configuration without any API keys, even if GraphQL is not configured or its auth type is explicitly set to key. Such configurations are logically useless and should not be allowed.

Details

Difficulty level: Unknown (require assessment)
Version: -
Why the issue appeared?: Will be filled on close
Is it a breaking change?: Stricter validation
Issue type: Improvement (missing useful functionality)

Event Timeline

dmbaturin created this task.Nov 22 2023, 12:26 AM

pasik added a subscriber: pasik.Nov 22 2023, 7:05 AM

Viacheslav changed the task status from Open to Needs testing.Dec 5 2023, 10:37 AM

dmbaturin closed this task as Resolved.Fri, Apr 12, 2:17 PM

dmbaturin edited projects, added VyOS 1.4 Sagitta (1.4.0-epa2); removed VyOS 1.4 Sagitta.

Require HTTPS API server configurations to include at least one key if key-based auth is usedClosed, ResolvedPublicActions

Description

Details

Event Timeline

Require HTTPS API server configurations to include at least one key if key-based auth is used
Closed, ResolvedPublic
Actions