IBM websphere 6.1 integration with OAM

Question

Hi,
1) Is the "interceptorClassName" Clases Name important? can i name it as other thing rather than what is stated in the documentation?
example:
According to the WAS integtraion guide the Interceptor classname is as: com.oblix.tai.was5.WebGate2TrustAssociationInterceptor
Can i change it to com.oblix.tai.was5.WebGateTrustAssociationInterceptor
2) Is there anywhere to verify that TAI is loaded properly and how do i test it?
================================================================================
Interceptor classname is under WAS, Secure administration -> applications, and infrastructure -> Trust association -> Interceptors
Thanks and Regards,
Grey

Answer 1

Thanks! i got the figure out. but i encouter something else while integrating with WAS
im trying to integrate OAM with WAS without reverse proxy and i followed the documentation religiously. in the documentation
Defining an Oracle Access Manager Policy Domain for WebSphere without Reverse Proxy_
Without reverse proxy, disabling SSO in WAS is required. I will need to protect the WebSphere Administrative Console SSL URL. Otherwise, I will not be able to access the console after disabling SSO in WAS. I have create the policy domain as the documentation.
■ Resource Type: http
■ Host Identifier: xxx
■ URL Prefix: _/ibm/console; and /admin_
■ Description: Used by NetPointWASRegistry TAI component.
Authorization Rules: Click the Authorization Rules tab, click Add, and then create and save an authorization rule to allow access to WebSphere Administrative
Console resources. For example:
a. Click General, then enter and save:
* Name: Allow Administrator.
* Description: Allow access to WebSphere Administrative Console resources.
* Enabled: Yes
* Allow takes Precedence: Yes
Without Reverse Proxy: Click Actions, then enter and save the following WebSphere Administrative Console SSL URL for Authentication Success. For example:
Redirect to: https://hostname:port/ibm/console *<- i found out that once I had this implemented. I will be going in an authentication cycle (keep getting authenticated and redirected back to the same page) because it is part of the resources I had it declare previously to be protected.*
Is there a work around or is it due to documentation error?