Today I would like to explain to you that we have different types of cn=orcladmin user into OVD and OID products. The first one goes with 8899(Admin port) by default, as provided below. And second one goes by 3060(LDAP port). So, once you try to login into OVD administration WEB UI, you will not go to OID and check if this cn=orcladmin is there. It is a connection only related of OVD.
Let me explain it better: Let's start my example having cn=orladmin from oid and from ovd with same pwd. Then let's change ovd pwd:
First step: Go and login on /EM -->Expand Identity and Access --> Right click on OVD -->Administration --> Server properties.
Second step: You will see 2 tabs, go to 'Change SuperUser password' and type the old password and the new password.
Third step: Now you can go back to OVD adminsitration and try to login with your new password:
Fig3: You should be able to login successfully here.
Note: According to the first picture provided into this article and the explanation I provided, if you do ldapbind against 3060(OID LDAP) and 6501(OVD port) using "cn=orcladmin" on both, you should see different results as they have different passwords. So, I hope this will help you to understand these users , even if they have same name, they are different .
after the change:
ldapbind -p 3060 -D "cn=orcladmin" -q
Please enter bind password: oldpwd
bind successful
ldapbind -p 6501 -D "cn=orcladmin" -q
Please enter bind password: oldpwd
ldap_bind: Invalid credentials
ldapbind -p 6501 -D "cn=orcladmin" -q
Please enter bind password: newpwd
bind successful
Check also this:
How to change cn=orcladmin PW for OVD without EM
I hope it helps,
Thiago Leoncio.
