Technical Tip: FortiGate RADIUS authentication not working with Microsoft NPS when using accented or UTF-8 special characters in passwords
| Description | This article describes why FortiGate RADIUS authentication may fail with Microsoft NPS as a RADIUS server. |
| Scope | FortiGate. |
| Solution | The setup is as follows:
User: test. Password: ä12345.
When trying to use accented characters as above in the password, the authentication fails.
diagnose debug console timestamp enable diagnose debug application fnbamd -1 diagnose debug enable diagnose test authserver radius Rad_server ms-chapv2 test ä12345
[1329] __fnbamd_rad_send-Sent radius req to server 'Rad_server': fd=14, IP=10.10.1.193(10.10.1.193:1812) code=1 id=17 len=181 user="test" using MS-CHAPv2
To disable the current debug:
diagnose debug disable diagnose debug reset
This is a limitation for the Microsoft NPS, where accented characters, if used in passwords, will lead to this limitation. The same occurs with symbols like the euro €.
This is explained in Network Policy Server Best Practices.
The following options are currently available for password encoding in FortiGate :
config user radius edit <radius name> set password-encoding ? auto Use original password encoding. ISO-8859-1 Use ISO-8859-1 password encoding.
Note: If using Microsoft NPS with FortiGate as a RADIUS server, it is advised not to use any accented characters or special symbols in the password. Strictly use Symbols and punctuation of ISO-8859-1.
Related articles: |
