Token Timeout:  If the 30 second timeout passes before you have entered your code, please close the RDP session and launch Dolphin again.

If you have a second or third token registered, you will be given the opportunity to use these next.

Cannot enter token or passcode: Make sure you have clicked 'Show details' as per the screenshot below. This should happen automatically when input is required but sometimes does not.

Also make sure you have toggled numlock if using the number pad on your keyboard

Incorrect approval code: If you enter the wrong code, you may need to close the RDP session and re-launch Dolphin

Common Error Mesaages

User invalid or not found

Most likely you are a new user and we have neglected to license you for MFA. Please contact the Support desk or your Superuser to enable your user.

No usable login method found / User has no OTP token registered / Account missing required data or MFA enrolment needed

You do not have a valid registered token. If you have not received an email to register a token then please contact your superuser.

Invalid Username or Password

First of all, confirm your username and password is correct. If it is failing after entering your token, your token may have become desynchronised.

If you are using the OpenOTP app, you can click on your token in the app and click 'Synchronise'. You may even be prompted by the app to do so when you open it

Microsoft Authenticator etc do not offer this functionality so you will likely need to re-register a token. Please contact your superuser.

The synchronisation of tokens is a complex algorithm based on the internal clocks of the device you are using and the server you are connecting to. Tokens can easily become desynchronised slowly over time if there are differences.

Account already under transaction

If you have had a failed attempt to log in, you will need to wait for the 30 second OTP timeout to complete before attempting to log in again. To prevent OTP relay attacks, the same user cannot initiate concurrent logins.