There Was an Unexpected Error Verifying Your Barcodes. Please Try Again Later.
Overview
Students, faculty, and staff may be prompted to authenticate with a second factor (Azure MFA - a single, reliable MFA provider for all UNM) when accessing various systems. This entails verifying your identity non only with your NetID ( * email address) and password, but likewise with a phone call or text message.
* Starting Spring 2022, UNM Information technology is implementing an interim workaround solution to address business continuity needs. Nearly HSC users volition be able to sign into many UNM applications seamlessly with their HSC username and password. Put another style, HSC users can access various UNM applications in the same browser window/session as their HSC account(southward) without inbound a UNM NetID/password, performing MFA again, or using a Private/Incognito/InPrivate browser window. If seamless login fails or is not yet implemented on the application being accessed, HSC users tin still login using <NetID>@unm.edu (even without an agile UNM electronic mail address) – encounter "I am an HSC user and exercise not have a UNM electronic mail address…" beneath for additional information.
Information technology is likely your financial institution uses Multi-factor Authentication and requires more 1 type of hallmark for you to admission your business relationship data. When MFA is enabled, business relationship holders receive a notification on their mobile device. Requiring a response on a secondary device (phone, landline, tablet, etc.) helps prevent others from accessing your account, even if they take your NetID and password.
Azure MFA applies to various applications and systems, including but not express to:
- TouchNet (Bursar Account Suite)
- Loboweb Direct Deposit
- Loboweb Tax Forms (W2/W4/1095-C/electronic consent)
- Loboweb Benefits and Deductions
- Benefits Open Enrollment
- Role 365 (Lobomail/email, Teams, etc. – both web and client app versions)
- TouchNet (Bursar Account Suite)
- UNM VPN Service
- AppTree
- Other general applications (Adobe, UNM Learn, Zoom , etc.)
- Various privileged IT systems
With nearly applications, yous have the pick and are encouraged to use the "Don't' ask again for …" option on each of your trusted devices to reduce the number of times you are prompted to perform MFA. When presented with the following screen, check the box:
Notation that this setting is device and browser specific – if you use multiple devices and browsers, y'all will need to enable the "Don't' ask over again for" … pick on each.
Client applications for both mobile devices and desktop/laptop computers generally leverage "Don't' ask again for …" automatically and may non display the choice. Common examples of this are the Outlook app and Teams app for iOS/Android. Note that in some cases, you may need to authenticate separately in each app on your device(s).
Users are encouraged to pre-register their MFA device(s) here (login with Main C ampus NetID <NetID>@unm.edu and password).
If you do non pre-register a MFA device in accelerate, you volition exist prompted to annals the first time you login to a system or app requiring MFA. The enrollment process is fast and easy - y'all can see it in action at https://world wide web.youtube.com/lookout man?five=uWbkLuI4g30
Note: Devices registered for Azure MFA are separate from devices registered at netid.unm.edu (Update My Contact Information) for password resets (meet Reset Password with SMS Text Message to Mobile Number in How tin can I reset or change my NetID's Password?). Users are encouraged to register their phones in both places for the highest level of security and convenience.
Initial Enrollment
Azure MFA'due south self-enrollment procedure makes it easy to register your telephone and configure it to receive a text (SMS) message, phone telephone call, or Push button notification when you are accessing a protected application (you can also utilize a landline telephone via phone call for MFA). Azure MFA prompts you to enroll the first time you log into a secured application. Acquire more (alternative format: video)
I am an HSC user and do not have a UNM email accost – I only accept an @salud.unm.edu or @srmc.unm.edu or @unmmg.org address. Tin I still login and apply Azure MFA?
Starting Spring 2022, UNM IT is implementing an interim workaround solution to address business continuity needs. Well-nigh HSC users will exist able to sign into many UNM applications seamlessly with their HSC username and password. Put another way, HSC users tin access diverse UNM applications in the same browser window/session as their HSC account(southward) without entering a UNM NetID/password, performing MFA once again, or using a Private/Incognito/InPrivate browser window.
If seamless login fails or is not yet implemented on the application being accessed, yous tin can still login in a Individual/Incognito/InPrivate browser window and use Azure MFA (regardless of whether y'all have an active UNM email address), as long as you accept an active UNM main campus NetID. HSC users should login using their main campus Internet ID <NetID>@unm.edu, where <NetID> is the HSC user's UNM chief campus NetID.
If you are an HSC user without a UNM chief campus NetID, you must showtime request a UNM chief campus NetID at https://netid.unm.edu prior to using Azure MFA.
In brief, always append @unm.edu to your UNM master campus NetID (regardless of email account status) when authenticating.
If you are not certain if y'all take a UNM Main Campus NetID or experience other issues, delight contact the UNM IT Service Desk via Assist.UNM or by calling 505-277-5757.
What types of phone can I apply for Azure MFA and what methods are available?
Azure MFA supports any mobile device or landline phone equally follows:
- Mobile phone (phone call/sms)
- Office telephone (landline – phone call only – can also be used with abode phone)
- Mobile phone (authenticator app/push)
The Microsoft Authenticator mobile app with push notifications is the recommended choice for Azure MFA. If possible (you have a smartphone with a cellular internet plan), you are encouraged to employ this option.
How many phones should I add to Azure MFA, and how can I exercise this?
UNM Information technology recommends adding at least ii devices for Azure MFA. This way, if you lose one, yous are not locked out of UNM apps or the device direction portal.
I do not want to use the Microsoft Authenticator app. Can I use just call or text for MFA instead?
Please note, the Microsoft Authenticator mobile app with push button notifications is the recommended option for Azure MFA. If possible (you have a smartphone with a cellular internet plan), y'all are encouraged to employ this selection.
That said, Azure MFA works with any device capable of receiving a phone phone call (country lines, feature phones, etc.) so the Microsoft Authenticator app is non required to use MFA at UNM.
If yous prefer to not employ the App, ensure yous enroll 1 of the post-obit methods:
- Mobile phone (call/sms)
- Office phone (landline – call but– tin can also be used with home phone)
I practise not have a mobile device or I adopt non to utilise it for MFA. Is in that location some other choice?
Azure MFA works with landlines by supporting hallmark via telephone phone call. During enrollment, ensure you select the following option:
- Office telephone (landline – call only – tin besides be used with dwelling phone)
If you practise not take a landline phone or mobile telephone, you can also enroll an authenticator app that runs on your personal computer (or some other device, such as a tablet). A mutual case of this is WinAuth for Windows, Authenticator Extension for Chrome (Windows, macOS), or Google Authenticator (iOS, Android) . Internet connectivity is not required. To leverage this option, ensure you select the following during enrollment (counterintuitive):
- Mobile telephone (authenticator app/push)
- Mobile app -> Use verification code
Then, apply this guidance while working through the steps:
- On the "Configure mobile app" screen with a QR code, click the "Configure app without notifications" link
- If you have not already, install the Authenticator application of your choice on your computer or device (WinAuth, Authenticator Extension for Chrome, Google Authenticator, etc.)
- If your selected authenticator app supports scanning barcodes, use that choice to browse the QR code. If non, enter the secret key manually.
- Lastly, ostend that the one-time passcode displayed in your authenticator app validates in the Azure MFA window.
User's without a mobile device, landline, or a computer may have the option to complete functions that usually require MFA in person (offline).
For example, multi-factor authentication is required to admission the Bursar Account Suite (TouchNet) online, but users have the choice of mailing in payments or visiting the Bursar's function to complete other changes to their account.
Ongoing Use and Tips
In one case you lot've enrolled in Azure MFA, you will login to UNM applications with your username and password, so utilise your device to verify that it is actually you. The 2 "factors" involved are something yous know (password) and something y'all take (device).
I cannot access TouchNet and receive a "oops, this link isn't working…This link to XXXXXX is invalid. Click the link below to see what applications you accept admission to. Otherwise, contact your ambassador or the person who gave you lot this link to resolve this issue" error message. What is causing this?
This issue may also manifest as a "at that place was a problem processing your request" fault message.
This generic mistake occurs when yous are currently logged into another Microsoft account (besides your UNM account) in the browser session you are accessing TouchNet or another application. Mixing accounts and "keep me signed in" options in the same browser tin can lead to inconsistent authentication behavior.
Delight use one of the post-obit workarounds:
- Open a "individual" or "incognito" window in your browser and login to TouchNet (or the app in question) using your UNM account.
- Clear your browser data (cache and cookies), close the browser, reopen the browser, navigate back to TouchNet (or the app in question), and login with your UNM credentials when prompted (you may be prompted to setup MFA if you have non already).
- Logout of your non-UNM Microsoft account using the link in the top right – then, login again using your @unm.edu account.
- Practice NOT select "Keep me signed in" in your browser for Microsoft accounts besides your UNM account. Other Microsoft accounts include (just are non express to) Hotmail, MSN, Live, accounts from other schools/universities and fifty-fifty generic (non-personal) UNM accounts like department and lodge NetIDs.
- If you must consistently remain logged in to multiple Microsoft accounts (UNM, personal, etc.) in the same browser, you must employ "profiles" or equivalent sandboxing functionality (if you utilize Google Chrome, come across https://support.google.com/chrome/answer/2364824 – this prevents accounts from interfering with each other.
If these steps practice not work, contact the UNM IT Service Desk-bound. In that location may be a larger issue with your UNM account.
I cannot admission TouchNet and receive a "We're distressing, an error has occurred. The requested page could not exist found. Please log out and try once again later." error message. What is causing this?
This generic error usually occurs when you lot are currently logged into another UNM Microsoft account (besides your own) in the browser session you are accessing TouchNet.
The quickest fix is to open up a "individual" or "incognito" window in your browser and login to TouchNet in that window.
The longer-term ready is ensuring you do non select "Keep me signed in" in your browser for Microsoft accounts besides your UNM account. Other Microsoft accounts include (simply are not limited to) Hotmail, MSN, Live and even generic (non-personal) UNM accounts (like department and club NetIDs). Mixing accounts and "proceed me signed in" options in the same browser can pb to inconsistent authentication behavior.
What browsers work all-time when accessing web applications that require Azure MFA?
In general, users report the best experience using upwards-to-date, mainstream browsers such as Google Chrome, Mozilla Firefox, and the new Microsoft Border.
Browsers should be configured in a standard way (assuasive cookies, JavaScript, etc.) and should not automatically clear browser data on leave if single sign on (SSO) is desired (otherwise, you will need to re-authenticate each time y'all admission a UNM web application).
If you practise not have a mobile device or landline (or prefer not to use them for UNM MFA) and program to use an authenticator plugin instead (see "I do non have a mobile device or I prefer not to use it for MFA. Is in that location another selection" above), a Chromium-based browser similar Chrome or new Edge is required.
I am receiving push notifications, calls or text messages from Azure MFA, but I am not trying to log in. What should I do?
By and large, this occurs for 1 of 2 reasons:
- An application on i of your trusted devices is attempting to authenticate and requires you to complete the MFA process
- Your NetID password has been compromised and a malicious user is attempting to access your business relationship
Outset and foremost, do not panic, but practice not reply the push notification, phone call, or text until you investigate farther.
You should but receive a button notification, call, or text from Azure MFA when you or one of your devices are logging into a secured application (web or customer app).
As a first step, assemble your trusted devices (phone(s), tablet(southward), laptop, desktop, etc.) and review each to see if a trusted application on 1 of them is requesting that y'all complete the MFA process.
If yes, yous can respond to the MFA prompt and go on.
If after reviewing all your trusted devices and apps, you lot do not see any pending MFA requests, it is possible that someone is trying to break into your account.
If that occurs, contact the UNM Information technology Service Desk-bound immediately if this occurs. You should also reset your NetID password as soon every bit possible at https://netid.unm.edu .
Tin can I remember my personal device to avoid logging into Azure MFA every fourth dimension I access a secure application?
With web applications, you have the pick and are encouraged to utilise the "Don't' ask over again for …" option on each of your trusted devices to reduce the number of times you are prompted to perform MFA. When presented with the following screen, check the box:
With this option, subsequent logins from the same device and browser will not crave the MFA process. This applies even if y'all logout and login once more:
Yous can also use the "Stay signed in" option, which is not specific to MFA but your session in general (username/password and MFA).
When presented with the post-obit screen, select "Yes" if desired but practise not check the box:
Using this option, subsequent logins will be seamless, and you will not need to enter your username/password nor complete the MFA process. However, if yous logout, you must complete both password verification and MFA next time you login on that browser/device.
Annotation: If you lot do not receive the "Stay signed in" prompt when accessing a web application, clear your browser's cookies, close/reopen it, and complete the authentication procedure over again. When cookies are cleared, this behavior is reset and yous can answer "Yes" once again (leaving the box unchecked).
Only employ these options on your ain, secure devices. Never use them on a public, untrusted, or shared device.
Note that both settings are device and browser specific – if you employ multiple devices and browsers, y'all volition need to enable the "Stay signed in" or "Don't ask once again for …" option on each.
Client applications for both mobile devices and desktop/laptop computers mostly leverage "Stay signed in" or "Don't enquire once again for …" automatically and may not brandish the options. Common examples of this are the Outlook app and Teams app for iOS/Android. Note that in some cases, you may need to authenticate separately in each app on your device(southward).
How can I alter my preferred authentication method, re-enable push notifications (instance, after an iOS upgrade), or add/remove devices for MFA subsequently I already enrolled?
Y'all will exist prompted to authenticate with an existing MFA device prior to making and changes.
I am trying to login to an application using Azure MFA merely have not received a push notification, call or SMS/text. What should I exercise?
There are a variety of reasons y'all may experience this issue. Apply the following steps to address the most common issues:
- If you are using a landline telephone (also known as an "office telephone")
- Ensure it is plugged in and configured properly (ringer on, etc.).
- Ensure you lot are using a touch tone (not rotary) phone.
- Ensure a feature called "Anonymous Telephone call Rejection" (or something similar) is turned off.
- Case: CenturyLink
- Case: Xfinity
- Ensure y'all (or your carrier) are not using other settings or features to block unknown/unsolicited telephone calls.
- Ensure that DTMF (dual tone multi frequency) is working properly on your line by calling 804-222-1111, selecting pick 2, then pressing the number five on your telephone. The organization should read dorsum "v" if DTMF is working properly.
- Ensure that the pound (#) central on your telephone is not assigned to another carrier-specific functionality. # should send the standard DTMF tone directly to Azure MFA when the key is pressed.
- If yous are using a mobile phone (phone call or sms/text message)
- Ensure it is configured properly and that you lot have cellular coverage.
- Ensure that you (or your mobile carrier) are not using settings or applications to block unknown/unsolicited sms text letters or phone calls.
- If y'all are using a mobile telephone and the Microsoft Authenticator app (button)
- Ensure your device has internet access and that is it configured to receive push notifications from the authenticator app (uninstall/reinstall if needed)
Lastly, if one of the contact options (push, call or text/sms) is not working, try to utilise i of the other options instead.
I lost the telephone I use for Azure MFA. What should I do?
Contact the UNM It Service Desk immediately if you lot lose a device enrolled in Azure MFA or suspect that it's been stolen. Nosotros will disable it for authentication and help yous log in using another device.
Why practice I only receive the Azure MFA prompt sometimes or with some apps and not others?
Dissimilar applications take different security requirements and we try to utilize MFA every bit least invasively every bit nosotros can, based on security decisions made by our application owners and the Information Security and Privacy Office (ISPO).
Short answer, exercise not be alarmed if you are only prompted to cosign with MFA sometimes. The experience is designed to be equally frictionless equally possible.
Less sensitive applications may just crave MFA from off campus ("untrusted" networks) or when accessed via specific protocols. Other applications may require MFA every logon, regardless of whether you are on or off campus. Some applications may non crave MFA at all.
Another item to consider is whether you opted in to the "Stay signed in" mode on your device(s). That selection suppresses the MFA prompt on trusted devices for upwards to 180 days.
If you have any questions please open a Chat session OR submit an "Inquire a Question" via FastInfo (Staff/Kinesthesia) or StudentInfo (Students). If the previous options do not provide a satisfactory resolution to your question then delight call IT (Information Technologies) Customer Support Services at 277-5757.
Source: https://unm-student.custhelp.com/app/answers/detail/a_id/7823/~/what-is-azure-multi-factor-authentication-%28mfa%29-and-how-does-it-work-at-unm%3F
0 Response to "There Was an Unexpected Error Verifying Your Barcodes. Please Try Again Later."
Post a Comment