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
Is your feature request related to a problem? Please describe.
ldap_max_search_depth is required as part of TAS 3.0, and while OpsMan will be updated to provide this with a value of 1 if this is not set, it would be nice to be able to set this value via OM so it can be included in automation.
Describe the solution you'd like
Inclusion of the ability to change ldap_max_search_depth in OM.
Describe alternatives you've considered
Operations Manager will be updated to ensure a value of 1 is added if their is no value set, but we have some use cases where being able to set this for automation purposes would be nice, especially if a value needs to be set.
Additional context
No response
The text was updated successfully, but these errors were encountered:
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.
The labels on this github issue will be updated when the story is started.
Is your feature request related to a problem? Please describe.
ldap_max_search_depth is required as part of TAS 3.0, and while OpsMan will be updated to provide this with a value of 1 if this is not set, it would be nice to be able to set this value via OM so it can be included in automation.
Describe the solution you'd like
Inclusion of the ability to change ldap_max_search_depth in OM.
Describe alternatives you've considered
Operations Manager will be updated to ensure a value of 1 is added if their is no value set, but we have some use cases where being able to set this for automation purposes would be nice, especially if a value needs to be set.
Additional context
No response
The text was updated successfully, but these errors were encountered: