We have installed a brand new BPM Suite server with everything in the latest PS5 (184.108.40.206.0).
We have successfully integrated User authentication with our Active Directory by creating an additional Provider in Weblogic. Such integrated authentication also works for Oracle BPM and the BPM Workspace.
However, BAM is not working properly. Users can login to BAM, but after 5 minutes their users get flagged inactive by a background thread which can only be reverted by a System Administrator.
The problem happens because we use Active Directory as the external authenticator and we do not use "cn" as the User Name attribute; instead we use sAMAccountName. We cannot change this setup though, as the AD is used in many applications across the company.
We have followed all steps from document http://www.oracle.com/technetwork/middleware/bam/technote-bam-multiplesecurityprovid-130532.pdf but the background check is still active. My understanding is that we either change the User Name attribute to "cn" or we must disable the background verification. We want to accomplish the later, but we have not been successful so far. I'm wondering if this is a bug in the latest version or if there's something else that should be set in this version.
We are experiencing the same authenication issue in Oracle BAM as described above and are also running on an installation with the latest PS5 (220.127.116.11.0). When logging in with a user from the active directory provider the user will be set to inactive. Note, we are also having the user name attribute set to "sAMAccountName", but adding the property in the jps-config.xml did not help.
If anyone managed to resolve this authenication issue we would really appreciate to know your solution.