As far as i remember, the NPS extension doesn't support changing passwords as part of the sign-in workflow. Therefore, if the pasword of the user has expired, the user cannot change it...
r
Robert Magasi
04/29/2025, 8:32 AM
I think it was with NPS, that not all characters are allowed in the passwords. IF user has some special character in the pw like "รค" then the authentication fails.
From my notes: Extended ASCII characters not allowed
Characters allowed:
A โ Z
a - z
0 โ 9
@ # $ % ^ & * - _ ! + = [ ] { } | \ : ' , . ? / ` ~ " ( ) ;
m
Marco Zimmermann
04/29/2025, 9:09 AM
also you cannot use number matching etc.
n
nsvegman
04/29/2025, 10:37 AM
It's serviceable, but there's definitely better options out there(for a much higher price). Debugging it is tough, and as Robert and TS says, it's.. well, perhaps not ideal. ๐
j
Julian Jakob
04/29/2025, 2:29 PM
From my experience, it's also "normal" that some RADIUS requests fail or doesn't respond. NetScaler always sends the request, but sometimes there's a timeout, so NPS isn't correctly forwarding it to MS / Azure. So the User has to try again... Feels like a non-enterprise ready solution tbh.