Description of the Problem
In multiregion enabled env, User has opened a ROSA cluster and navigated to "Access control" tab > Identity providers section.User opened LDAP IDP form and filled all mandatory field definitions.(Note : All non mandatory fields were not attended and kept as it is). User tried to save the definition and reported the inline failure.

The same steps were tried with non multiregion env and the LDAP form successfully saved without any issue.
See the recording Screen Recording 2024-11-26 at 4.07.04 PM.mov

It looks like the issue reported from backend.However the issue likely to be in UI while constructing the payload definition send to the backend.

LDAP request payload from non-multiregion env

{"type":"LDAPIdentityProvider","name":"LDAP-1","id":null,"mapping_method":"claim","ldap":{"attributes":{"id":["hrll"],"email":[],"name":[],"preferred_username":[]},"url":"hello"}} 

LDAP request payload from multiregion env

 {"type":"LDAPIdentityProvider","name":"LDAP-2","mapping_method":"claim","ldap":{"attributes":{"id":["hello"],"email":[""],"name":[""],"preferred_username":[""]},"insecure":"","url":"hello","ca":""}}

Maybe it is sending "insecure" definition as string instead of boolean i.e. true or false by default.

How reproducible:

Always

Steps to Reproduce:

1. Open OCM UI staging using https://console.dev.redhat.com/openshift/?multiregion=true 
2. Open a ready cluster.
3. Click "Access control" tab > Click "Identity providers".
4. Click "Add identity providers" > LDAP.
5. Fill all required fields from the form (i.e  LDAP url and id fields)
6. Click "Add" button.
7. See the behavior.

Actual results:

At step 7 , LDAP definition failed to save from UI due to above mentioned error.

Expected results:

At step 7 , LDAP definition should be successfully  saved from UI without any error.