WebLogic integration with Active Directory

This post provides an overview of WebLogic configuration for Active Directory as Authentication provider with several key settings. It is assumed that you have already configured the security realm.
The version of WebLogic is 12c and the document being followed is the Oracle Fusion Middleware Securing WebLogic server, chapter 5 - configuring Authentication Providers.
The key settings in the Authentication Provider are
1) User DN: For providing the container or DN of the users who will be authenticating
2) Group DN: For providing the container or DN of the users who will be authenticating
3) Host: This setting is for providing the Active Directory domain controllers list. However, this will vary according to the current environment, whether it is a single domain or multi-domain.
Above 1),2),3) are from WebLogic Security realm configuration with Authentication Provider. The below 4) is for the Application that is deployed on the WebLogic server. Once user has been authenticated, the application will refer to the weblogic.xml file to grant or authorize users.
4) weblogic.xml settings - settings for security role assignment in weblogic.xml file (These settings will be used by the application after successful authentication step in WebLogic server)




For an overview of Identity Asserter function refer to this blog.
References which were helpful
https://community.oracle.com/message/15105850#15105850
https://oracle-base.com/articles/11g/oracle-weblogic-server-configure-active-directory-authentication
http://biemond.blogspot.com/2009/09/sso-with-weblogic-1031-and-saml2.html
https://community.oracle.com/message/13050040#13050040
https://community.oracle.com/message/14229880#14229880 (correct answer)
https://docs.oracle.com/cd/E24329_01/web.1211/e21049/weblogic_xml.htm#WBAPP571 (WebLogic.xml Deployment Descriptors)
https://blogs.oracle.com/ardaeralp/configure-oracle-identity-manager-adldap-authentication (WebLogic settings)

Comments

Post a Comment

Popular posts from this blog

VMware fix for Invalid manifest and ova file import failed errors

Image
Recently we got a OVA file for a virtual machine. The vendor instructions were to import the ova file in vmware Workstation, Player for Windows/Linux, Fusion for Mac, and VirtualBox as well.  The instructions were to take the available package and launch the VM with VMware workstation. The package contained  Module.mf, Module.ovf and Module-disk.vmdk and a Module.ova file. The .mf and .ovf file were 2 KB each whereas the vmdk was several gigs. The package also contained a Module.ova file which was several gigs as well. OVF           Open Virtualization Format MF             Manifest file VMDK       Virtual Machine Disk OVA           Open Virtualization Appliance The ovf file is a xml file that contains metadata for the ovf package The mf file contains the SHA1 hash codes of all files in the package The vmdk file is the disk image of the virtual machine,  VMware Workstation or VirtualBox. (vmdk format was originally developed by VMware and is an open format now). All of
Read more

SOAPUI - import certificate

Image
Note: SoapUI has two versions, one is open source and second Professional version. The open source can be download here . (confirmed link 12/19/2018). SSL Handshake issue:   There is an Issue in SoapUI version 5.3.0 (and 5.2.0 version) with SSL handshake error. It was resolved by updating below in vmoptions file ( refer here ). However, the error that shows up while trying to load wsdl is "Error loading WSDL" as below The fix is to Enable TLS 1.2 protocol for SOAP/REST calls in SoapUI, by ammending the vmoptions file to add the directive for TLS as (-Dsoapui.https.protocols=TLSv1.2). Refer here . Update: Version 5.5.0 does not have this issue. If you are on 5.3.0 better upgrade to 5.5.0 which is available now (Feb 2019). I had above issue as well as another issue reaching to https endpoint. Upgrade to 5.5.0 resolved issue. Select "Check for updates" under the Help menu and you will get option for upgrade. Select upgrade current version and accept all defaul
Read more

Centrally Managed Users (CMU) - New Feature in Oracle Database 18c

Image
Centrally Managed Users (CMU) Centrally Managed Users or CMU is a new feature introduced since Oracle DB 18c which allows simplified database user management through integration with Microsoft Active Directory (AD). Beginning with Oracle Database release 18c, version 18.1 and later supports direct integration with Microsoft Active Directory (AD) using the new centrally managed users capability. CMU allows the Oracle database to perform user authentication and authorization directly against AD. Benefits of CMU With centrally managed users, users accessing the database can be centrally managed to improve an organization's security posture. An enterprise user (a user in Microsoft Active Directory) can be exclusively mapped to a database account, or many enterprise users (in an Microsoft Active Directory group) can be mapped to a shared account in the database. Microsoft Active Directory groups can also be mapped to a database global role, which provides users with additional privilege
Read more