User guide

Security Administration NMS RADIUS Client Support
114
AlliedView NMS Administration Guide
Note: To make these changes, the RADIUS server may need to be restarted. Refer to the appropriate documentation.
However, once the RADIUS NMS client feature has been set up, the following scenarios could occur:
• The customer could de-activate the RADIUS NMS client through the RADIUS Configurator tool.
• The RADIUS server(s), while configured and activated, might not be available.
Refer to 4.8.4.1.
4.8.4.1 Login behavior RADIUS Server De-activated or not Available
When this occurs, the user now must log in with a locally authenticated account, which follows these rules:
• Accounts will belong to the permission groups they had when last used, regardless of whether they were authenticated
using RADIUS.
• The passwords are set to what they were the last time before RADIUS authentication. This means:
• If the account was created on the NMS prior to RADIUS authentication, the password reverts to what it was set at
on the NMS server.
• If the account was created on the RADIUS server, the id is still valid, but the default password is the same as the user
ID
Using the example accounts listed in 4.8.3 this would mean:
• The user ID Keith_K would revert to the password knk1knkZ, since that is what the pw was set to before RADIUS
authentication. However, it would belong to the groups Admin and User, since those were the associated groups defined
and last used.
• The user ID John_L would have the password John_L, since the account was created on the RADIUS server.
• The user ID Paul_M would still have a pw of plh7plhY and belong to the Admin group, since it was never created on the
RADIUS server