Logging In To The IRP

This topic covers the following areas:

• Full Login Procedure
• Troubleshooting Logins

The full login procedure for the IRP is a two-step process:

1. Log in using Windows Server Authentication.
2. Log in to IRP Admin.

To log in to your IRP, proceed as follows

1. Start a web browser and enter https://Your-IRP-Website/Administration/Login.aspx in the address bar (replacing Your-IRP-Website with the real name of your IRP instance). Immediately, you are presented with the Windows Server Authentication window:
   
2. Enter the Windows Authentication User Name and Password that have been supplied to you by your IRP Agency. Please note that this will be a company-wide User Name and Password – these are not set up on a per-user basis, therefore these login details will be identical to those used by other colleagues within your company. These details will have been supplied to your Head of Ecommerce. If you are in any doubt about what these details should be, first talk to your Head of Ecommerce or, as a fall-back, ask your Deployment Manager or Account Manager. Note that if you enter incorrect details, or if you click Cancel, you will see a '401' Server Error message:
    
   


3. Click the OK button. If successful, you will see the IRP Admin login window (note that the following screen capture is just an example of the screen that you might see):
    
   
   
   Note that at this stage your browser may prompt you to save these login credentials.
4. Type in your IRP Admin Username and your Password. These will have been set up at deployment time and are based on the Admin User Group to which you belong. Please note that, unlike the Windows Authentication User Name and Password described previously, your IRP Admin Username and Password are unique to you and are not shared by anyone else within your company. If you are in any doubt about what these should be, first talk to a person in your company with Administrator privileges as they can check your Username and reset your Password if necessary. As a fall-back, ask your Deployment Manager or your Account Manager for assistance. (Your Admin User Group further determines the administration sections within IRP Admin that you can see; this is one of your IRP's many important security features – users only have permissions that are appropriate for their role.)
5. To proceed, click the Login button.

If you are unable to log in to IRP Admin, check the following:

1. Have you typed in the correct Windows Server Authentication User Name and Password?
If not, you will see a '401' Server Error message:

In this case, first talk to your Head of Ecommerce or, as a fall-back, ask your Deployment Manager or Account Manager. If you can see the IRP Admin login screen shown below then you have successfully passed Windows Server Authentication (note that the following screen capture is just an example of the screen that you might see):

2. Have you correctly entered your IRP Admin Username and Password?
If you have entered a Username and Password but the IRP Admin login window remains on the screen without logging you in and without showing an error message, then you have not entered a valid Username. Please note that a common mistake is to enter your email address instead of your Username – email addresses are not accepted for login to the IRP. If you see the message shown below then you have entered a correct Username but an incorrect Password:

In this case, first talk to a person in your company with Administrator privileges as they can check your Username and reset your Password if necessary. As a fall-back, ask your Deployment Manager or your Account Manager for assistance.

3. Is your IP Address blocked?
To check if your IP Address is blocked, take a note of your IP Address (there are many online tools that will tell you what this is) and ask someone with Administrator privileges to check that your IP Address is not restricted at the Admin User level (AdminUserEdit.aspx), the Admin User Group level (AdminUserGroupEdit.aspx) or at a global level (BlockedIPAddresses.aspx).