You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following improvements need to be done to the custom authentication management.
Addressing Naming Conflicts for User-Defined and future System-Defined Authenticators
Currently, for user-defined authenticators, it is checking for any conflict with system-defined names making authenticator name unique.
The reqirement is to have unique identifier for the amr values. However, with the implementation so far, if a custom authenticator is created with the name whatsappAuthenticator and we later introduce a system authenticator with the same name, it would result in a conflict. There improve authenticator name regex validation to check whether authenticator name start with custom- prefix with atleast three charactors.
In addtion to above validate authenticator name uniqueness across both local and federared authenticator names.
Improve display name validation to check whether it has atleast three charactors.
Version
No response
The text was updated successfully, but these errors were encountered:
Thisara-Welmilla
changed the title
Addressing Naming Conflicts for User-Defined and future System-Defined Authenticators
Improve authenticator name and display name validation for user defined authenticators
Jan 16, 2025
Description
Issue:
Following improvements need to be done to the custom authentication management.
Currently, for user-defined authenticators, it is checking for any conflict with system-defined names making authenticator name unique.
The reqirement is to have unique identifier for the amr values. However, with the implementation so far, if a custom authenticator is created with the name whatsappAuthenticator and we later introduce a system authenticator with the same name, it would result in a conflict. There improve authenticator name regex validation to check whether authenticator name start with
custom-
prefix with atleast three charactors.Version
No response
The text was updated successfully, but these errors were encountered: