When a user tries to Authenticate to a AAA Vserver with Classic Authentication Policies configured as Primary and Secondary, the user may face an issue where after providing the OTP/token code in the last factor, the Authentication process does not complete.
The user is not redirected to the intended resource/Vserver to which they are attempting to authenticate.
The same configuration works with X1 theme.
1. With RfWebUI based theme, switch to Advanced Authentication policies.
2. Use X1 based theme which can work with Classic as well as Advanced policies.
After submitting the token, the client issues a /nf/auth/doAuthentication.do even though nFactor is not in use and Classic Authentication policies are configured. In response, the user receives a 404 message and the Authentication remains incomplete.
RfWebUI based theme is not supported for an Authentication virtual server configured with Classic Authentication policies
RfWebUI based themes for AAA Vserver are designed for Advanced Authentication policies as a result the action is performed as /nf/auth/doAuthentication.do