I would suggest to delete the files from here as it may contain sensitive data.
Most likely this is configuration issue which can be solved with help from support.
Thanks for the reply. What do you mean by configuration issue?
We have done AD integration several times but didn't faced this error.
Can you give some hint where we went wrong ? or have you seen this type of error before ?
Note: The AD user we have used for Integration is working fine and tested.
Is this sorted? If not, could you please log a support ticket so that BMC team can look into the environment?
If yes, could you please mention the resolution here for everyone?
Still issue is not resolved. Raised a support ticket with BMC and working with them.
Will share the resolution here once issue resolves
Quick update from my side:
If we provide any user base in catilina.properties file then we are able to login to console with AD users otherwise not. I mean integration is not working when we provide blank search in user base.
We have provided baseDN as "bna.jndiRealm.baseDN=dc=*****,dc=***"
(blank search ,Not able to login)
(Able to login to console if we provides complete userBase)
When we provide blank search in userBase ,It should search entire baseDN and should able to login to console. But not happened in our case.
But as I explained above If you provide complete userBase then It is working.
I suspect this is not a normal behavior and Seems like a bug in 20.02v. Awaiting update from support team to confirm.