If the offending line is removed from the login.config file roleSearchMatching= "(&(objectCategory=group)(groupType:1.1.111.111111.1.1.111:=1111111111)(member:1.1.111.111111.1.1.1111:=\{0})(sAMAccountName=AAA AAA AAA*))" the ActiveMQArtemis CR is created successfully. Later, the secret is recreated by adding the offending line, and the Operator does not complain

Below are the command used, and the files' contents, to reproduce the issue. The files are also attached commands used $ oc create secret generic custom-jaas-config --from-file=login.config $ oc create -f artemisCR.yaml login.config activemq {    org.apache.activemq.artemis.spi.core.security.jaas.LDAPLoginModule sufficient         debug= true         initialContextFactory=com.sun.jndi.ldap.LdapCtxFactory         connectionURL= "ldap: //blabla"         connectionUsername= "bla"         connectionPassword= "bla"         connectionTimeout= "5000"         connectionProtocol= "simple"         readTimeout= "5000"         authentication= "simple"         userBase= "DC=aa,DC=aaa,DC=aaaaa,DC=aa,DC=aa"         userSearchMatching="(&(objectCategory=user)(SAMAccountName=\\{0} ))"         userSearchSubtree= true         roleBase= "DC=aa,DC=aaa,DC=aaaaa,DC=aa,DC=aa"         roleName=sAMAccountName         roleSearchMatching= "(&(objectCategory=group)(groupType:1.1.111.111111.1.1.111:=1111111111)(member:1.1.111.111111.1.1.1111:=\{0})(sAMAccountName=AAA AAA AAA*))"         roleSearchSubtree= true         referral=follow; }; artemisCR.yaml apiVersion: broker.amq.io/v1beta1 kind: ActiveMQArtemis metadata:   name: test-login-config spec:   console:     expose: true   adminUser: "user1"   adminPassword: "1234"   deploymentPlan:     image: placeholder     jolokiaAgentEnabled: false     journalType: nio     managementRBACEnabled: true     messageMigration: false     persistenceEnabled: false     requireLogin: false     size: 1     extraMounts:       secrets:       - "custom-jaas-config"