On a same databse, we have 2 AD_Client_ID.
We authenticate ourselves using LDAP.
I've found that if 2 distinct users of 2 distinct AD_Client got the same LDAP user, it is always the same AD_User_ID which is put in the context.
Thus you can login into a society using a AD_User of another one !!!
It seems that Login set first the user and only after the society !
(tested in Swing and webUI, not in mobile, but i think it should apply also)
What would be the best to do ?
- Stop using LDAP for one of the two ?
- Modifying login in order to verify that the AD_User_ID you are using is related to the AD_Client_ID ?
- In that particular case, add a listBox to select the correct AD_User_ID on the Default tab ?