I think it is common subject but we had a bit of different requirement where we had all Web Logic servers (dev/test/prod and osm/osb/odi/soa) connected to same Active directory and based on user's activity we wanted to provide different rights to different server.
Basic Configuration
Basic Configuration
- Create users/roles in LDAP (Administrator and Monitors). We can create more groups (e.g. AdminChannelUsers,AppTesters,CrossDomainConnectors,Deployers,Operators,OracleSystemGroup) but for demo purpose, just keeping it to two.
- Configure WLS for AD authentication provider
Change the DefaultAuthenticator to Sufficient
Change Custom AD Authenticator to Sufficient
Please provide AD information for connection, user and group tree path. I used Softerra LDAP client to verify the values for connection user tree path and groups/roles tree path.
LDAP Connection
User base
Group base
- Problem with this approach: if user had Administrator rights, he would be Administrator in all weblogic servers
Advanced Configuration
This configuration is to make sure if all weblogic servers are configured with same AD/LDAP server, user gets different access to different server based on role and membership defined in LDAP.
- We created fmw_prod_Administrators, fmw_prod_Monitors, fmw_dev_Administrators and fmw_dev_Monitors
- Created users and membership in LDAP
- masteradmin with fmw_prod_Administrators and fmw_dev_Administrators roles
- auditor with fmw_prod_Monitors and fmw_dev_Monitors
- developer with fmw_dev_Administrators
- Configure Role Mapping in WLS production
- Similar way WLS development can be configured with fmw_dev_Administrators and fmw_dev_Monitors
- This way masteradmin will have admin rights on both server, but developer user will have admin rights only on dev server