OAM11gR2: Accessing /oam on managed server to validate OAM installation will result in HTTP 403
Last updated on MARCH 08, 2017
Applies to:Oracle Access Manager - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Oracle Fusion Middleware High Availability Guide 11g Release 2 (11.1.2) suggests accessing /oam on managed server port to validate the installation of OAM but doing so results in HTTP 403 instead of the "Action Failed" message as described in the doc.
22.214.171.124 Validating OAMHOST2
Validate the implementation by connecting to the OAM server using the following URL:
The implementation is valid if the OAM login page is displayed. Note at this point it will show an "Action failed" error on the page. This is normal because you are accessing the page directly rather than as a login request.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms