For this kind of issue, we have a process that will correct and allow you to make a more thorough and detailed verification, being able to deliver to your client the data that the platform is receiving from its system.
This process is intended to be used by people with a certain level of technical knowledge, so we recommend that you review it together with a Systems Manager.
📌 Common mistakes
The most common errors are caused by the person sending the IP or URL data by not doing it correctly or not loading the URL correctly to redirect the user. The integration failure is seen at the moment when the user is entering to read, the user is asked to enter a username and password (which should not happen).
How to check if the URL or IP address received is correct:
To do this verification we can first make an attempt from the side of the person who manages the Library or store. In case we cannot solve it with this, we must ask the client to do the same verification but within their own system.
In order to do this test, we will ask the client for test access to its internal platform from where users have to enter, including username and password if it's requested.
Using Chrome or Firefox (do not use Safari): Once we have that information we enter and navigate to the last screen from where it is redirected to the Library. Once you are there you will need to do the following:
1. Find the button or link that takes us to the Library or the specific book.
2. You need to right-click to see the options of the button or link and select where it says "inspect element"
3. The browser's command panel will open up and the row where the specific command appears that will redirect the button or link to a URL (in this case to the library or book) will be selected.
It should look like this:
4. Within that row that is selected ( in case it is not selected, right click on the button again and choose the “inspect element” again) in the part that says “href =” you have to verify if the URL ends accordingly to the extension for IP or URL (/ auth / ip or / auth / referrer). In the case that we detect that the URL is incomplete or incorrect, you must pass the correct one back to the client.
5. In case the reference is correct, you must double click at the end of the URL to allow us to edit that row and add the extension: ? Debug = true and click Enter
Ex: In this specific case it would be:
6. Now you have to go back to the page where the button or link that was right-clicked before to inspect is located, and click there again.
It should show us a chart like the following on the screen:
Here is the information of the last URL that we left from the system and the IP.
The URL shown is the one that the system is sending correctly. With this, we can already verify in the case of integration by URL. This is the URL that the library will use to find the corresponding user.
In the case of IP, the IP (s) shown should be from the physical place where you are entering (ex: a university) or from the proxy (in cases where a proxy is used and you want to enter from outside through a proxy ). In case you have presented a list of IPs, the first one should always be used starting from the top, this is the IP that the library will use to search for the corresponding user.
Tip: If the IP is shown is from our network, it means that the proxy is not working. (It can be verified by searching Google for "myip" )
Tip: in some cases, the integration by URL is very similar to URLs but it can vary by one letter, eg: HTTP instead of HTTPS . They are common errors for which the integration may not work when receiving the URL from the client.
In the case that verifying all this and the correct result is not achieved, they should ask the clients, technical team, to do the same so that they themselves can verify that the information they send is not the same as the system is reporting.
We hope we made this tutorial easy for you and if you have more questions write us at [email protected]