![Sample LibreNMS Application 1 6ee2f4c4 librenms](https://www.agilicus.com/www/6ee2f4c4-librenms.png)
Sample Setup
LibreNMS Application
LibreNMS is “a fully featured network monitoring system“. In order to make it externally accessible, we will treat it as a Web Application.
Overview
LibreNMS is “a fully featured network monitoring system“. In order to make it externally accessible, we will treat it as a Web Application.
Application Setup
The LibreNMS application is setup using defaults with 1 exception: we must HTTP Rewrite the Media Type text/html.
In this sample, we show setting it up so that all users in the organisation have equivalent access.
First, create a new web application. Select a ‘name’ (which will become part of the URL, e.g. https://NAME.DOMAIN), a description and a category. The latter two are for information purposes only.
![Sample LibreNMS Application 2 1b762942 image](https://www.agilicus.com/www/1b762942-image.png)
Now we can select a hostname. By default it will be NAME.DOMAIN, but, if you have an alternate hostname setup as a CNAME, you may use it here.
![Sample LibreNMS Application 3 5e0e1cab image](https://www.agilicus.com/www/5e0e1cab-image.png)
You may use an onsite connector you have previously setup, or a VPN you have previously setup.
![Sample LibreNMS Application 4 c2d241b3 image](https://www.agilicus.com/www/c2d241b3-image.png)
This choice controls the fidelity of the access & audit logs, as well as the depth of the WAF. The first choice gives full audit records on each access transation, and protects against SQL injection, CSRF and XSS attacks. The second option keeps the custodial control of the TLS private key entirely within your site and private. Both will work for this example.
![Sample LibreNMS Application 5 9e95b5b8 image](https://www.agilicus.com/www/9e95b5b8-image.png)
Now we select the coordinates of the LibreNMS server *as it is on your current site*. This might be a hostname or IP, it is how you currently use LibreNMS.
![Sample LibreNMS Application 6 8b9af8df image](https://www.agilicus.com/www/8b9af8df-image.png)
We now select authenticate by the reverse proxy.
![Sample LibreNMS Application 7 31a13c84 image](https://www.agilicus.com/www/31a13c84-image.png)
Here we can control the initial default access. You can change this later in the ‘Access’ tab.
![Sample LibreNMS Application 8 a453ad0f image](https://www.agilicus.com/www/a453ad0f-image.png)
We are now complete on the initial setup, and then have 1 more non-default step to perform, to do the Media rewrite.
![Sample LibreNMS Application 9 cbff917c image](https://www.agilicus.com/www/cbff917c-image.png)
Now that this is done, we have one last step. The LibreNMS web application writes the local IP:PORT into the HTML and we must rewrite it. To do so, on the ‘define’ screen, select ‘librenms’ from the top, and, under the HTTP Rewrites section, add ‘text/html’ to the media to be re-written. At this stage, we should be able to login and use normally.
In addition, you should set ‘application/json’ to the rewrite, in order to be corrected on return to API-driven components.
You may consider setting the ‘Include user context headers’ which will cause the authenticated user information to be available as a trusted header.
![Sample LibreNMS Application 10 851fc2ff image](https://www.agilicus.com/www/851fc2ff-image.png)