-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Environment:OS:
node.js / npm versions:
Additional info:
As recently reported in HELP-59583 and similar to HELP-55546 it is possible for OIDC login flow to fail if system CA certs are different from the ones packaged with the application. When connecting to mongodb server through mongosh or Compass we allow to use system CA when the tlsUseSystemCA option is enabled, but this option (or any other) is not applied to the oidc-plugin instance that is used for Atlas login.
To allow users who are running into this issue to use Atlas Gen AI feature, and any other features that will require them to use Atlas login in the future, we should somehow allow to use system CA for the oidc-plugin login in Atlas service.
We should also check whether or not we need to also apply this to the requests in the renderer process somehow or is Electron / Chromium network stack already hadles this for us (the network stack used by Electron is different from the Node.js one that oidc-plugin uses)