Enabling White List Mode in Oracle Access Manager

OAM: Enable White Listing mode

                       We are going to cover about the commands that can be used to enable White listing of URLs in OAM and enable it on OAM Protected applications. This white listing of URLs helps to avoid re-directions to external sites/URLs that are not registered with OAM.

Environment:

OAM 11.1.2.3BP07

RHEL6/OEL6

Steps:

      Enabling and configuring White-listing  mode is very simple and just requires the
     following acitivites.

Enable OAM White listing Mode

Adding/Removing URLs to/from the list of White listed URLs

1. Enable OAM White listing Mode:

Login to the server that contains installation of OAM component

Browse to the following directory

<Oracle_IDM_Home>/common/bin

Execute the following commands

./wlst.sh

connect('weblogic','password','t3://oamhost:7001'>)

domainRuntime()

oamSetWhiteListMode(oamWhiteListMode="true")

This returns the success message as shown below.

2. Adding/Removing URLs to/from the list of White listed URLs :

Execute the below command to add a URL to the list

oamWhiteListURLConfig(Name="SampleApplication",Value="http://Sample Application ,Operation="Update")  

Execute the below command to remove a URL from the list

oamWhiteListURLConfig(Name="SampleApplication",Value="http://Sample Application ,Operation="Remove")  

                            

Thanks,
Aditya

The process cannot access the flie because it is being used by another process exception from HRESULT:0*80070020

Issue:-At times you may notice that one or more Web sites are not started in IIS 7.0. If you try to manually start the Web site, it may fail with the following error message:

Internet Information Services (IIS) Manager - The process cannot access the file because it is being used by another process.
(Exception from HRESULT: 0x80070020)

Environment:-Windows 2012R2 server

Error Cause:-The error code 0x80070020 translates to ERROR_SHARING_VIOLATION (The process cannot access the file because it is being used by another process.)

This issue may occur if TCP port 80 and/or 443 is grabbed by a different service.

Solution:-First check to see what is listening on port 80.
                Open a command prompt and enter the following command:

                 netstat -ano | find ":80"

 netstat -aon | find ":443"
  
  In this case process ID 4228 was listening on port 80.
                  To check what this process is open task manager and locate that PID.
  (Note you may need to select View -> Select columns -> PID first).

 1.It turns out a developer installed Apache which was listeningon port 80 and
    causing a conflict.To resolve the conflict change one service to run on a different
    port or uninstall the unnecessary web server.
 2.In Task bar we can select httpd.exe running on  port 80 and end process

Now you can start and stop IIS website.




Thanks,
Aditya.