UPDATED: With IAS and having users with "special characters" in their user names - back end fails as well as auto-creation on security subsystem fails.
REVISED EDIT #3:
IAS issue confirmed.
AD Authentication method does not have the problem.
However - when using the authentication order:
1. RADIUS
2. AD Authentication.
Then the AUTH will fail, because of the first RADIUS reject.
The second request through AD is "ignored" since the RADIUS/IAS has precedense in the AUTH list.
Workaround(s):
* Do not use special characters in user-names when using RADIUS/IAS Windows Server 2003.
* Or use AD Authentication method instead of RADIUS.
Test-environment:[LIST=1]
- Create the following test-users in AD:
- Username:testu
Password: Password1 - Username: tøstæ
Password: Password1
- Username:testu
- Create RADIUS authentication setup according to the KB article, "RADIS Authentication V7 - Howto":
http://portal.knowledgebase.net/display/2/kb/article.asp?aid=254953
*** Note: You must enable"Automatic user creation" in Users->Authentication->Global Settings if this is not already enabled. - Enable debugging via SSH:
killall -USR2 aua.bin - Enable AD Authentication (for an alternative test) as well.
Test procedure:
- Log on to the End-user portal with "testu".
- Verify that the user is properly created in Users->Users. It's username will be listed there.
- Log on to the End-user portal with "tøstæ".
- Logon to the portal should fail.
- No user is created under "Users->Users" management page.