You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is an issue related to the mOTP configuration. It may not necessarily be a bug, but when a mandatory policy is enforced, this process must be supported correctly.
Currently, the mOTP value for RADIUS is required to be exactly 4 characters long, and the system is very strict about the character count. If the policy is changed to require 8 characters, many automation processes fail because they are still restricted to a 4-character mOTP.
For example, in our environment, the policy requires an 8-character mOTP, but since the implementation is hardcoded to 4 characters, it causes numerous issues and breaks the automation workflow.
If possible, could you please fix this issue or update the implementation so that mandatory policies requiring a different mOTP length (such as 8 characters) are properly supported?
Activity
fix(FreeRADIUSUser): increase maximum length for motp_pin to 8 #915
jaredhendrickson13 commentedon Jul 12, 2026
Thanks for reporting this issue. I'll have the maximum increased to 8 in the next patch.