OpenText NetIQ Advanced Authentication Community

OpenText NetIQ Advanced Authentication

Don't allow to user save TOTP without scan QR

Jose Pardo Carrion

In the new Enrolment Portal, when user try to enroll TOTP method he can save it without scan QR. To avoid wrong TOTP enroments could be interesting don't allow to user enroll it a provide an error/mensage like "should be scan QR code before save the…
- 1 month ago
- OpenText NetIQ Advanced Authentication
- Advanced Authentication Ideas
AA APP could be receive QR Code by any AA Version

wencheng

AA Team release a Android APP　（3.2.2 version 565）, it update all user mobile phone by auto / manual update. But this version seem could not support QR Code by old AA Server. this issue cause customer user much complain. When dev Team want to release…
- over 1 year ago
- OpenText NetIQ Advanced Authentication
- Advanced Authentication Ideas
Advanced Authentication NAM Integration: An option to remove the "cancel" button from second factor methods

Felicity Chapman

As a security concern, we would like the option to remove the "cancel" button on the second factor prompt on OAuth integrations for Fingerprint, Smartphone push, TOTP, and SMS OTP methods.
- over 2 years ago
- OpenText NetIQ Advanced Authentication
- Advanced Authentication Ideas
Enable or disable "autocomplete" on input fields via method configuration option

Wouter Rusman

Many modern browsers support autocomplete on input fields : https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/autocomplete Please make the ability to turn this option on or off available in the method configuration or show some documentation…
- over 2 years ago
- OpenText NetIQ Advanced Authentication
- Advanced Authentication Ideas
Registering TOTP method via Google Authenticator should not result in generic "Netiq(Netiq)" as profile name

Elfstone

Within the AA Enrollment Portal (even as recent as 6.3.5.2), if you scan the QR code for TOTP method using Google Authenticator (which is officially supported by AA), this results in a Google Authenticator profile named "Netiq(Netiq)" This is bad for…
- over 3 years ago
- OpenText NetIQ Advanced Authentication
- Advanced Authentication Ideas
Token Lifecycle Management

DennisR1

We would like to see a mechanism in Advanced Authentication that allows for basic Lifecycle Management features for hardware based tokens (HOTP/TOTP). Having the ability to see when a token's seed was imported into AA and when it was last used or assigned…
- over 3 years ago
- OpenText NetIQ Advanced Authentication
- Advanced Authentication Ideas
TOTP - Support enrolment without scanning QR code/Display TOTP key as text

swlshtm

At the moment when enrolling a TOTP app you must to have the ability to scan the QR code. So you need two devices, one to display the QR code and one to scan the QR code. To support enrolment when user just has a phone/tablet or desktop TOTP app (authy…
- over 4 years ago
- OpenText NetIQ Advanced Authentication
- Advanced Authentication Ideas

Menu

OpenText NetIQ Advanced Authentication

Don't allow to user save TOTP without scan QR

AA APP could be receive QR Code by any AA Version

Advanced Authentication NAM Integration: An option to remove the "cancel" button from second factor methods

Enable or disable "autocomplete" on input fields via method configuration option

Registering TOTP method via Google Authenticator should not result in generic "Netiq(Netiq)" as profile name

Token Lifecycle Management

TOTP - Support enrolment without scanning QR code/Display TOTP key as text

Resources

Menu

Popular Tags

Resources