:information_source: If you have a question, please post it on the Okta Developer Forum instead. Issues in this repository are reserved for bug reports and feature requests.
I'm submitting a
[ ] bug report
[x] feature request
Background info
Currently leveraging OnPrem MFA agent to integrate Okta with onPrem RSA.
When first time user lands on OnPrem MFA page there is an option to enter username and passcode.
Definitely Okta wanted customer flexibility to enter different username (which can be the case) for RSA infrastructure.
But, we consider this as a security risk as user can use RSA token not permitted for the user during the enrollment phase.
We are pre-populated the field with Okta username [1] but it can be updated by the user. This helps us end-user don't have to enter this value themselves (which is good from user-experience point of view).
But, we want a way to make this username field immutable and potentially hidden.
We are looking for a way to make username field immutable and hidden during enrollment process (may be new configuration or workaround)
What went wrong?
Please provide log or error messages if applicable.
Steps to reproduce
If the current behavior is a bug, please provide the steps to reproduce and a minimal demo if possible (you can use this template as a starting point: https://jsfiddle.net/m2gyLq4v/).
:information_source: If you have a question, please post it on the Okta Developer Forum instead. Issues in this repository are reserved for bug reports and feature requests.
I'm submitting a
Background info
Currently leveraging OnPrem MFA agent to integrate Okta with onPrem RSA. When first time user lands on OnPrem MFA page there is an option to enter username and passcode. Definitely Okta wanted customer flexibility to enter different username (which can be the case) for RSA infrastructure.
But, we consider this as a security risk as user can use RSA token not permitted for the user during the enrollment phase.
We are pre-populated the field with Okta username [1] but it can be updated by the user. This helps us end-user don't have to enter this value themselves (which is good from user-experience point of view).
But, we want a way to make this username field immutable and potentially hidden.
[1] https://help.okta.com/en/prod/Content/Topics/Security/MFA_OnPrem-enable-agent.htm
Expected behavior
We are looking for a way to make username field immutable and hidden during enrollment process (may be new configuration or workaround)
What went wrong?
Please provide log or error messages if applicable.
Steps to reproduce
If the current behavior is a bug, please provide the steps to reproduce and a minimal demo if possible (you can use this template as a starting point: https://jsfiddle.net/m2gyLq4v/).
Your environment