OIM: Application Instance not visible in catalog

Check if the application exists in the APP_INSTANCE table:

select * from APP_INSTANCE where APP_INSTANCE_NAME like '<put application name here>';

If the application does not exists, you will have to either load or create an application first before it can be requested/viewed by catalog.

If the application instance is present, query the catalog table and check if the application is present in the catalog table:

select entity_name, ENTITY_DISPLAY_NAME, IS_DELETED, IS_REQUESTABLE from catalog where category = 'ApplicationInstance' AND entity_display_name like '<put application name here>';

If you get a result, it will mean that application is present in catalog but will not be requestable. Set 'IS_REQUESTABLE' flag to 1 and your application will be reflected in catalog.

If no result is returned by the query, it means that application is present in the application instance table but not in catalog table. To synch up the data, execute the OOTB scheduled task 'Catalog Synchronization Job' with the following parameters:

• Process Application Instances : YES
• Updated Date: Set to blank
• Mode: Full

Post the successful execution of the job, the application will be reflected in catalog.

OIM: Password Updated Task Not Triggered When Updating Password in Process Form

In OIM 11.1.2.2.0 and higher versions, when updating the Password field of process tasks, the Password Updated task is not triggered. All other <Field> Updated tasks are triggered successfully.

Starting with OIM 11g R2 PS2, account passwords need to be updated using the Reset Password operation from the Accounts sub-tab. Password modify operation in the process form will not honor account password changes. This change was done by Unpublished BUG 16518024 - CHANGE ACCOUNT PASSWORD SHOULD ALLOW CUSTOMIZATION

Use the Reset Password operation from the Accounts sub-tab.

BUG:22018915 - FORGOT PASSWORD FAILED TO UPDATE USER'S EBS UM ACCOUNT AFTER AD FIX



https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=314336318295927&parent=EXTERNAL_SEARCH&sourceId=PROBLEM&id=2218280.1&_afrWindowMode=0&_adf.ctrl-state=thbunsygn_4

WSM-02120 : Unable to connect to the policy access service.

There may be multiple reasons for this error. The wsm-pm deployment may be down, check the status of the same from weblogic deployment.

If it is up and running, the "Use JSSE SSL" flag may be enabled on the AdminServer.

1. Login in to the Weblogic Console
2. Navigate to Environment > Servers > AdminServer > SSL > Expand Advanced
3. Uncheck 'Use JSSE SSL' flag.

Exception in thread "main" java.lang.NoClassDefFoundError: oracle/sql/BfileDBAccess

Add "ojdbc6.jar" driver to the classpath of your project.

java.lang.UnsupportedOperationException: Remote JDBC disabled

java.lang.UnsupportedOperationException: Remote JDBC disabled

1. Edit the setDomainEnv.sh file located at $DOMAIN_HOME/bin i.e $MW_HOME/user project/domains/<DOMAIN_NAME>/bin.
2. Update WLS_JDBC_REMOTE_ENABLED value from false to true. i.e WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=true"
3. Restart the servers.

java.net.ProtocolException: Tunneling result unspecified - is the HTTP server at host: '' and port: '' a WebLogic Server?

java.net.ProtocolException: Tunneling result unspecified - is the HTTP server at host: '<Host Name>' and port: '<Port Number>' a WebLogic Server?

1. Login into weblogic console.
2. Go to the Environment > Servers > <Server> Protocols > HTTP and set Enable Tunneling= true,  where <Server> is the server running at the port specified in the error

OIM: Task Assignee not visible in track request

Sometimes, after you deploy your composite and raise a request which in turn invokes your custom composite, the following situation is encountered:
1. Request status shows 'Request Awaiting Approval'.
2. Task is assigned to the correct assignee and the assignee can see it in his/her inbox.
3. When anyone tracks the request, the request assignee are not visible.

This is because, the task was not correctly associated with the request.
To associate the task,
1. Open your .bpel file in jdeveloper.
2. Double click on the human task that was invoked.
3. In the 'Initiator' field in 'General' tab, give the login of the requester:
<%bpws:getVariableData('inputVariable','payload','/ns3:process/ns4:RequesterDetails/ns4:Login')%>

4. Now, navigate to 'Advanced' tab and give requestID in the 'Identification Key' field.

5. Redeploy the composite and test.

OIM: Request Type in OIM PS3

#  Request Type

1 Assign Role
2 Bulk Assign Role
3 Bulk Delete Role
4 Bulk Delete User
5 Bulk Disable Account
6 Bulk Disable User
7 Bulk Enable Account
8 Bulk Enable User
9 Bulk Modify User Profile
10 Bulk Provision ApplicationInstance
11 Bulk Provision Entitlement
12 Bulk Remove from Roles
13 Bulk Revoke Account
14 Bulk Revoke Entitlement
15 Create Role
16 Create User
17 Delete Role
18 Delete User
19 Disable Account
20 Disable User
21 Enable Account
22 Enable User
23 Hetergeneous Request
24 Modify Account
25 Modify Entitlement
26 Modify Role
27 Modify Role Grant
28 Modify User Profile
29 Provision ApplicationInstance
30 Provision Entitlement
31 Remove from Roles
32 Revoke Account
33 Revoke Entitlement
34 Self-Register User

BI Report: Apply button missing

1.  Navigate to folder containing the report layout and click on Edit button

2.  The following window will open, click on 'Parameters' button

3.  The pop up that opens will allow you to set the visibility of 'Apply' button.

OIM: Release a claimed task

Detailed Steps:

1. Login into BPM worklist URL (http://hostname:port_number/integration/worklistapp).

a. Please note that ‘port_number‘ is soa server’s port(8001).

2. In the left hand navigation tree, click on ‘Administrative Tasks’

3. Click on the ‘pencil icon’ on the top of the navigation tree to edit the inbox settings. Specifically, we are adding more column in the main window.

4. Click on  the down arrow next to the ‘magnifying glass’ icon on top of the main window and select ‘Advanced’

a. This is used to specify the search filter. This is a one-time activity, search filter can be saved as a view.

5. Specify the search condition

6. As per the search conditions, this will give you all the tasks which satisfy all the following conditions:

a. Are raised for disconnected provisioning.

b. Are acquired by a user with user login as ‘RAGNI’

c. Are in ‘assigned’ status.

7. All tasks will be displayed, satisfying the search criterion.

8. You can select the claimed task and, and from the ‘Actions’ dropdown select ‘Release’ to un-

claim

OIM: ORA-12899: value too large for column "WFMESSAGEATTRIBUTE"."STRINGVALUE" (actual: 2003, maximum: 2000)

The request fails with an error message: ORA-12899: value too large for column "WFMESSAGEATTRIBUTE"."STRINGVALUE" (actual: 2003, maximum: 2000)

The root cause is simple, OIM allows justification of 4000 characters but SOA supports justification of maximum of 2000 characters

We need to restrict justification to 2000 characters in OIM. 

Justification is a inputText field in ADF’s terms and one of the fields property is ‘Maximum Length’. 

Solution: Create a SB,  update the maximum length property to 2000 and test.

Quick Tip#3: Storing JSON data in Oracle Database

For the last couple of years, I have used JSON as my go to data format. Many a times, I had to store the JSON in the database. I used the same approach of storing it as a VARCHAR2/CLOB/BLOB and then validating the data via API. Also there was no check on what else could exist in that column(junk value or error insertion) resulting in even more validations for my data.

Now, Oracle has come up with JSON support in databases 12.1.0.2 version, which is really helpful for some one storing the json values in db.

Here is the link to the article, which explains the same in details.

https://blogs.oracle.com/jsondb/storing-json-in-the-oracle-database

Awesome work, Oracle.  

OAM: Learning the basics - Part 5 - SAML

SAML (Security Assertion Markup Language), is the leading SSO protocol and is paramount in understanding the Single Sign Sign(SSO) workings. SAML is the language by which Identity Provider and Service Provider communicates(XML based) to establish the user's identity.

*image copied from google.

Previous Post: http://iamsecurity-tips.blogspot.com/2017/07/oam-learning-basics-part-4-proxy.html

OAM: Learning the basics - Part 4 - Proxy, Forward Proxy, Reverse Proxy

Proxy: Proxy means that someone is action on behalf of someone else.

Forward Proxy: Here the proxy server is acting on behalf of the client, i.e. the content server is unaware that the request is coming from the ‘Client’.  For the ‘Content Server’, the ‘Client’ does not exist. 

Reverse Proxy: Here the proxy server is acting on behalf of the content server. i.e. the Client is unaware the response is returned from the ‘Content Server’. For the client, the ‘Content Server’ does not exist.

Next Post: http://iamsecurity-tips.blogspot.com/2017/07/oam-learning-basics-part-5-saml.html
Previous Post:  

SOA: JBO-29000: Unexpected exception caught: oracle.bpel.services.workflow.client.WorkflowServiceClientException, msg=javax.naming.NameNotFoundException: Unable to resolve 'TaskQueryService'.

Check soa-infra.war's status from admin console. Restart the same.

ORA-03115: unsupported network datatype or representation

So, I created a connection with weblogic data source and tried to execute a query and got the following error:
ORA-03115: unsupported network datatype or representation[[
 java.sql.SQLException: ORA-03115: unsupported network datatype or representation

The solution is simple,
Instead of
                  resultSet = preparedStatement.executeQuery(myQuery);
use
                   resultSet = preparedStatement.executeQuery();

OIM: unable to find LoginModule class: weblogic.security.auth.login.UsernamePasswordLoginModule, when connecting from IDE

Solution: Add wlfullclient.jar in your class path,

The steps to create wlfullclient.jar can be found at: http://iamsecurity-tips.blogspot.com/search/label/wlfullclient.jar

OIM: User unlock query

The following query can be executed to unlock an OIM user:

UPDATE USR SET USR_LOCKED=0,USR_LOGIN_ATTEMPTS_CTR=0, USR_LOCKED_ON = null,USR_MANUALLY_LOCKED = null  WHERE USR_LOGIN='<PROVIDE_USER_LOGIN>';

Quick Tip#2: Ping and telnet

ping command is used to find out whether the remote host is reachable.

Syntax:
ping [hostname/ip]
ping google.com

But you cannot ping ports, thus if you need to find out if the port is open on a remote host, you use TELNET.

Syntax:
telnet [domainname or ip] [port]

If the port is open, you will see a blank screen. This will mean that connection is successful.

Exiting from telnet: Type 'Ctrl]' , and then 'q' or 'quit'

OIM: Troubleshooting Reconcilliation

1. Each instance of the recon schedule job execution process is associated with an unique identifier – the Job ID. This job ID is created when createReconciliationEvent() method is called from the recon code.

2. All the monitoring happens on the basis of job ID. Useful tables are:

• recon_jobs
• recon_batches
• recon_events
• ra_* staging tables
• orchevents
• orchfailedevents

3. Job ID can be found in two ways:

• By searching for the recon event created by the scheduled job 
• By querying the recon_jobs table

4. Tables involved in recon process:

• RECON_JOBS
• RECON_BATCHES
• RECON_EVENTS
• RA_* TABLES

5. Helpful SQLs:

--RECON_JOBS

select count(*) from recon_jobs

select * from recon_jobs order by rj_start_time DESC

select * from recon_jobs where rj_name = 'HRMS Trusted User Recon' order by rj_start_time DESC

select distinct(rj_job_status) from recon_jobs

--RECON_BATCHES

select * from recon_batches where rj_key = '386261'

select count(*) from recon_batches where rj_key = '386261'

--RECON_EVENTS

select * from recon_events where rj_key = '386261'

select re_key, rj_key, usr_key, RE_CHANGE_TYPE, RE_STATUS, RE_LINK_SOURCE from recon_events where rj_key = '386261'

select count(*) from recon_events where rj_key = '386261'

select DISTINCT(RE_CHANGE_TYPE) from recon_events  --DELETE, CHANGELOG, REGULAR

select DISTINCT(RE_STATUS) from recon_events

select DISTINCT(RE_LINK_SOURCE) from recon_events

6. Recon Batch Size System Property: OIM.ReconBatchSize

This property is used to specify the batch size for reconciliation. You can specify 0 as the value for this to indicate that the reconciliation will not be performed in batches.

7. Drilling into a single event

Tables used: recon_events, recon_batches, orchevents, orchfailedevents

• Get event id of the event from the UI
• Run the following SQLs:

select rb_key from recon_events where re_key = '2989631'

select rb_note from recon_batches where rb_key = '12962'

select * from orchevents where processid='572404' ORDER by orchorder  -- processid=obtained from rb_note column ALSO This would give the details of the all the Event handlers invoked including their execution order and their status

select * from orchfailedevents where processid='572404'

OAM: Learning the basics - Part 3 - Understanding User Identity Store, Default Store and System Store

The following is the third post of the series, OAM: Learning the basics.

This series is intended to guide you through understanding the basic concepts of OAM. I assume, no prior knowledge and experience of OAM on your part.

Identity Stores in OAM: 

Simply put, these are the LDAP directories against which the authentication happens. 

There are three identity stores that you must be aware of:

User Identity store: A User Identity Store is a centralized LDAP repository in which an aggregation of Administrator and user-oriented data is stored and maintained in an organized way. Oracle Access Management supports multiple LDAP vendors, and multiple LDAP stores can be registered for use by Oracle Access Management and its services. 

By default the Oracle Access Manager comes with the “UserIdentityStore1”, This identity store is configured with the Embedded LDAP Server of Weblogic instance on which the OAM is running. 

However, the embedded LDAP server should only be used for testing environment. For production environment, you should use external identity stores, such as OUD, OID, AD etc.

Default store: The LDAP store designated as the Default Store is the automatic choice for use by LDAP authentication modules unless you configure use of a different store for the module or plug-in. 

Identity Federation supports multiple Identity Stores, which can be assigned on a per Identity Partner basis. Each Identity Store must be registered with Oracle Access Management. 

If no Identity Store is defined in the Identity Partner, the designated Default Store is used.

System store: Only one User Identity Store can (and must) be designated as the System Store. This is used to authenticate Administrators signing in to use the Oracle Access Management Console, remote registration tools, and custom administrative commands in WLST. 

Administrators using the Oracle Access Management Console or remote registration utility must have credentials stored in the System Store. 

Once you define a remote User Store as the System Store, you must change the OAMAdminConsoleScheme to use an LDAP Authentication Module that references the same remote user store (the System Store).

In next post, we will learn to configure these identity stores.

Keep following....

OIM: Understanding Approval Workflow Rule Evaluation

When an operation (bulk or non-bulk) is being performed, approval workflow rule evaluation takes place in the following way:

1. The approval workflow rules associated with the operation being performed are evaluated one by one, in the order in which they are configured.
2. Rule evaluation stops, and the outcome, which is workflowID or Direct, of the matched rule is returned.
3. Approval workflow rule evaluation stops at the first matching rule, which is the rule that evaluates to true, and that rule's outcome is returned as the result.
4. For a Bulk operation, if none of the rules match, then the SOA composite configured in defaultRequestApprovalComposite of SOAConfig is returned implicitly.
5. For a non-bulk operation, if none of the rules match, then the SOA composite configured in defaultOperationApprovalComposite of SOAConfig is returned implicitly.

If the approval workflow rule evaluation returns a WorkflowID, for example UserManagerApproval, then a request is created and the corresponding ASYNC orchestration is initiated. As part of the orchestration, there is a possibility that some of the data submitted by the user is modified or added. As a result, a different workflow ID than UserManagerApproval might be applicable. To handle such scenarios, approval workflow rules are re-evaluated before the workflow is initiated. If the re-evaluation results in a different workflowID, for example HRManagerApproval, then HRManagerApproval is initiated.

Source: https://docs.oracle.com/cd/E52734_01/oim/OMADM/workflowrules.htm#OMADM5385

OIM: PS3 Exporting the Approval Workflow

Deployment Manager supports moving the approval workflow rules from test to production. When you invoke the deployment manager export, select Policy and export the necessary workflow rules.

OAM: Learning the basics - Part 2 - OAM Screens

The following is the second post of the series, OAM: Learning the basics. 

This series is intended to guide you through understanding the basic concepts of OAM. I assume, no prior knowledge and experience of OAM on your part.

Login into your OAM console, refer to the first post of the series to check the OAM urls. Use weblogic username and password. The following images are from a fresh install of OAM PS3.

You should now be familiar with the screens, don't worry about what each tab/link does yet. We will discuss the same in details in future posts.

Keep following...

Next Post: http://iamsoaguru.blogspot.com/2017/05/oam-learning-basics-part-3.html
Previous Post: http://iamsoaguru.blogspot.com/2017/05/oam-learning-basics-part-1-urls.html

OAM: Learning the basics - Part 1 - Urls

The following is the first post of the series, OAM: Learning the basics. 

This series is intended to guide you through understanding the basic concepts of OAM. I assume, no prior knowledge and experience of OAM on your part.

URLs

1. Admin server url

http://<WLS_HOST>:<WLS_PORT>/console
e.g. http://iamsoaguru:7001/console

<WLS_HOST>: Host name on which the weblogic server is running
<WLS_PORT>: Port Number on which the weblogic server is running

2. OAM url

http://<OAM_HOST>:<WLS_PORT>/oamconsole
e.g.  http://iamsoaguru:7001/oamconsole

Note the port number, this is not your usual 14000 port number, this is the weblogic port as OAM is deployed as a web application on top of weblogic. 

That is all, simple right. Keep following....

Next Post: http://iamsoaguru.blogspot.com/2017/05/oam-learning-basics-part-2-oam-screens.html

OIM: PS3 - Important Links to bookmark

Admin Guide: http://docs.oracle.com/cd/E52734_01/oim/OMADM/toc.htm
Developer Guide: http://docs.oracle.com/cd/E52734_01/oim/OMDEV/toc.htm
API doc: https://docs.oracle.com/cd/E52734_01/oim/OMJAV/toc.htm

will keep adding more stuff...

OIM: Catalog's 'Risk Level' on UI to 'item_risk' data base mapping

ITEM_RISK (catalog table in database)	Risk Level on UI
1
2
3	Low Risk
4
5	Medium Risk
6
7	High Risk

OIM: FVC (Form Version Control Utility) Alternate Query

If new fields are added in the Process Form, that fields will not be available for the users who already have the account provisioned. In this case, OIM provides and OOTB utility to update the process form for such(provisioned) accounts, called Form Version Control Utility (FVC).

An alternate approach to this is executing the following query to update such accounts:

Update <process_form_UD_table> set process_form_table_version = (Select sdk_active_version from sdk where sdk_name='process_form_UD_table');

OIM: PS3 Sizing Guide

OIM PS3 sizing guide can be found at the following location:

http://www.oracle.com/technetwork/middleware/id-mgmt/oim11g-sizingguide-194346.pdf

OIM Error: java.io.InvalidClassException: oracle.iam.request.vo.BasicRequest; local class incompatible:

Error while running RequestService API

Exception in thread "main" javax.ejb.EJBException: failed to unmarshal interface oracle.iam.request.vo.Request; nested exception is: 

java.io.InvalidClassException: oracle.iam.request.vo.BasicRequest; local class incompatible: stream classdesc serialVersionUID = -5945010536412041491, local class serialVersionUID = -7263199514123717932; nested exception is: java.io.InvalidClassException: oracle.iam.request.vo.BasicRequest; local class incompatible: stream classdesc serialVersionUID = -5945010536412041491, local class serialVersionUID = -7263199514123717932

java.io.InvalidClassException: oracle.iam.request.vo.BasicRequest; local class incompatible: stream classdesc serialVersionUID = -5945010536412041491, local class serialVersionUID = -7263199514123717932

Solution:

Copy the 'oimclient.jar' and 'eclipselink.jar' from the location 'MIDDLEWARE_HOME/Oracle_IDM1/server/client/oimclient.zip' and add the same in your classpath.

OIM: Update 'xelsysadm' Password In Working OIM Environment

1. Login to Oracle Identity Manager Self Service as Oracle Identity Manager administrator and change the xelsysadm's password.
2. Also update the password in the OIMAdmin key under the oracle.wsm.security map in CSF.

If you have OIM-OAM integration environment with OVD and an LDAP in the back end, you need to change the xelsysadm password at following places.

1. Change xelsysadm password in Identity Self service console.
2. Change OIMAdmin password from EM Console under Weblogic domain -> iam domain -> security ->credentials - > oracle.wsm.security folder.
3. Change xelsysadm password in Directory side using ldap. Because change in xelsysadm password will NOT be propagated to LDAP. One need to manually update the password in LDAP directory as well.

OIM: Create OIM connection from IDE(Eclipse/Jdev)

Given that you are able to create a project a your IDE, carry out the following two exercise to connect to OIM to execute your APIs:

1. Writing the code
2. Importing the necessary jars

Code:

import java.util.Hashtable;

import javax.security.auth.login.LoginException;

import oracle.iam.platform.OIMClient;

public class OimConnection {

    private static final String OIM_URL = "t3://iamsoaguru.local.com:14000";

    private static final String AUTH_CONF = "C://Rohit//designconsole//config//authwl.conf";

    protected static final String OIMUSERNAME = "xelsysadm";

    protected static final String OIMPASSWORD = "Welcome1";

    protected OIMClient oimClient = null;

    public OIMClient BaseClient() {

        System.setProperty("APPSERVER_TYPE", "wls");

        System.setProperty("java.security.auth.login.config", AUTH_CONF);

        Hashtable<String, String> env = new Hashtable<String, String>();

        env.put(OIMClient.JAVA_NAMING_FACTORY_INITIAL,

                "weblogic.jndi.WLInitialContextFactory");

        env.put(OIMClient.JAVA_NAMING_PROVIDER_URL, OIM_URL);

        oimClient = new OIMClient(env);

        try {

            oimClient.login(OIMUSERNAME, OIMPASSWORD.toCharArray());

            System.out.println("BaseClient.BaseClient() Login SUCCESS");

        } catch (LoginException e) {

            System.out.println("Exception in getting oimConnection");

            e.printStackTrace();

        }

        return oimClient;

    }

}

Required Jars:

1. Commons-logging.jar
2. Eclipselink.jar
3. Jrf-api.jar
4. OIMClient.jar
5. Spring.jar
6. WLFullClient.jar

OIM Query: List of roles without access policy attached

SELECT
  ugp1.ugp_name AS "Role Name",
  ugp1.UGP_DISPLAY_NAME AS "Role Display Name",
  ugp1.UGP_DESCRIPTION AS "Description",
  ugp1.UGP_CREATE AS "Create Date"
FROM ugp ugp1
WHERE ugp1.ugp_name not in (select  ugp.ugp_name
from pol
left join pog on pog.pol_key=pol.pol_key
join ugp on ugp.ugp_key = pog.ugp_key)
;

OIM SOA - Callback Server URL location

1. Login into EM console.
2. Right click on SOA -> SOA_INFRA -> SOA Administration -> Common Properties
3. The callback server url will be inside Server URLs section

Callback server URL location

OIM: Connector List and Downloads

The list of all OIM connectors and the download links can be found at the following location:
http://www.oracle.com/technetwork/middleware/id-mgmt/downloads/connectors-101674.html

Oracle Identity Manager Connector	Version Number
BMC Remedy Ticket Management	9.0.4.12
BMC Remedy User Management	11.1.1.6.0
BOX	11.1.1.5.0
CA ACF2 Advanced	9.0.4.20
CA Top Secret Advanced	9.0.4.20
Concur	11.1.1.5.0
Connector Server This version is backward compatible with earlier versions of the Connector server and therefore can be used for all ICF Connectors.	11.1.2.1.0
Database Applications Table	11.1.1.6.0
Database User Management	11.1.1.8.0
Flat File	11.1.1.6.0
Fusion Applications	11.1.1.5.0
Generic SCIM	11.1.1.5.0
Generic REST	11.1.1.5.0
Generic Script	11.1.1.5.0
GoogleApps	11.1.1.7.0
Go To Meeting	11.1.1.5.0
IBM Lotus Notes/Domino	11.1.1.6.0
IBM OS/400 Advanced	11.1.1.6.0
IBM RACF Advanced	9.0.4.25
IBM RACF Standard	9.0.4.12
Identity Cloud Service	11.1.1.5.0
JDEdwards EnterpriseOne	11.1.1.6.0
Microsoft Active Directory User Management	11.1.1.6.0
Microsoft Active Directory Password Synchronization Please apply AD Password Sync connector patch 25028999 (9.1.1.5.15) after downloading from MOS (My Oracle Support).	9.1.1.5
Microsoft Exchange	11.1.1.6.0
Microsoft Windows	9.0.4.12
Novell eDirectory	9.0.4.14
Novell GroupWise	9.0.4.12
Office365	11.1.1.5.0
Oracle CRM OnDemand	11.1.1.5.0
Oracle e-Business Employee Reconciliation	11.1.1.5.0
Oracle e-Business User Management	11.1.1.5.0
Oracle Internet Directory	11.1.1.6.0
Oracle Retail Warehouse Management System	9.0.4.12
PeopleSoft Campus Solutions	11.1.1.5.0
PeopleSoft Employee Reconciliation	11.1.1.5.0
PeopleSoft User Management	11.1.1.6.0
RSA Authentication Manager	11.1.1.5.0
RSA ClearTrust	9.0.4.12
Salesforce	11.1.1.5.0
SAP Employee Reconciliation	9.1.2.6
SAP Success Factor	11.1.1.5.0
SAP User Management Engine	11.1.1.9.0
SAP User Management	11.1.1.7.0
ServiceNow	11.1.1.5.0
Siebel User Management	11.1.1.6.0
Sun Java System Directory	9.0.4.15
UNIX	11.1.1.7.0
WebEx	11.1.1.5.0
WebServices	11.1.1.5.0