Deploy to GitHub pages

Author: github-actions[bot]

Extensions/Authentication/index.html

@@ -73,7 +73,7 @@
 lnms<span class=w> </span>config:set<span class=w> </span>radius.secret<span class=w> </span>testing123
 lnms<span class=w> </span>config:set<span class=w> </span>radius.timeout<span class=w> </span><span class=m>3</span>
 lnms<span class=w> </span>config:set<span class=w> </span>radius.users_purge<span class=w> </span><span class=m>14</span>
-lnms<span class=w> </span>config:set<span class=w> </span>radius.default_roles<span class=w> </span><span class=o>[</span><span class=s2>&quot;admin&quot;</span><span class=o>]</span>
+lnms<span class=w> </span>config:set<span class=w> </span>radius.default_roles<span class=w> </span><span class=s1>&#39;[&quot;Admin&quot;]&#39;</span>
 </code></pre></div> </div> <h3 id=radius-huntgroup>Radius Huntgroup</h3> <p>Freeradius has a function called <code>Radius Huntgroup</code> which allows to send different attributes based on NAS. This may be utilized if you already use <code>Filter-ID</code> in your environment and also want to use radius with LibreNMS.</p> <h3 id=old-account-cleanup_1>Old account cleanup</h3> <p>Cleanup of old accounts is done by checking the authlog. You will need to set the number of days when old accounts will be purged AUTOMATICALLY by daily.sh.</p> <p>Please ensure that you set the <code>authlog_purge</code> value to be greater than <code>radius.users_purge</code> otherwise old users won't be removed.</p> <h2 id=http-authentication><a name=http-auth> HTTP Authentication</a></h2> <p>Config option: <code>http-auth</code></p> <p>LibreNMS will expect the user to have authenticated via your webservice already. At this stage it will need to assign a local user for that user which is done in one of two ways:</p> <ul> <li> <p>A user exists in MySQL still where the usernames match up.</p> </li> <li> <p>A global guest user (which still needs to be added into MySQL:</p> </li> </ul> <div class="admonition setting"> <p class=admonition-title>auth/http</p> <div class=highlight><pre><span></span><code>lnms<span class=w> </span>config:set<span class=w> </span>http_auth_guest<span class=w> </span>guest
 </code></pre></div> </div> <p>This will then assign the guest user to all authenticated users.</p> <h3 id=http-authentication-ad-authorization>HTTP Authentication / AD Authorization</h3> <p>Config option: <code>ad-authorization</code></p> <p>This module is a combination of <strong><em>http-auth</em></strong> and <strong><em>active_directory</em></strong></p> <p>LibreNMS will expect the user to have authenticated via your webservice already (e.g. using Kerberos Authentication in Apache) but will use Active Directory lookups to determine and assign the role(s) of a user. The roles will be calculated by using AD group membership information as the <strong><em>active_directory</em></strong> module does.</p> <p>The configuration is the same as for the <strong><em>active_directory</em></strong> module with two extra, optional options: auth_ad_binduser and auth_ad_bindpassword. These should be set to a AD user with read capabilities in your AD Domain in order to be able to perform searches. If these options are omitted, the module will attempt an anonymous bind (which then of course must be allowed by your Active Directory server(s)).</p> <p>There is also one extra option for controlling user information caching: auth_ldap_cache_ttl. This option allows to control how long user information (user_exists, userid, roles) are cached within the PHP Session. The default value is 300 seconds. To disable this caching (highly discourage) set this option to 0.</p> <div class="admonition setting"> <p class=admonition-title>auth/ad</p> <div class=highlight><pre><span></span><code>lnms<span class=w> </span>config:set<span class=w> </span>auth_ad_binduser<span class=w> </span>ad_binduser
 lnms<span class=w> </span>config:set<span class=w> </span>auth_ad_bindpassword<span class=w> </span>ad_bindpassword