fix: Workaround for Lucee's incorrect toBase64 behavior

Workaround for where `toBase64` returns a different value on the first call
then subsequent calls.  We call `toBase64` once in our code so the user
does not have to deal with this bug.

See https://luceeserver.atlassian.net/browse/LDEV-3964

Author: elpete

models/TOTP.cfc

@@ -34,6 +34,12 @@ component singleton accessors="true" {
         config[ "secret" ] = generateSecret( arguments.length );
         config[ "url" ] = generateUrl( arguments.email, arguments.issuer, config.secret );
         config[ "qrCode" ] = generateQRCode( config.url, arguments.width, arguments.height );
+
+        // Lucee does not generate the same base64 string on the first call of `toBase64`.
+        // We call it here once so that user-land code gets the correct value if they call `toBase64`.
+        // https://luceeserver.atlassian.net/browse/LDEV-3964
+        toBase64( config[ "qrCode" ] );
+
         return config;
     }
 

tests/specs/unit/TOTPSpec.cfc

@@ -212,6 +212,18 @@ component extends="testbox.system.BaseSpec" {
                 expect( isImage( config.qrCode ) ).toBeTrue( "An image should have been returned" );
                 expect( variables.totp.getBarcodeService().decode( config.qrCode ) ).toBe( config.url );
             } );
+
+            it( "generates the same base64 string from the QR code multiple times", function() {
+                var email = "john@example.com";
+                var issuer = "Example Company";
+                var config = variables.totp.generate( email, issuer );
+                var firstBase64 = toBase64( config.qrCode );
+                var secondBase64 = toBase64( config.qrCode );
+                expect( firstBase64 ).toBe(
+                    secondBase64,
+                    "toBase64 should return the same value every time it is called."
+                );
+            } );
         } );
     }