Thursday, September 29, 2016

implementing Sql Authenticator to secure Weblogic , ADF and BPM workspace in 12. 2.1

Sql Authenticator is a weblogic provider that used to enable users stored in databases to login to weblogic console , EM. in addition to use it to authenticate users in ADF stand-alone applications and BPM workspace (using workaround was valid in 11g) .

in 2008, Edwin Biemond wrote very nice article that explain how to implement SQL Authenticator , you can find here here . before few days i have applied this steps in 12.2.1 environments with minor modification . so please pay attention for the Tips below before you go to original article .

  • in  12c Groups names for Sql authenticator should be typical to that already defined in default authenticators . groups such as "administrators", "AdminChannelUsers" ...etc , should be added to the table "JHS_ROLES" and keep in mind that column "Short_Name" is sized with only 10 which not enough for Default authenticator groups , for that please consider to change it to 100
  • Standalone ADF application which deployed on weblogic can be authenticated using Database users without any extra efforts
  • the bad news is about using those users to login BPM workspace by implementing the workaround that specified here and here . this solution was valid in 11g but it's not supported any more based on oracle response to my SR which opened regarding this matter before couples of days  ! 
the error that you will receive as below :

The configured Identity Store provider "oracle.security.jps.internal.idstore.generic.GenericIdentityStoreProvider" is not supported by IDM IdentityDirectory     

to login to BPM workspace using users stored in database you have to use OVD                                                                                                        

4 comments:

  1. I am implementing the exact same scenario,

    I have configured a SQL Authenticator and want to use that to login the BPM workspace.

    I have also tried the approach by Edwin Biemond and getting the exact same error that mentioned in you blog.

    currently I am able to login to Console and EM using the users from SQL Provider.

    can you please tell me how to use OVD and use the SQL Provider to login to the BPM workspace.

    Thanks

    ReplyDelete
    Replies
    1. hi Punit ,

      sorry for delay .

      in our case we implemented OID but to implement OVD i suggest follow this oracle document
      https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=56252821257739&parent=SrDetailText&sourceId=3-13388600901&id=1144368.1&_afrWindowMode=0&_adf.ctrl-state=14s4pk2rib_234

      thanks

      Delete
  2. Hi

    We are working in a similiar problem.

    Do you have some information about OVD to implement a custom provider to login to the BPM workspace.

    Thanks,

    ReplyDelete
    Replies
    1. hi Nuria ,

      in our case we implemented OID but to implement OVD i suggest follow this oracle document
      https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=56252821257739&parent=SrDetailText&sourceId=3-13388600901&id=1144368.1&_afrWindowMode=0&_adf.ctrl-state=14s4pk2rib_234

      Delete