Difference between revisions of "RADIUS"
(→Other RADIUS issues) |
(→Other RADIUS issues) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 27: | Line 27: | ||
It is not recommended to use channels that provide multiple security strings (i.e. Dual Channel, Mobile Phone Client or Swivlet/Swivlet.Net/iPhone app) with RADIUS protocols other than PAP. For details, see [[RADIUS with multiple security strings]]. | It is not recommended to use channels that provide multiple security strings (i.e. Dual Channel, Mobile Phone Client or Swivlet/Swivlet.Net/iPhone app) with RADIUS protocols other than PAP. For details, see [[RADIUS with multiple security strings]]. | ||
| − | |||
| − | |||
Latest revision as of 13:17, 10 September 2020
Overview
This page covers problems with RADIUS authentication. For further information on PINsafe and RADIUS see RADIUS How To Guide
Prerequisites
PINsafe 3.x
Errors
RADIUS authentication fails, the following log messages may be displayed:
AGENT_ERROR_BAD_OTC or Failed Validation see AGENT_ERROR_BAD_OTC
Badly formed Attribute Block, Attribute at position see Badly formed Attribute Block
Does not have a NAS entry see Does not have a NAS entry
RADIUS server failed to start, error see RADIUS server failed to start
Other RADIUS issues
RADIUS FilterID returns username and not group see RADIUS Filter ID.
It is not recommended to use channels that provide multiple security strings (i.e. Dual Channel, Mobile Phone Client or Swivlet/Swivlet.Net/iPhone app) with RADIUS protocols other than PAP. For details, see RADIUS with multiple security strings.
