Identity and Access Management, Identity Governance

Difference between AOB and CI-based connector If you are  using Oracle Identity Governance (OIG) 12c (or earlier name Oracle Identity Manager OIM) then you may use the new AOB based connectors to integrate your applications with Oracle Identity Governance OIG or OIM. There are over 20 such connectors available ranging from Oracle E-Business Suite, to Microsoft Active Directory and O365, to SAP, GoToMeeting and Webex. Here is the download page . In OIG 12c release, the  AOB connector  have been introduced. The earlier ICF connectors (for 11g and previous versions) continue to be available and supported, and are now referred to as  CI-based connectors . So given the option of these two types of connectors with OIG which one should one choose. Well, if you are already in 12c version then use the AOB based connector. You can refer to the Table below, which provides snapshot comparison of the requirements for the two types of connectors Following are the available OIG 12c Connectors impleme

Error in SoapUI when creating a new SOAP Project When creating a new SOAP Project in SoapUI following error was given (as shown in the screenshot below) after providing the Project Name and URL of the wsdl.  It was expected to get the service on the Left hand side pane along with the operations of the SOAP Web Services. However the error was about loading of the WSDL as the above screenshot shows. So the WSDL url that was being provided was from the example below what you can see as below. So when creating a new SOAP Project in the SoapUI I was providing above URL which was as visible inside the Request screen shown in the above screenshot.  The error message was " SoapUI error loading wsdl  - org.apache.xmlbeans.XmlException error: Unexpected element: CDATA " . Stackoverflow and SoapUI blogs have several instances of this error message and none of the use case nor resolution steps worked.  Here are few examples from Stackoverflow and SoapUI blogs with similar e

Smart Card Logon Enforcement Hey everyone - it's been a while since the last post with so much going on in IT; the boom of the cloud, security breaches/incidents, new products, etc.  Wanted to take a little time to talk about something that hit my desk again recently and most folks in the DoD and other spaces wind up doing at some point,  and usually various iterations of it across multiple networks.  You may be looking to give it a go for the first time or maybe you're looking at making some changes in how you skin this cat?  There are some choices and things to be aware of when you start considering how you process enforcement of smart card logon (SCL).  First I'll start out by talking about how you can go about requiring that a smart card be used for "interactive logon," which is logon type 2.  Logon types are important when you start talking about SCL enforcement and enablement which are two distinctly different things, more on that later.  SCL enforcement