Managing OAM Identity Assertion on IBM WebSphere 7-15
6.
On the same page, under Additional Properties, click Advanced Lightweight Directory Access Protocol LDAP user registry settings and fill in fields under the
General Properties:
User filter: uid=vobjectclass=inetOrgPerson Group filter: cn=vobjectclass=ldapsubentry
User ID Map: uid Group ID Map: cn
Group Member ID Map: nsRole:nsRole
7.
Click Apply and OK and save this configuration.
8.
On the same page, under Related Items, click Trusted authentication realms - inbound and confirm that the LDAP entry host:port is trusted.
9.
Click Test connection to verify the connection configuration.
10.
Restart IBM WebSphere. If Standalone LDAP Registry is not selected as Current realm then under User
account repository in Available realm definitions, select Standalone Ldap Registry and click Set As Current.
11.
From now onward, log in to the IBM WebSphere console using OAM LDAP directory login credentials as registered with IBM WebSphere.
7.9.2 Adding and Configuring a Virtual Host in IBM WebSphere
You must bind your Web applications to virtual hosts logical name for configuring Web applications to a particular host name. When you request a resource, IBM
WebSphere maps the request to an alias of a defined virtual host.
To add and configure a virtual host in IBM WebSphere for the enterprise application
1.
Login to your IBM WebSphere console. For example: http:host:portibmconsole
2.
Go to Environment, Virtual Hosts, and click New
3.
Enter the General Properties for your environment, as follows:
a.
Add name: IHS host name and click on Ok and then save the changes.
b.
Click the recently created entry IHS host name:
4.
Under Additional Properties, click Host Aliases, and then click New.
5.
Fill in details for General Properties for your environment, as follows:
a.
Host: Host name where IHS server resides
b.
Port: IHS port
6.
Click OK to save the changes and continue with the next steps to configure the virtual host in your deployed enterprise application.
7.
Go to Applications, WebSphere Enterprise Applications, and:
a.
Click enterprise application.
b.
Under Web Module Properties, click Virtual Hosts.
c.
Select all the Web modules and apply the virtual host that you added.
d.
Click OK, then save the changes.
7-16 Oracle Fusion Middleware Third-Party Application Server Guide
8.
Restart IBM WebSphere where the enterprise application is deployed.
9.
Proceed to Configuring IHS Reverse Proxy in the IBM WebSphere Console
.
7.9.3 Configuring IHS Reverse Proxy in the IBM WebSphere Console
This section describes how to configures the IHS server in reverse proxy mode within the IBM WebSphere console.
To configure IHS in reverse proxy mode within IBM WebSphere 1.
Login to your IBM WebSphere console. For example: http:host:portibmconsole
2.
Go to Server Types, Web Servers.
3.
Click New, and provide IHS Web server details.
4.
Save changes to see a server entry for IHS.
5.
Select the ServerName and click Generate Plug-in.
6.
Select the ServerName and click Propagate Plug-in:
7.
Configure the IHS Web server to act as a reverse proxy for IBM WebSphere, as follows:
a.
Locate plugin-cfg.xml in IHS_install_dirPluginsconfigServerName
b.
Remove the following entry: Uri AffinityCookie=JSESSIONID AffinityURLIdentifier=jsessionid
Name=
8.
Restart the IHS Web server.
9.
Proceed to Creating the Interceptor Entry in the IBM WebSphere Console
