Exploring OAM 11g

I am getting free time these days to explore on OAM 11g features more.
Few things I have started with are: Creating OAM 11g administrator users by configuring identity store. Logging and auditing stuff.

I am going to write up posts very soon on the above mentioned stuff. Next exploring topic is Custom Authentication plugins.
Stay tuned!!

Oracle Access Manager 11g is certified with Sharepoint 2010 server

One of the much awaited integrations in OAM 11g queue is Sharepoint 2010 server. Well, there is a good news and it is certified now. Check out the certification matrix.
Please contact me for integration documents.

Configure Node Manager for OAM Server 11g

Hi All,

Today I am going to explain the steps for configuring node manager for OAM Server 11g. In fact these steps can be used to configure node manager for any of the other managed servers too.

Before I get into the actual topic, let me explain you what a Node Manager is. Node Manager is a java utility tool that allows you to perform common operation tasks on Managed Servers. In a typical production environment where managed servers are distributed across geographic locations the Managed Servers can be operated from a single place called Node Manager.

Let's see how we can do this.

1. Create a machine where Managed servers are running. If there are 3 managed servers present in a cluster, then 3 machines with respective hostnames has to be created in WebLogic Admin console. Specify the machine name as you like, but should be meaningful :)
2. Specify the Type of Node Manager and machine hostname and listening port that the node manager has to communicate with.
3. Specify a Managed server to associate with this machine.
4. Execute the setDomainEnv.sh script and connect to WebLogic Admin server using WLST java command.
5. Execute nmEnroll script to enroll the node manager for a specific weblogic domain
6. Edit the nodemanager.properties file and set parameter SecureListener=false. This file is located at $MW_HOME/wlserver_10.3/common/nodemanager
7. Start the node manager using script startNodeManager.sh located at $MW_HOME/wlserver_10.3/server/bin. Wait for the message "Plain socket started listener on port 5556". You will see the port that was specified in step 2.
8. 
9. Goto WLS Admin console and check the status of Node Manager in the machine.
10. Now, its time to start managed server using node manager. Goto WLS Admin console and traverse to Environment -> Servers -> oam_server1 -> Control. Goto the end of the page and select the checkbox and click Start.
11. Wait till the status appears RUNNING.

Planning to install Oracle Identity Management 11.1.1.6?

I have written few posts here on planning the installation of Oracle Identity Management 11.1.1.6 for various scenarios. The post also covers the installation steps with detailed screenshots.

Hope this helps!

Please get back to me in case of any queries/suggestions.

Updates on OES 11g with Java SM in Tomcat Server

Earlier I had written my comments about OES 11g with java SM in Tomcat container in this post. I'd like to redefine this with some changes.

First of all, OES 11.1.1.5.0 is not supported on Tomcat Server 6.x. However if your client have no choice other than using Tomcat and there is an application to be protected against OES 11g, then here is what you can do:

Assuming that OES server and client + Java SM is installed and up and running.

• Goto Tomcat install directory, edit the setclasspath.sh or setclasspath.bat and update the Tomcat Classpath with oes-client.jar as export CLASSPATH=$CLASSPATH:$OES_CLIENT_HOME/modules/oracle.oes.sm_11.1.1/oes-client.jar.
• Specify the Java SM jps-config.xml in the Java OPTIONS (in the same file setclasspath.sh or setclasspath.bat) as export JAVA_OPTS= $JAVA_OPTS -Doracle.security.jps.config=$OES_CLIENT_HOME/oes_sm_instances//config/jps-config.xml.

Test the Tomcat application with some authorization policies and it works!

Exceptions: In my case, our enterprise application was using xml parser jars which was conflicting with xmlparserv2.jar located under $OES_CLIENT_HOME/modules/...

Experiences of Oracle Entitlement Server 11g Java SM

Since 2 months I have had the opportunity to work on Oracle Entitlement Server 11g on various requirements and would like to put my experiences here.

Java SM: The Java SM instance creation is very simple using a command line script with few input parameters. All this SM requires is the jps-config.xml present in $JAVA_SM/config location. The contents of this XML would be identity store, policy store, credentials store and so on. I am not going into details of the backend stores specified in this XML. You can use Java SM to execute java code on a stand-alone mode. There is an application Server JBOSS which is supported (atleast the steps are known to the world - detailed in fusionsecurity.blogspot.com). However if you want to use Java SM in the famous Tomcat container, then it is not supported in this current release which I think is very big lag. In general there are two types of calls you can make out to OES 11g - Authorization Calls, Policy Management calls.

In our case, we have developed an enterprise application and deployed in Tomcat container. We have to make authorization calls from the application in a dynamic manner for protecting the fine grained elements. We have tried N no. of ways to achieve this but could not make it work. However we are able to make policy management calls to OES Server just using jps-config.xml file. Policy Management calls include creating applications, resources, policies etc.,

How to change Font color and background colour in Linux Terminal

Change the Font Color of Shell Prompt in Linux:
$ export PS1="\e[0;31m[\u@\h \W]\$ \e[m "

The color can be chosen from below table values



List of Color code

Color	Code
Black	0;30
Blue	0;34
Green	0;32
Cyan	0;36
Red	0;31
Purple	0;35
Brown	0;33
Blue	0;34
Green	0;32
Cyan	0;36
Red	0;31
Purple	0;35
Brown	0;33

Replace digit 0 with 1 to get light color version.

Change the background color in Linux Terminal: