-
Tenant SSO access with PKCE support
Provide support for the use of PKCE in addition to Client ID and Client Secret in SSO/OIDC configuration for XC Console access. Customers don't trust 3rd party vendors and don't want to use the Client Secret Authorization code flow but prefer the ...
Planned
-
401 errors without credentials inserted by users
The clients get many 401s because the site including static resources is protected by login but browser doesn't always send Authorization header when trying to access static resources. The origin replies with 401 and response header "www-authentic...Planned
-
injecting JA4 TLS fingerprint into every HTTP request as header
I'd like to inject the Ja4 tls fingerprint as a request header into every request sent to the origin. why: to have a relatively unique signature we can track that will be included in all the stacks upstream for correlation and to allow upstream ac...Planned
-
ACME client support on CE Nodes connecting to a Private CA.
Currently the only two methods for Certificate management are to upload certs and CAs via the console or make a script to upload the cert via an API call. It would be ideal if the CE Node could use an ACME client, to communicate with a private CA ...Planned
-
CE to support port range for HTTP and TCP LB
Currently, RE support configuration of HTTP LB to listen on port-range. This feature not supported on CE. Customer need this to advertise custom on CE for their SAP application to works.
Planned
-
Add the possibility of using a registry container with a private certificate on vk8s.
On the vk8s solution it is possible to configure Container Registries. Our container registries are internal to the company and use certificates from an internal PKI. We need the ability to use these registries, for example either adding root CA o...Planned
-
DNS primary zone search field to lookup for DNS records
When we have just few DNS records at a zone it is easy to manage. When we have few pages of records it is easier to have a search field where we can look up by the record we want to modify or check if it exists.Planned
-
Disallowed response code - upstream resp code in UI
DESCRIPTION In a log of a Disallowed response code, the upstream response code is not present in UI and present in JSON log key app_firewall_info.description. For example "description": "Disallowed response code (404)" (see attached file). SecOps ...Planned
-
Support requests that does not use SNI
We'd like to be able to communicate properly with tools that does not support SNI (here, for an example, our DNS traffic manager), so it would be great if VoltMesh was able to support these requests.Planned
-
Add "FIPS 140-2" option for HTTPS load balancer TLS security
A common requirement asked by government agencies and vendors is to be FIPS 140-2 compliant or "enforce" FIPS 140-2 compliance. From an NGINX perspective, the response was to suggest enabling FIPS mode on the OS (e.g. OpenSSL) which would disallow...
Planned