“Unable to Connect to Authentication Service Error” usually occur due to incorrect DNS configuration and windows firewall. You can fix it with below solutions:

#1 Change DNS Server address

• Press the Windows key + R.
• Type control and click OK to open Control Panel.
• Go to Network and Internet > Network and Sharing Center.
• Click the Change adapter settings option from the left pane.
• Right-click on the network adapter and select Properties.
• In the Properties window, double-click on Internet Protocol Version 4 (TCP/IPv4).
• Select Use the following DNS server address.
• In the Preferred and Alternate DNS server field enter the following:
• 8.8.8
• 8.8.4.4.
• Check the Validate settings upon exit box.
• Click OK to save the changes.

#2 Disable Windows Defender Firewall

• Press the Windows key + I.
• Click on Update & Security.
• Open the Windows Security tab from the left pane.
• Click on Firewall & Network Protection.
• Click on your currently active profile (Public in most cases).
• Toggle the switch to turn off Windows Defender Firewall.

Now, We will know that How Google authenticator works?

Google Authenticator is a two-factor authentication app that provides an extra layer of security for online accounts. It works by generating one-time codes that can be used for logging into an account in addition to a password.

Here is how it works?

Step-1) Account setup:- The user sets up two step verification on their account by enabling it in their account security settings and linking it with the Google Authenticator app.

Step-2) QR code scanning:- The user scans a QR code provided by the account with the Google Authenticator app, which links the account with the app.

Step-3) Code generation:- The Google Authenticator app generates a unique 6-digit code every 30 seconds.

Step-4) Login process:- When the user logs into their account, they are prompted to enter their password and the current code generated by the Google Authenticator app.

Step-5) Verification:- The server checks if the code entered by the user matches the code generated by the Google Authenticator app and verifies the user's identity.

This process provides an extra layer of security, making it more difficult for hackers to gain access to an account as they would need both the password and access to the device running the Google Authenticator app.

Conclusion:—I hope, you are getting answer of this question clearly. If you satisfy with this answer then follow us. It's your choice.

Thank you

Continuous authentication is a method of providing users access to internet services depending on risk levels or contextual information that is deemed acceptable. Continuous authentication is passive, whereas traditional authentication is active, requiring the user to give an authentication factor (e.g., knowledge, ownership, or biometric) to get access in each case. Continuous authentication calculates an authentication score based on browser metadata, user location, passive liveness detection, and the time of day.

Let me give a simple example to explain it better

"At my bank, we established a system known as "continuous authentication." Now, everytime I log onto my work computer, it appears to recognise if I'm connected to the business network and logs me out automatically if I leave the office."

The system incorporates a variety of methods for ongoing authentication. Some of the most popular verification methods that continuous authentication uses for its hassle-free functioning are listed below.

1. Verification using biometrics

The most secure authentication mechanism used by a system is biometric authentication. Some of the benefits of biometric authentication are listed below:

a) Physiological characteristics can be compared to permitted attributes stored in a database with ease.

b) Biometric authentication can also be used to regulate physical access to multiple entrances.

c) Biometric authentication can be used as part of a two-factor authentication system.

2. Password-based authentication

Passwords are one of the most often used methods of ongoing authentication. A person's network is protected by a mix of letters, numbers, strings, or any other special character. To provide your network more protection, it's critical to generate strong passwords that use all of the above-mentioned combinations. However, because these passwords are so readily cracked by fraudsters, they have become increasingly vulnerable to numerous phishing schemes.

3. Certificate-based authentication

The system employs digital certificates to identify its users in this fashion. A digital certificate is a digital document that serves as a system licence for the consumer. It is only granted by a certification authority and contains a key that contains the consumer's digital signature. This approach of certification-based authentication provides a more secure means of logging into a system.

The usage of certificate-based continuous authentication may be found in software development firms where data and privacy are at risk.

It is a relatively recent advancement in User authentication technology.

In traditional authentication systems, the user (or even device) is authenticated once at the start of session. The server system/application assumes the same User is continuing to interact with the server.

There have been many security incidents wherein an authenticated session is hijacked/intercepted by malicious software/attacker. Examples of session interception/hijacking include MITM, MITB (man-in-the-browser) kind of attacks.

Similarly there have been incidents where the User has left the computer/phone unattended during a coffee break/lunch. This has let to misuse.

Security experts and companies have promoted the concept of continuous authentication to protect the active session.

In such systems, the User and or Device are periodically and continuously re-authenticated for the lifetime of the session. Often in such security systems, the (re-)authentication is done transparently to the User so as to not inconvenience the User.

For example: the User can wear a biometric device like wristband while using the application/server and that wristband keeps authenticating to the security system.

There are many implementations of such a mechanism including using mobile devices, security tokens, special usb connected to the computer during the lifetime of the session etc

There are some vendors use User behavior analytics (ex: keystrokes, dwell time etc) to identify session compromise and force re-authentication

Google Authenticator supports both the HOTP and TOTP algorithms for generating one-time passwords.

With HOTP, the server and client share a secret value and a counter, which are used to compute a one time password independently on both sides. Whenever a password is generated and used, the counter is incremented on both sides, allowing the server and client to remain in sync.

TOTP essentially uses the same algorithm as HOTP with one major difference. The counter used in TOTP is replaced by the current time. The client and server remain in sync as long as the system times remain the same. This can be done by using the Network Time protocol.

The secret key (as well as the counter in the case of HOTP) has to be communicated to both the server and the client at some point in time. In the case of Google Authenticator, this is done in the form of a QRCode encoded URI.

Authenticator works for any site or service that has enabled two-factor authentication. Like most web-based 2FA applications, the system combines knowledge and possession features. To access websites or web-based services, the user types in his normal username and password and then enter a one-time passcode (OTP) that was delivered to his device, triggered by the login. That combination verifies that the same person entering login data on the site is in possession of the device to which the Google Authenticator app was downloaded.

Passwords may be easy to crack or otherwise steal but because the vast majority of exploits are conducted via the Internet, it is unlikely that the hacker also has access to the user's physical device.

The Authenticator app is based on the time-based one-time password (TOTP) system specified in the IETF's RFC 6238 document. The TOTP algorithm generates a six-digit passcode that factors in the current time of day to ensure that each passcode is unique. Passcodes are changed every 30-60 seconds for further security.