You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Im not being able to set the property, "authenticationEnabled" to FALSE using the client.LDAPConfigurations.Save(), every time this property is provided as FALSE, is discarted, and keeps being TRUE.
in the next example, im executing the save functionality with only the AuthenticationEnabled in False, then getting the ldap configurations with a curl call, and validating that the property is in true.
is possible to set that property in false using an api call
ive also tried to set it on TURE (original was set on false) and it works ok
# Summary: the property AuthenticationEnabled can be set on TRUE, but cannot be set on FALSE
Expected behavior
When providing the property authenticationEnabled in false using the client, should be set in false in the atlas api.
Desktop (please complete the following information):
OS: macOS Monterey 12.3
Lib Version go.mongodb.org/atlas v0.20.0
Go 1.19
The text was updated successfully, but these errors were encountered:
Describe the bug
Im not being able to set the property, "authenticationEnabled" to FALSE using the client.LDAPConfigurations.Save(), every time this property is provided as FALSE, is discarted, and keeps being TRUE.
in the next example, im executing the save functionality with only the AuthenticationEnabled in False, then getting the ldap configurations with a curl call, and validating that the property is in true.
is possible to set that property in false using an api call
ive also tried to set it on TURE (original was set on false) and it works ok
# Summary: the property AuthenticationEnabled can be set on TRUE, but cannot be set on FALSE
Expected behavior
When providing the property authenticationEnabled in false using the client, should be set in false in the atlas api.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: