Description of problem:

if not respecting the case sensitivity for cliendId in the secret the value will be reported as "missing in auth" in an error message

Version-Release number of selected component (if applicable):

rhacm 2.10

How reproducible:

customer environment

Steps to Reproduce:

1. create a clusterdeployment using for secret the form used in {1]
2. deploy

Actual results:

deployment finishes but rhacm encounters a "clientId missing in auth" error

Expected results:

deployment finishes, noerror reported

Additional info:

{1] the secret used for this clusterdeployment looked like this :

kind: Secret
apiVersion: v1
metadata:
  name: azure-service-principal
  namespace: 'acm-c-example3-str'
stringData:
  osServicePrincipal.json: |-
    {
      "clientid":"REDACTED",
      "clientSecret":"REDACTED",
      "tenantid":"REDACTED",
      "subscriptionid":"REDACTED"
    }
type: Opaque