Last updated on JUNE 10, 2017
Applies to:Oracle Access Manager - Version 126.96.36.199.1 to 188.8.131.52.0 [Release 11g]
Information in this document applies to any platform.
This document will explain the method to deploy and configure OIDDAS on OAM
Note: Oracle application Server 10g had an application called OIDDAS, which was used to self-administer USERS in OID that was used by Portal, Forms, Reports, and some other products. It is was an application deployed in an OC4J container.
As Oracle Application Server 10g, which uses Oracle Single Sign-On, has been replaced with WLS and Oracle Access Manager 11g, these Legacy Applications (Specifically versions, unclear as to what versions they are) still have specific functions that can only be done by OIDDAS.
Due to this requirement the OIDDAS Application has been created specifically for OAM 11g and the use with these legacy products. The letter of the law states that this new DAS product can only be used by those legacy products ans specific versions (FMW 184.108.40.206/Portal 220.127.116.11 or with Forms/Reports 11.1.2.) and if used for any other functionality will at the customers own risk.
OAM does not certify other Oracle products specifics needs/functionality of the DAS application, that fall on that specif product team.
DAS is a dead product. No new features, nor any bug correction are available. It was meant to be used for a limited time for the Oracle legacy applications that used it, until the newer versions of the products come out with other solutions to accomplish the same tasks.
DAS requires the use of an OSSO Agent (mod_osso). The OHS 12c web servers do not have this functionality.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms