Blog de Joe Freeman

Have you ever noticed some behavior that made you think "That's different"?  I noticed this with push notifications a while back. Microsoft supports more than one Push Notification usage pattern in their Microsoft Authenticator application. Sometimes you will see more than one of them with the same account across different sites within the same organization. Push Notifications are more integrated with the authenticator application.  The server indirectly sends a message to registered Authenticator applications.  The user interacts with the Authenticator app and the app sends the response back to the server. MFA happens in the authenticator app from the human's point of view. Microsoft Authenticator also supports TOTP tokens as an alternative to Push Notifications. TOTP generates numeric sequences that can be used as part of MFA.  Numbers change on a regular cadence.  The user provides the current token value shown in the Authenticator app when a server asks for ...

You can generate Syamtec VIP compatible 2FA tokens that can be loaded into standard TOTP based Authenticator applications like  Microsoft Authenticator  , Google Authenticator  or FreeOTP. You generate new tokens  t o be registered with the protected web site.  You cannot load existing tokens  tokens because you do not have access to the token's secret seed . See references below for the original 2014 work on this. Steps These steps are documented on the Docker Hub page for this docker image. 1. Pull Docker Image     docker pull freemansoft/vipaccess 2. Generate token, example with SYMC prefix     docker run freemansoft/vipaccess provision -p -t SYMC 3. Save the token URL and Symantec ID somewhere 4. Generate a QR code to be scanned by mobile application replacing the otpauth://...  with the otpauth string from above.     docker run --entrypoint "qrencode" freemansoft/vipaccess -t ANSI256 otp...