
Something went wrong? Please open a support ticket. For example, if a user has already enrolled a key using the FIDO2 authentication mechanism and logins to Casa using such method, all their existing U2F enrollments (if any) will be migrated, this way all security keys will be listed under the one single widget in the user's dashboard. Regardless of the steps above are executed, by default Gluu Server will attempt to migrate U2F entries when users attempt to login using FIDO2 acr. Identifiers of failed entries (if any) are dumped to file rejected.txt. You can tail the file log.txt to see more details of the processing.

The script will output some feedback in the console. :WEB-INF/lib/* bsh.Interpreter script.bsh Run jar -xf /opt/gluu/jetty/casa/webapps/casa.war WEB-INF/lib.


To perform the conversion follow these steps: Every successfully migrated U2F entry acquires the state migrated and thus cannot be used for U2F authentication anymore. Only active entries not corresponding to Super Gluu enrollments are converted.
