Tuesday, December 9, 2014

OIM DB Tables for Lookups

Query to see Lookups in OIM Database: 

select LKV_ENCODEd, LKV_DECODED,lku.lku_type_string_key from LKV, LKU WHERE  lkv.lku_key = lku.lku_key and lku_type_string_key like 'Lookup.USR_PROCESS_TRIGGERS'

Thanks !!! 

OIM Mobile Self-Service from Techdemocracy LLC

Wednesday, December 3, 2014

Issue After OAM upgrade: java.lang.NoSuchFieldError: TIVOLI


 <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'oam_server [Version=]'.
weblogic.application.ModuleException: [HTTP:101216]Servlet: "AMInitServlet" failed to preload on startup in Web application: "oam".
java.lang.NoSuchFieldError: TIVOLI


This issue is mainly caused because of missing patches. Some time patching fails during the process of upgrade so please reinstall all the required patches.

Patches for OAM Without Issue:

Patches for OAM With Issue:

Sameway check on oracle_common

Need to apply patch, refer Doc ID 1902297.1

Tuesday, December 2, 2014

OIM Export: Missing Permissions manifest attribute in main jar: detect.jar

Missing Permissions manifest attribute in main jar: http://host:Port/xlWebApp/ClientClassServlet/xlWebApp/detect.jar
Nexaweb Client 3.3.1072

Need to do following steps:

This can be bypassed by updating the security information in the Java Console. To do so:

  1. Open the Java Console (Start --> Control Panel)
  2. Click the Security tab and click on Edit Sites 
  3. Add the site name, which is in the following format:http://HOST:PORT/xlWebApp/DeploymentManager/loadDU.do

If you don't see Edit Sites List you need to update your Java Version.

Try exporting now. 


OAM WNA Logout Issue

Users won't be able to Logout using WNA Authentication:

  1. This is expected behavior.
  2. The issue is with the Browser and the basic authn.
  3. The browser stores the basicauthn credentials, so even if you log out of OAM, and it cookies are deleted/removed, when you go to authenticate again, the browser passes the basic authn credentials that were provided earlier in the browse session.
  4. The only way to stop this is to close the browser.
  5. This can be confirmed by viewing the http headers
  6. The issue is not specific to OAM or Kerberos autn, but to the basic authn and the browser.
  7. The same issue occurs if the Kerberos authentication scheme or with the Basic Scheme.

Source : Oracle

Other Posts