{"id":6257,"date":"2013-10-01T17:30:51","date_gmt":"2013-10-01T21:30:51","guid":{"rendered":"http:\/\/onlineappsdba.com\/?p=6257"},"modified":"2016-05-04T11:55:29","modified_gmt":"2016-05-04T15:55:29","slug":"discovery-mode-in-oes-11g-for-weblogicosb-security-module-oracle-security-jps-discoverymode","status":"publish","type":"post","link":"https:\/\/onlineappsdba.com\/index.php\/2013\/10\/01\/discovery-mode-in-oes-11g-for-weblogicosb-security-module-oracle-security-jps-discoverymode\/","title":{"rendered":"Discovery Mode in OES 11g for WebLogic\/OSB Security Module : oracle.security.jps.discoveryMode"},"content":{"rendered":"

Oracle Entitlement Server<\/strong> (OES) is a\u00a0fine grained Authorization<\/strong> Server from Oracle (acquired from BEA’s Aqualogic Entitlement Server<\/span>) where you define Policy<\/strong>\u00a0for an application<\/strong> that covers all application resources<\/strong> that must be protected. OES Security Module<\/strong> (OESSM) acts as Policy Enforcement Point<\/strong> (PEP) and can also act as Policy Decision Point<\/strong> (PDP)<\/p>\n

.<\/p>\n

How to identify what application resource to be protected and what policy to define<\/strong> ?<\/p>\n

Well to achieve this, you install & configure\u00a0OES Security Module<\/a>\u00a0and enable Discovery Mode <\/strong>for\u00a0this Security Module.<\/strong> Once Security Module<\/strong> is configured in Discovery Mode<\/strong> then perform action on application that reflects actual use of application . Based on actions performed by user, OES will generate policy set to files that can be imported<\/strong> to OES Server .<\/p>\n

Note<\/strong>: Discovery mode doesn’t implement policy, it just creates policy set that can be imported to OES for enforcement<\/span>.<\/p>\n

Note:<\/span><\/strong> Discovery mode doesn’t create policy set of everything and this policy set should be used as starting point to create policies required in OES to protect application.<\/span><\/p>\n

.<\/p>\n

How to enable Discovery Module for OESSM in OES 11g<\/strong><\/span><\/p>\n

1.<\/strong> Start OESSM Config tool<\/strong><\/p>\n

cd $OESCLIENT_ORACLE_HOME\/oes_sm_instances\/[OESSM_NAME]\/bin\/\u00a0<\/span>(where OESSM_NAME in my case is )<\/p>\n

.\/oessmconfig.sh \u00a0-jpsconfig [WEBLOGIC_APPS_DOMAIN]\/config\/fmwconfig\/jps-config.xml<\/span> \u00a0(jps-config.xml is from $DOMAIN_HOME\/config\/fmwconfig where application is deployed for which you wish to discovery policy set)<\/p>\n

2.<\/strong> Select tab Advanced<\/strong> and set<\/div>\n
a) Discovery Mode<\/strong> to TRUE<\/strong>
\nb) Discovered Policy Directory<\/strong> to Directory where you wish to store discovered policy files<\/div>\n
<\/div>\n

\"\"<\/a><\/p>\n

 <\/p>\n

3.<\/strong> Save the changes and it will add following property in [WEBLOGIC_APPS_DOMAIN]\/config\/fmwconfig\/jps-config.xml<\/p>\n

oracle.security.jps.discoveryMode<\/strong>
\noracle.security.jps.discoveredPolicyDir<\/strong><\/p>\n

 <\/p>\n

\"\"<\/a><\/p>\n

 <\/p>\n

Note<\/strong>: Above step will create discovered policy in file discovery-jazn-data.xml<\/strong> under directory defined by\u00a0oracle.security.jps.discoveredPolicyDir<\/strong><\/p>\n

More on discovered policy format and importing discovered policy data to OES in later posts !!<\/span><\/strong><\/p>\n

 <\/p>\n

Note<\/strong>: During Discovery Mode of OESSM, OES policies for that Security Module are not enforced<\/span>.<\/p>\n

Related\/References<\/strong><\/span><\/p>\n