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:

Parents
  •  

    It's truly shocking that this is a still a problem all the years after I've submitted it.  It's downright embarrassing if you ask me.

  •   in reply to Matt Weisberg 

    Hi Matt
    Just to clarify on the vision for this request.

    Should the label follow the default  the System name (account name) notation or do we see the need for the user to add they own input? From a user experience perspectivem, we could get users just skipping the "input name" portion and perhaps we could do a "if label is empty then use default System name (account name) notation" but if you can clarify if that would be sufficient.

    The other aspect that comes with user input is that we might need to also add input validation and checks for "unwanted" words that could add to complexity but this is just a thought.
     

  •   in reply to Bruno Ubisse 

    I think it should following the: "System Name (account name)" format.

    I have dozens of TOTP entries in my Google Authenticator and Microsoft Authenticator as well as other 3rd party auth apps and I've never once had to manually edit any of them.  Only NetIQ.

    If I look in my Google Authenticator, it's all like this:

    Google (blah@gmail.com)

    Amazon (blah@gmail.com)

    Dropbox (blah@gmail.com)

    So I think that format is well understood and should be followed.  Microsoft's is a bit different, a two line display:

    Company Name
    Account

    I have about a dozen entries in my Microsoft Authenticator.  Each one has Company Name/Account, every single one, EXCEPT one:

    Matt

  •   in reply to Matt Weisberg 

    Thank you for the clarification, Matt. Will highlight this to the team.

Comment Children
No Data

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.