Labels

AAF
204
ActiveSync
2
Advanced Authentication SaaS
0
Apache Plugin
1
API
9
Authenticator Linking
6
Bitcode ios
1
Cluster Services
4
Configuration
186
Customization options
44
customize OSP login page message
6
Dashboard-Visualization
1
Dashboards-Visualization
36
Device Access
9
Display info on logon page
9
Email
6
Emergency Password Improvement
2
Endpoint ID
2
filter user reports
1
Filters
3
fingerprint
8
Flex OTP
2
Font
1
Idea
92
Installation-Deployment
34
Integrations
99
license
4
Mac
5
MacOS
7
Manage Chains at endpoint
1
Methods
39
new variable
1
Oauth2 Events Redirect URI
5
OTP
16
Outlook
2
Permissions
1
Policies
13
promoting a new GM should not require dns...
1
Readability
2
Reporting & Analysis
8
Reports
10
REST API
6
Roles and Responsibilities
3
SaaS
4
saml attribute
5
Smartphone
29
SMTP
1
SSL
6
SSO
12
Status
3
Supported Platforms
20
timeout
6
Token Lifecycle Management
1
Tokens
5
TOTP
7
UI
21
User Accounts
12
user administration
9
UX
18
Other
98
Idea ID: 2783951

Allow for customization of labels when using TOTP

Matt Weisberg  
Status: Duplicate

Typically, when you enroll a device using a TOTP authenticator app like Google's or Microsoft's, after you enroll, the account shows up with the name of the application or vendor and the login ID. But with Adv. Auth. both values just show up as "Netiq", which is meaningless. Those values need to be able to be customized.

Tags:

  •  

    Got a request from a customer to automatically identify the QR code with the user and domain.

    We really need this in the product when registering the TOTP.

  • This is becoming more of an issue as more and more applications require MFA using authenticator apps. It would help to reduce any end user confusion and likely reduce help desk calls, and therefore costs leadding to an improved service.

  • I would agree on that, that for normal users would be confusing to use MFA without proper label, especially with increasing number of apps that require MFA

  • I agree. I have made a program to test the AA api calls and made my own QR-code and it was easy to modify the labels. When you have multiple accounts for different environments it's vital to have this otherwise it gets very difficult to select the correct one. And we are advanced users, for normal users MFA is difficult and with these labels they will get lost.
  • Following up on my comment, it is not as if achieving this is at all difficult. The labels of the TOTP authenticator in question arise from the QR code generated by the appliance. The QR code is simply this formatted URL: otpauth://totp/[account_name]?secret=[secret_key]&issuer=[Website_Title] On the AA appliance the account_name and website_title are both replaced with NetIQ. On the TOTP class on NAM for instance, the account_name is fixed as the user's email address, and the website_title, the IDP's hostname. We just need AA to do similar, or better, add a configurable policy that allows overriding which user attribute for the account_name and identifiable website_title. Seems such an easy an obvious win!

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.