Remote Desktop and Remote/Online Access Labs, and VPN are older technologies that are unable to accept the entry of hardware token codes as an MFA verification method.
This means that if your mobile device is not available you must use a hardware token ("fob") code to authenticate to these remote access services using an intermediary tool installed on your home computer. The verification code generated by your hardware token is then entered into this tool which passes your authentication to the remote service allowing you to log in.
UWSP uses the BIG-IP Edge Client to provide this secure, intermediary service.
The BIG-IP Edge Client is only needed when:
- You are signing into Remote Desktop, the Remote/Online Access Labs, or VPN,
AND,
- Your mobile device is not available and you must use a hardware token code for MFA authentication.
For easiest authentication, Information Technology strongly encourages you to install the MFA app on your mobile device and have your device with you when you work.
Install The BIG-IP Edge Client on Your Home Computer
- On the off-campus computer, download the BIG-IP Edge Client for PC or Mac.
- Open your default Downloads folder and double-click the downloaded file, UWSP_FOB_VPN_Setup.exe, to open.
- In the Setup screen click Next >.
- Click Install.
- When the install completes click Next > (only needed if the installer does not automatically move to the Completing screen).
- Click Finish.
Authenticate With MFA Using a Hardware Token ("Fob") Verification Code and the BIG-IP Edge Client
- Open the BIG-IP Edge Client:
- On Windows PC: In Windows Search type, BIG-IP, and select it from the Search list.
- On Mac:
- Click Connect.
- Sign in with your UWSP account.
When the BIG-IP Client has finished connecting you will be prompted for your second authentication method.
- Select Azure Multi-Factor Authentication.
- Select Use a different verification method.
- Select Use verification code from mobile or hardware token then enter the code that displays on your hardware token screen.
You can now log into your remote access service as you normally do. BIG-IP Client should continue to run in the background for future remote access sessions.
What if the BIG-IP Client becomes disconnected?
If the BIG-IP Client becomes disconnected you will no longer be able to authenticate to remote access services. For example, a computer restart will force the BIG-IP client to disconnect.
If you find that you have been disconnected from BIG-IP Client, reconnect by repeating the previous section, "Authenticate With MFA Using a Hardware Token...".
Contact the IT Service Desk for additional help!