{"id":4001,"date":"2012-08-15T13:25:11","date_gmt":"2012-08-15T17:25:11","guid":{"rendered":"http:\/\/onlineappsdba.com\/?p=4001"},"modified":"2016-07-06T09:48:25","modified_gmt":"2016-07-06T13:48:25","slug":"security-modules-oes-client-in-oracle-entitlement-server-oes-11g","status":"publish","type":"post","link":"https:\/\/onlineappsdba.com\/index.php\/2012\/08\/15\/security-modules-oes-client-in-oracle-entitlement-server-oes-11g\/","title":{"rendered":"Security Modules (OES Client) in Oracle Entitlement Server (OES) 11g"},"content":{"rendered":"

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

 <\/p>\n

Oracle Entitlement Server<\/strong> (OES) is a fine-grained authorization product and part of Access Management Suite.<\/p>\n

1.<\/strong> OES consists of :
\na) OES 11g Administration Console<\/strong> : Authorization Policy Manager (APM) : This is server side components installed as part of Identity & Access Management<\/a>\u00a0software.<\/p>\n

b) OES 11g Client (SM)<\/strong> : OES Security Module is a client side component (this acts as Policy Enforcement Point and can also acts as Policy Decision point) that queries and enforces policies. OES Client (SM) is installed as separate software<\/span>.
\nOES<\/strong> – Oracle Entitlement Server
\nPDP<\/strong> – Policy Decision Point
\nPEP<\/strong> – Policy Enforcement Point
\nJRF<\/strong> – Java Required Files
\nSM<\/strong> – Security Module
\n2. Type of SM<\/strong> : Security modules can be of following type<\/p>\n

a) WebLogic SM<\/strong> (-smType wls)- WebLogic Security Module is a custom Java Security Module that includes both a Policy Decision Point and a Policy Enforcement Point. It will only run on the WebLogic Server container and does not need explicit authorization API calls. WebLogic SM can be with or without JRF (Java Required Files). JRF are installed with WebLogic Server under oracle_common when you install any Fusion Middleware product like WebCenter, SOA, IdM, IDAM etc. in a Middleware Home (MW_HOME)<\/p>\n

b) Oracle Service Bus (OSB) SM<\/strong> (-smType wls -onJRF) – similar to WebLogic Security Module but with JRF<\/p>\n

c) Java SM<\/strong> (-smType java)<\/p>\n

Note : You can also use Java Security Module in the proxy mode with Web Service Security Module or RMI Security Module<\/span><\/p>\n

d) RMI SM<\/strong> (-smType rmi)<\/p>\n

e) .Net SM<\/strong> ( -smType dotnetws)<\/p>\n

f) Web Service SM<\/strong> (-smType ws)<\/p>\n

g) Web Service SM on Oracle WebLogic Server<\/strong> (-smType ws -onWLS) :<\/p>\n

h) IBM WebSphere SM<\/strong> (-smType was) : This SM will only run on the IBM WebSphere container.<\/p>\n

i) JBoss SM<\/strong> (-smType jobs) : This SM will only run on the JBoss container.<\/p>\n

j) Apache Tomcat SM<\/strong> (-smType tomcat) : It will only run on the Apache Tomcat container.<\/p>\n

k) .NET SM<\/strong> :<\/p>\n

l) Microsoft Share Point (MOSS) SM<\/strong> :<\/p>\n

3.<\/strong> Security Module contains functionality to evaluate and enforce authorisation decisions. Security Module can act as Policy Decision Point (PDP) or both<\/strong> PDP and Policy Enforcement Point (PEP)<\/p>\n

4.<\/strong> In OES 11gR2, WebLogic Server SM<\/strong>, Oracle Service Bus SM<\/strong>, and Microsoft Sharepoint SM<\/strong> works both as PEP and PDP.<\/p>\n

More on installing and configuring OES client (Security Module) in next post<\/span><\/p>\n

 <\/p>\n