I have a customer that rolled out AAF for enterprise users with SMS and TOTP as their authentication mechanisms.
On roll out they noticed that helpdesk started receiving a large volume of calls which were related to the wording on the AAF interface (/account). For instance, during authentication with a chain (LDAP Password + SMS OTP) the user is presented with a screen asking for the SMS OTP but the filed name on the form says "Password". This causes the confusion. It is not the first customer to highlight that.
The client has sent me the following email
"In logging on the screenshot below asks you to enter a password. For clarity purposes, can you please change this to 'OTP Password' to resolve the confusion caused."
Having the ability to rename the HTML display of these fields (similar to the way "Password" can be renamed to "PIN" or having an open text filed that Admin can input the name of the field) would facilitate this. The display name could be variable but not affecting the actual technical value name of the field that is used internally by AAF.
by: Bruno U. | over a year ago | Configuration
Comments
It will be supported with custom localization from 6.0
Bruno - Please confirm that the v6.0 customization feature satisfies the client.
Troy
Please respond if this is resolved with customization capabilities in 6.0
In the CP in Windows the Rename function doesn't work. I hope the new Client will fix this with the New AAF Version 6.2.
Dennis, some identifiers are different for Servers and Clients, so it's required to get the zip with resources from a Client and manually merge it with the resource file from Server. Then upload it back to the server and do the required customizations.
The merged resource file will be accessible in 6.2.