I am working on Oracle products and other products simultaneously. We are working for MTN, a telecom subscriber from South Africa. We are using Oracle OUD Access Manager 12.2.1.4, which is 12c PS4. I was working on eBusiness Suite a long time ago. It was a straightforward integration where we integrated Oracle eBusiness Suite with Oracle Access Manager. In between, it was a WebGate integration that we completed for single sign-on purposes, and for eBusiness Suite, we have a different team who handles that. While registering the eBusiness Suite with Oracle Access Manager, we used Oracle Internet Directory and Oracle OUD. Previously, we were using Oracle Internet Directory. Since then, we have migrated to Oracle OUD. When we were installing the initial stage of eBusiness Suite, we installed it with Oracle Internet Directory. There is a registration process where automatically the WebGate gets installed for single sign-on purposes. Later on, when we completed the migration from Oracle Internet Directory to Oracle OUD, we performed the re-registration of the OID profiles and the WebGate profile at the eBusiness Suite end. Oracle OUD has been good overall. If you take this Oracle OUD component, many vendors are using the same Oracle OUD in different ways. For example, Ping uses the same OID component, but they call it PingDS and ForgeRock DS. Earlier, it was OpenDJ. It is quite commonly used by many customers. In Oracle OUD, as per the customer's needs, we are having different schemas for different service accounts. We have different services such as Siebel, Siebel Uli, and WCC, which are interdependent on each other. At Oracle OUD, we have different service accounts because Siebel Uli, Siebel prepaid, and WCC require a service account to connect to their systems for integration with single sign-on and authentication purposes. We have created service accounts accordingly. When a new user is getting onboarded, the user fills a form at Avasa, where they are using an identity management system. Once the user gets registered and created, if they need to access WCC, Uli, or Siebel, we restrict everything at the user and groups level. Manually, we need to take the user ID and give read, read-write, write-write, or write-read privileges at the Oracle OUD end. This is the current functionality we are using at the Oracle OUD end.
I am working on Oracle products and other products simultaneously. We are working for MTN, a telecom subscriber from South Africa. We are using Oracle OUD Access Manager 12.2.1.4, which is 12c PS4. I was working on eBusiness Suite a long time ago. It was a straightforward integration where we integrated Oracle eBusiness Suite with Oracle Access Manager. In between, it was a WebGate integration that we completed for single sign-on purposes, and for eBusiness Suite, we have a different team who handles that. While registering the eBusiness Suite with Oracle Access Manager, we used Oracle Internet Directory and Oracle OUD. Previously, we were using Oracle Internet Directory. Since then, we have migrated to Oracle OUD. When we were installing the initial stage of eBusiness Suite, we installed it with Oracle Internet Directory. There is a registration process where automatically the WebGate gets installed for single sign-on purposes. Later on, when we completed the migration from Oracle Internet Directory to Oracle OUD, we performed the re-registration of the OID profiles and the WebGate profile at the eBusiness Suite end. Oracle OUD has been good overall. If you take this Oracle OUD component, many vendors are using the same Oracle OUD in different ways. For example, Ping uses the same OID component, but they call it PingDS and ForgeRock DS. Earlier, it was OpenDJ. It is quite commonly used by many customers. In Oracle OUD, as per the customer's needs, we are having different schemas for different service accounts. We have different services such as Siebel, Siebel Uli, and WCC, which are interdependent on each other. At Oracle OUD, we have different service accounts because Siebel Uli, Siebel prepaid, and WCC require a service account to connect to their systems for integration with single sign-on and authentication purposes. We have created service accounts accordingly. When a new user is getting onboarded, the user fills a form at Avasa, where they are using an identity management system. Once the user gets registered and created, if they need to access WCC, Uli, or Siebel, we restrict everything at the user and groups level. Manually, we need to take the user ID and give read, read-write, write-write, or write-read privileges at the Oracle OUD end. This is the current functionality we are using at the Oracle OUD end.