-
Notifications
You must be signed in to change notification settings - Fork 22
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.
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
Qmatic plugin does not use mtls #3328
Comments
Refinement:
|
See also #3299 (comment) So I'm marking this as a wontfix since we're looking to remove Qmatic from the codebase. |
It is used but no immediate need for 2.3.0 |
Can we then please discuss when you're back what the plan is? I had the impression only LV used this and they no longer use it through OF? |
DB uses it. |
All the places that support client certificate configuration for mTLS:
Anything that uses this config to create a client must account for potential mTLS and/or other auth params |
Taken from the StUF client base implementation, ensure that one-off requests still close the session.
Put the unit tests close to the actual implementation and keep some smoke tests as regression tests to prove the original issue is indeed resolved.
* Cleaned up base URL checking a bit * Cleaned up hypothesis search strategy * Clean up context manager code style
Product versie / Product version
2.3.0-alpha.0
Omschrijf het probleem / Describe the bug
Certificate can be provided but is not sent along to the server.
Qmatic itself does not use this but when an organization uses a gateway, it can require a certificate.
Stappen om te reproduceren / Steps to reproduce
No response
Verwacht gedrag / Expected behavior
No response
Screen resolution
None
Device
None
OS
None
Browser
No response
The text was updated successfully, but these errors were encountered: