Configuring Oracle Access Manager(OAM) with Window Native Authentication(WNA) for Windows Single Active Directory Domain
Prerequisites:-
A windows active directory domain is installed on a Windows 2008 server. OAM
11g R2 OAM server is installed and a target is protected with OAM deployed on a
webserver through a webgate agent.
- Login to the Active Directory server and create a user oam for WNA integration.
2. Execute ktpass command to generate a keytab file. The princ
parameter needs to be HTTP/hostnameofOAMServer@DomainName. It should map to a
user (oam)of AD.
ktpass -princ HTTP/oam.example.com@EXAMPLE.COM -mapuser oam
-pass password -out c:\oam.keytab
3. Once ktpass has been executed successfully you will see that
parameter User Logon Name has been modified.
4. On oam server at /etc/ directory krb5.conf file is present.
Modify the file for domain name and AD server name. If File is not there please
create a file with same name and provide the details as below:
5. After krb5.conf file is modified run the klist
command to check the contents of oam.keytab file. Also run kinit command to
authenticate to Kerberos server.
klist -k -t -K -e FILE:/app/u01/oam.keytab
kinit –V HTTP/oam.example.com@EXAMPLE.COM -k -t /app/u01 /oam.keytab
kinit –V HTTP/oam.example.com@EXAMPLE.COM -k -t /app/u01 /oam.keytab
6. Create new User Identity Store which points to
Active Directory(AD) server. It is not mandatory to have AD Server as a user
store you can have OVD as a user store with Adapters pointing to AD server or
you can have OID as a User Identity Store with Synchronization with AD Server.
This AD can be set as default store if needed.
7. Modify the Kerberos Module by browsing to System
Configuration --> Access Manager --> Authentication Modules -->
Kerberos Authentication Module --> Kerberos. Set required parameters as per
your environment configuration.
Parameter
Name
|
Parameter Values
|
Name
|
Kerberos
|
Key Tab file
|
/app/u01/oam.keytab
|
Principal
|
HTTP/oam.example.com@EXAMPLE.COM
|
KRB Config File
|
/etc/krb5.conf
|
8. Go to Policy
Configuration --> Application Domains --> ApplicationDomainName -->
Protected Resource Policy and change the Authentication Scheme to Kerberos Scheme. This resource is the one which is already
protected with OAM through existing deployed webgate.
9. Login to the machine which Is connected to
domain and open IE browser. Open Internet option and select Local Intranet from
security tab. Add oam server host name in the Local Intranet sites.
10. Create a test user in Active Directory and login
with that user in domain. OAM protected resource page can be accessed without
any authentication asked.
Comments
Post a Comment