diff --git a/content/engineering/what-is-oauth2-0/authentication-authorization-and-encryption.webp b/content/engineering/what-is-oauth2-0/authentication-authorization-and-encryption.webp new file mode 100644 index 000000000..64fd7f698 Binary files /dev/null and b/content/engineering/what-is-oauth2-0/authentication-authorization-and-encryption.webp differ diff --git a/content/engineering/what-is-oauth2-0/index.md b/content/engineering/what-is-oauth2-0/index.md new file mode 100644 index 000000000..b6d38e046 --- /dev/null +++ b/content/engineering/what-is-oauth2-0/index.md @@ -0,0 +1,243 @@ +--- +title: "A comprehensive guide to OAuth 2.0 " +date: "2025-03-27" +coverImage: "what-is-oauth2-0.webp" +author: "Kundan Singh" +tags: ["Oauth", "Authorization Code Flow","Authorization","Authentication"] +description: Ever clicked "Login with Google"? That’s OAuth 2.0 behind the scenes—securely granting apps access to your data without sharing passwords. In this guide, we break down what OAuth 2.0 is, how it improves upon OAuth 1.0, and why it’s become the industry standard for secure authorization in APIs, mobile apps, and web platforms. +metatitle: "OAuth 2.0 Explained: A Complete Guide to Secure Authorization" +metadescription: "Discover how OAuth 2.0 works, why it replaced OAuth 1.0, and how it secures modern applications. Learn about access tokens, grant types, and real-world use cases." +--- + +## Introduction + +Have you ever used "Login with Google" or granted an app permission to access your private files from the cloud? That’s OAuth 2.0 in action. + +OAuth 2.0 is a secure authorization framework that allows applications to access your data without having to share passwords. While often mistaken as an Authentication framework, OAuth 2.0 strictly deals with authorization, using access tokens to grant permissions to resources for a specified period. + +However, if you’re also unclear about how authentication differs from authorization? Check out our detailed blog:[ Authentication vs. Authorization](https://www.loginradius.com/blog/identity/authentication-vs-authorization-infographic/). + +OAuth 2.0 is an important part of modern authorization. It helps platforms keep access controls secure and organized. It also makes it easy to manage user interactions. + +In this blog, we will break down how OAuth 2.0 works, why it is important and how it improves upon its predecessor, OAuth 1.0. + +## What is OAuth 2.0? + +OAuth 2.0 is a [token-based authorization](https://www.loginradius.com/blog/engineering/authorization-code-flow-oauth/) framework that provides access to resources without sharing user credentials. Suppose you have some pictures in a cloud drive that you wish to print from a local photo printing shop. You can enable the print shop to access your photos in this drive without sharing your password by using OAuth 2.0 authentication. + +This keeps your account safe. It lets the shop access the information it needs. It also makes sure they cannot see anything else in your personal account. In essence, OAuth 2.0 serves the purpose of managing privacy and safety of your information as well as granting the permissions needed. + +## Need for OAuth 2.0 + +Before OAuth, users had to share actual credentials (username and password) with applications that needed to access their data. We all understand why this approach was risky. + +### OAuth 1.0: The First Step Toward Secure Authorization + +OAuth 1.0 introduced a token-based system to eliminate this need for credential sharing. Users could now grant limited access to their data via tokens. However, OAuth 1.0 had these limitations: + +* Challenging to implement as every API request required cryptographic signatures. + +* Difficult to adapt to new use cases, such as mobile apps. + +* Cumbersome to extend sessions as there were no standardized tokens. + +### OAuth 2.0: A More Flexible and Scalable Solution + +OAuth 2.0 was not just an upgrade—it was a complete rewrite designed to be more developer-friendly, scalable, and secure. + +Key improvements included: + +* Access tokens replaced API request signing, thereby reducing complexity. + +* OAuth 2.0 introduced different grant types for different use cases, helping reach mobile app users. + +* Seamless authorization flows with fewer steps for users, improving overall experience. + +* Standardized refresh tokens allowed maintaining access without storing credentials. + +With these improvements, OAuth 2.0 became the industry standard for authorization, used by platforms like Google, Facebook, and Microsoft. + +### Key Differences Between OAuth and OAuth2.0 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Feature + OAuth 1.0 + OAuth 2.0 +
Architecture + More complex, requires cryptographic signatures for every request. + Simpler, uses access tokens for authorization. +
Security + Relies on request signing and shared secrets for security. +

+Medium +

Focuses on token-based security with various grant types. +

+High (if implemented correctly) +

Mobile Support + Less suitable for mobile apps due to complexity. + Designed with mobile apps in mind, offering simpler flows. +
Token Handling + Uses request tokens and access tokens, requiring more steps. + Uses access tokens, refresh tokens, and authorization codes, depending on the grant type. +
Scalability + More challenging to scale due to complex signature requirements. + Highly scalable and flexible, supporting various use cases. +
User Experience + Can be more cumbersome for users due to multiple steps. + Offers smoother user experience with simpler authorization flows. +
+ +[![Image showing free loginradius guide named A quick guide to authentication, authorization, and encryption for enterprises.](authentication-authorization-and-encryption.webp)](https://www.loginradius.com/resource/whitepaper/secure-api-using-oauth2) + +## How OAuth 2.0 Works + +**The following parties are important to understand the process:** + +**1. User (Resource owner)**: Usually the end-user who has the data and grants permission. + +**2. Client:** The service or application seeking access to the user’s data. + +**3. Authorization Server:** The system that verifies the users and issues access tokens. + +**4. Resource Server:** The service or application that holds the user’s data and grants access only when a valid token is available. + +### Basic OAuth 2.0 Flow: + +1. The client seeks permission from the user to authorize access. + +2. The user is taken to the Authorization Server to grant or deny access. + +3. If approved, the Authorization Server provides an authorization code to the client. + +4. The client utilizes the authorization code to acquire an access token from the authorization server. + +5. The client uses the access token to request protected data from the Resource Server. + +This approach guarantees that the applications receive the exact permissions required from the resource owner without ever accessing the password. + +![OAuth 2.0 authorization flow showing steps from user consent to access token and protected data request.](oauth2-0-authorization-flow.webp) + +## OAuth 2.0 Access Tokens and Authorization Code + +The access token is a temporary key that allows an application to access resources. It gets issued after a successful authorization code exchange and has an expiration time for security purposes. It is often paired with a refresh token, which allows for extended access without re-authentication. + +## Getting Started with OAuth 2.0 Using LoginRadius + +Ready to implement OAuth 2.0? LoginRadius makes it easy to get started in just a few steps. + +### 1. Set Up Your Application + +Log into the[ LoginRadius Admin Console](https://accounts.loginradius.com/auth.aspx?return_url=https://console.loginradius.com/login&action=register) and go to **Applications > Apps**. Click **Add Apps**, name your app, choose **OAuth 2.0** as the protocol, and select the appropriate app type (e.g., Native, SPA, Web, or M2M). Hit **CREATE** to generate the config. + +![LoginRadius dashboard showing the interface to create a new application with OAuth 2.0 or OpenID Connect and various app types.](openID-connect.webp) + +### 2. Configure OAuth Settings + +Fill in key fields like: + +* **Client ID & Secret** – credentials for your app + +* **Grant Types** – select one or more flows (Authorization Code, PKCE, etc.) + +* **Redirect URLs & CORS Origins** – for secure callback and cross-origin access + +* **Token Expiry & Reauthentication** – define token lifespan and re-login behavior + +Click **Save** when done. + +### 3. Enable Identity Providers + +Toggle on the login options (social or custom) your app will support. This gives users flexibility to sign in with their preferred IDP. + +### 4. Refresh Tokens When Needed + +Use the refresh token API to renew access tokens without making users log in again. Just pass the client_id, grant_type, and refresh_token in a POST request. + +LoginRadius supports all major OAuth 2.0 flows, making it easy to build secure, scalable login across apps, APIs, and devices. + +Do check our [technical documentation ](https://www.loginradius.com/docs/single-sign-on/federated-sso/oauth-2.0/overview/?q=oauth)covers everything in detail—from authorization flows to token handling. + +## What is an Authorization Grant, and What Are the Key Types? + +**OAuth 2.0** offers different ways (grant types) for applications to obtain an access token, depending on their needs: + +* **Authorization Code Grant**: This is intended for web and mobile apps as it mandates a code exchange for security. + +* **Implicit Grant**: A less complex flow that is not recommended anymore for security reasons. + +* **Client Credentials Grant**: This is designed for appliance-to-appliance communications. + +* **Resource Owner Password Credentials Grant**: This allows users to log in with their credentials, although it is not very popular because of security challenges. + +* **Refresh Token Grant**: It allows maintaining login for a user for an extended period without them having to log in again. + +## Why Your Business Needs OAuth 2.0 + +Safeguarding sensitive information should be a top priority in today’s digital world, and OAuth 2.0 makes it easier to minimize risks associated with security breaches by limiting applications to only the information they have access to. + +Businesses that manage large quantities of data or function in highly regulated markets need compliant OAuth 2.0 implementations to maintain trust and compliance. Implementing an OAuth 2.0 system brings the following advantages: + +* **Better Security:** Organizations can eliminate unauthorized access to sensitive information by reducing the use of passwords and utilizing tokens instead, making their security measures more effective. + +* **Improved User Experience:** Users can easily simplify the authentication process by easily granting or denying access to different applications. + +* **Scalability:** OAuth 2.0 is widely adopted by numerous services ranging from Google to Facebook as it enables use across a wide range of platforms. + +* **Flexibility:** Consistent access across various devices and platforms is guaranteed as OAuth 2.0 works on numerous devices and enables multiple environments. + +## Conclusion + +OAuth 2.0 has become the go-to authorization option due to its versatile support of multi-services, APIs, and websites and its capacity to ease secure access. + +Leveraging platforms like LoginRadius makes the design and maintenance of an OAuth 2.0 workflow much easier. It simplifies the authorization process for your users and your business's security, regardless if your company is using web apps, mobile apps, or APIs. + +Contact us today and book a live participation demo to see how you can improve your security infrastructure. Start here: [to book a live demo](https://www.loginradius.com/contact-us). + +## **FAQs** + +### **1. What is Open Authorization?** + +**A:** Open Authorization (OAuth) is an open-standard authorization framework that allows applications to access a user's data without exposing their credentials. Instead of sharing passwords, OAuth uses access tokens to grant limited and secure access to resources. + +### **2. What are the key components of OAuth2?** + +**A:** The key components of OAuth 2.0 include User aka Resource Owner, Client (Application), Authorization Server, Resource Server, and Access Token + +### **3. What is the auth token?** + +**A:** An auth token (authentication token) is a digital credential used to verify a user's identity and grant access to a system without requiring repeated logins. It is typically a temporary, encrypted string issued by an authentication server after a successful login. Common types include OAuth 2.0 access tokens and JWT (JSON Web Tokens). \ No newline at end of file diff --git a/content/engineering/what-is-oauth2-0/oauth2-0-authorization-flow.webp b/content/engineering/what-is-oauth2-0/oauth2-0-authorization-flow.webp new file mode 100644 index 000000000..9b9c84003 Binary files /dev/null and b/content/engineering/what-is-oauth2-0/oauth2-0-authorization-flow.webp differ diff --git a/content/engineering/what-is-oauth2-0/openID-connect.webp b/content/engineering/what-is-oauth2-0/openID-connect.webp new file mode 100644 index 000000000..cf5d089a1 Binary files /dev/null and b/content/engineering/what-is-oauth2-0/openID-connect.webp differ diff --git a/content/engineering/what-is-oauth2-0/what-is-oauth2-0.webp b/content/engineering/what-is-oauth2-0/what-is-oauth2-0.webp new file mode 100644 index 000000000..c90036654 Binary files /dev/null and b/content/engineering/what-is-oauth2-0/what-is-oauth2-0.webp differ diff --git a/content/identity/authentication-authorization-encryption/OTP-authentication.webp b/content/identity/authentication-authorization-encryption/OTP-authentication.webp new file mode 100644 index 000000000..df7f2868e Binary files /dev/null and b/content/identity/authentication-authorization-encryption/OTP-authentication.webp differ diff --git a/content/identity/authentication-authorization-encryption/authentication-authorization-encryption.webp b/content/identity/authentication-authorization-encryption/authentication-authorization-encryption.webp new file mode 100644 index 000000000..3dd24e861 Binary files /dev/null and b/content/identity/authentication-authorization-encryption/authentication-authorization-encryption.webp differ diff --git a/content/identity/authentication-authorization-encryption/authentication-authorization.webp b/content/identity/authentication-authorization-encryption/authentication-authorization.webp new file mode 100644 index 000000000..7fd21a7cd Binary files /dev/null and b/content/identity/authentication-authorization-encryption/authentication-authorization.webp differ diff --git a/content/identity/authentication-authorization-encryption/index.md b/content/identity/authentication-authorization-encryption/index.md new file mode 100644 index 000000000..9e04bcce3 --- /dev/null +++ b/content/identity/authentication-authorization-encryption/index.md @@ -0,0 +1,190 @@ +--- +title: "Understanding Authentication, Authorization, and Encryption" +date: "2025-04-01" +coverImage: "authentication-authorization-encryption.webp" +tags: ["Identity management","Authentication","Encryption","Authorization","Security"] +author: "Kundan Singh" +description: "Authentication, authorization, and encryption are the backbone of modern digital security. This guide breaks down each term with real-world clarity and practical examples. Learn how they work together to protect identities, control access, and secure your data." +metatitle: "Authentication, Authorization, and Encryption Explained" +metadescription: "Understand authentication, authorization, and encryption in security. Learn the difference with real-world examples and use cases." +--- + +You’ve probably heard these three words tossed around a lot: authentication, authorization, and encryption. They sound pretty technical—maybe even interchangeable—but trust me, they’re not. And if you use the internet (which you clearly do, at least for reading this blog 😀), these concepts touch your life more than you realize. + +Whether you’re logging into a website, sending a secure message, or working on a company app, there are security layers working behind the scenes. Let’s take a real-world look at what all of these terminologies mean, how they differ, and why you should care. + +## What is Authentication? + +[Authentication](https://www.loginradius.com/blog/identity/what-is-authentication/) is the process of confirming that someone (or something) is genuinely who they claim to be. The word comes from the Greek "authentikos," which means real or genuine. + +Okay, let’s start simple. Authentication is just a fancy word for proving you are who you say you are. That’s it. No smoke, no mirrors. + +Every time you log into an account, ex: Netflix, you unlock your phone with your fingerprint or enter a six-digit code sent to your device—that’s authentication doing its thing. + +The idea is straightforward: before any system lets you in, it needs to know you're legit. And these days, it’s not just about usernames and passwords. You’ve probably noticed apps asking for a fingerprint, a face scan, or that one-time passcode (OTP) sent to your email or phone. + +That’s because passwords alone aren’t enough anymore. Hackers are getting creative. We sometimes reuse our passwords, and if the hackers crack them once, they might get access to other accounts as well. + +That’s why [multi-factor authentication (MFA)](https://www.loginradius.com/blog/identity/what-is-multi-factor-authentication/) is becoming the norm these days—it layers security by asking for more than one way to confirm who you are. + +In more technical environments, especially when apps talk to each other, things like API authentication and authorization come into play. That’s how systems verify that another system or app has the right to connect and access certain data. + +So, in a nutshell? Authentication is the digital version of someone asking for your ID—and checking that it’s not fake. + +![An illustration depicting a user with a mobile screen waiting for a one-time-password to be used as an authentication mechanism.](OTP-authentication.webp) + +## What is Authorization? + +Now, just because you’ve proven who you are doesn’t mean you get access to everything. That’s where authorization comes in. + +Let’s say you log into your workplace dashboard. Congrats—you’re authenticated. But are you allowed to see payroll data? Can you edit customer details? Probably not unless you’re in HR or account management, respectively. + +Authorization is all about setting access boundaries. It tells the system what you’re allowed to do once you’re inside. Think of it like a hotel keycard: you may have access to your room and the gym, but not the staff area or other specific places. + +What’s really important is this: authentication and authorization are not the same. You can’t authorize someone until you’ve authenticated them. First, the system checks who you are. Then it decides what you’re allowed to do. + +And guess what? One of the biggest security risks companies face isn’t just letting the wrong people in—it’s giving the right people too much access. That’s why authorization rules need to be tight, specific, and constantly reviewed. + +Most organizations manage this using mechanisms like [role-based access control (RBAC) ](https://www.loginradius.com/blog/identity/what-is-rbac/)or authorization platforms that let admins set rules and permissions. So, if you’re in marketing, you might be authorized to create a new campaign but not touch financial reports. + +Here’s how setting up roles and permissions in the [LoginRadius CIAM](https://accounts.loginradius.com/auth.aspx?return_url=https://console.loginradius.com/login&action=register) looks like: + +![LoginRadius dashboard with roles and permissions page where a user can manage roles by assigning permissions for different users like admin or customer.](roles-and-responsibilities.webp) + +Look how easily businesses can define and manage user roles and permissions. With just a few clicks, you can control access levels, ensuring admins, customers, and other users only see and do what they’re allowed to. It’s streamlined, secure, and built for scalable identity management. + +## What is Encryption? + +If authentication and authorization are about who and what, encryption is all about how the data is protected. + +Here’s the gist: [encryption](https://www.loginradius.com/blog/engineering/encryption-and-hashing/) takes your data and scrambles it into a secret code. Unless someone has the right key, they can’t read it. + +It’s kind of like writing a note in a language only you and a friend understand. Even if someone grabs the note, it’s gibberish to them. + +Encryption is working all the time. Ever noticed the little lock icon in your browser when you’re on a secure site? That’s HTTPS, and it means your data is encrypted between your device and the website. Cloud storage platforms? Encrypted. Messaging apps like Signal? Encrypted. Online banking? You better believe it’s encrypted. + +There are two main flavors of encryption: + +* **Symmetric**, where the same key is used to lock and unlock the data. + +* **Asymmetric**, which uses two keys: a public one to encrypt and a private one to decrypt. + +Most modern apps and services use both, depending on the scenario. And here’s a cool twist: there's something called authenticated encryption, where the system not only encrypts the message but also verifies where it came from. This is used in things like secure APIs, encrypted chats, and VPN connections—where both privacy and trust matter. + +So, even if someone intercepts your data without the key, it’s just digital noise. + +## How Encryption and Authentication Work Together? + +Here’s where it gets interesting. These tools don’t work in silos. They stack, like layers of armor. + +Let’s say you’re working remotely and need to connect to a secure work server. First, you go through authentication—maybe your password, plus a biometric check. Once you’re in, any files you download or send are encrypted, so nobody can snoop on them in transit. + +It’s a one-two punch: verify the person, then protect the data. You’ve probably heard of “end-to-end encryption.” That’s a real-world example of encryption and authentication teaming up. + +When both are done right, even if someone intercepts the communication, it won’t matter because the data’s encrypted, and only verified users can unlock it. + +Still need a deeper comparison between authentication, authorization, and encryption? Download this insightful guide: + +[![Illustration depicting a free downloadable resource from LoginRadius named- a quick guide to authentication, authorization, and encryption for enterprises.](authentication-authorization.webp)](https://www.loginradius.com/resource/guide/authentication-authorization-encryption-guide/) + +## Authentication vs Authorization vs Encryption: How They Really Differ + +Let’s be honest—these terms get thrown around like they’re interchangeable. But understanding the difference between authentication and authorization, and how encryption fits in, is crucial. + +Here’s a simplified breakdown: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Feature + Authentication + Authorization + Encryption +
What it means + Confirming identity + Granting access based on that identity + Scrambling data so others can't read it +
Key question + “Who are you?” + “What can you do?” + “Is this data protected?” +
When it happens + First + After authentication + Any time data is at rest or in transit +
Example + Logging into Spotify + Accessing premium-only content + Securing your playlist metadata +
Used for + Login, SSO, MFA + Role-based permissions + HTTPS, secure messaging, file storage +
+ +All three—authentication, authorization, and encryption—form a triangle of trust. You need identity, permissions, and data protection working together. Leave one out, and you’ve got a hole in your security strategy. + +## So, Here’s the Takeaway + + +* **[Authentication](https://www.loginradius.com/platforms/authentication-and-registration)** is how systems confirm who you are. + +* **[Authorization](https://www.loginradius.com/platforms/authentication-and-federation)** is how they decide what you’re allowed to do. + +* **[Encryption](https://www.loginradius.com/legacy/docs/security/data-management/confidentiality-integrity-and-availability/#dataconfidentiality0)** is how your data stays hidden from the wrong eyes. + +If you think about it, these principles are everywhere. They protect your emails, secure your files, keep your personal info out of the wrong hands, and even safeguard the APIs that power your favorite apps. + +Whether you're managing a cloud platform, building a SaaS product, or just want better control over your digital life, understanding these three terms can go a long way. And if you're in cybersecurity, this trio is your toolkit. + +We’ve come a long way from passwords and PINs. In today’s zero-trust, cloud-native world, we need authentication encryption, context-aware authorization, and seamless identity management just to keep up. + +## FAQs + +### 1. What is the difference between authentication and authorization? +**A.** Authentication checks your identity. Authorization checks your permissions. You can’t be authorized without being authenticated first. + +### 2. How does authentication work? +**A.** It checks your login credentials (like passwords or fingerprints) against a known system. If they match, you're in. If not, you’re locked out. + +### 3. Is OTP authentication or authorization? +**A.** OTP is used for authentication. It confirms who you are by verifying that you also have access to a trusted device or email. + +### 4. Is SSO authentication or authorization? +**A.** SSO is an authentication method. It lets you log in once and access multiple systems without logging in again. Authorization still controls what you can do once inside. + +[![book-a-demo-loginradius](../../assets/book-a-demo-loginradius.png)](https://www.loginradius.com/contact-us) \ No newline at end of file diff --git a/content/identity/authentication-authorization-encryption/roles-and-responsibilities.webp b/content/identity/authentication-authorization-encryption/roles-and-responsibilities.webp new file mode 100644 index 000000000..0da98eca2 Binary files /dev/null and b/content/identity/authentication-authorization-encryption/roles-and-responsibilities.webp differ diff --git a/content/identity/what-is-authentication/adaptive-mfa.webp b/content/identity/what-is-authentication/adaptive-mfa.webp new file mode 100644 index 000000000..6f804e73b Binary files /dev/null and b/content/identity/what-is-authentication/adaptive-mfa.webp differ diff --git a/content/identity/what-is-authentication/adaptive-multi-factor-authentication.webp b/content/identity/what-is-authentication/adaptive-multi-factor-authentication.webp new file mode 100644 index 000000000..00201b237 Binary files /dev/null and b/content/identity/what-is-authentication/adaptive-multi-factor-authentication.webp differ diff --git a/content/identity/what-is-authentication/authenticate-using-password.webp b/content/identity/what-is-authentication/authenticate-using-password.webp new file mode 100644 index 000000000..356543d65 Binary files /dev/null and b/content/identity/what-is-authentication/authenticate-using-password.webp differ diff --git a/content/identity/what-is-authentication/authentication.jpg b/content/identity/what-is-authentication/authentication.jpg deleted file mode 100644 index 4b0486889..000000000 Binary files a/content/identity/what-is-authentication/authentication.jpg and /dev/null differ diff --git a/content/identity/what-is-authentication/cover-auth.jpg b/content/identity/what-is-authentication/cover-auth.jpg deleted file mode 100644 index 092d37756..000000000 Binary files a/content/identity/what-is-authentication/cover-auth.jpg and /dev/null differ diff --git a/content/identity/what-is-authentication/flowchart.webp b/content/identity/what-is-authentication/flowchart.webp new file mode 100644 index 000000000..eae34afc9 Binary files /dev/null and b/content/identity/what-is-authentication/flowchart.webp differ diff --git a/content/identity/what-is-authentication/gdpr-compliance.webp b/content/identity/what-is-authentication/gdpr-compliance.webp new file mode 100644 index 000000000..c06e14e13 Binary files /dev/null and b/content/identity/what-is-authentication/gdpr-compliance.webp differ diff --git a/content/identity/what-is-authentication/how-mfa-works.webp b/content/identity/what-is-authentication/how-mfa-works.webp new file mode 100644 index 000000000..d9bef383c Binary files /dev/null and b/content/identity/what-is-authentication/how-mfa-works.webp differ diff --git a/content/identity/what-is-authentication/index.md b/content/identity/what-is-authentication/index.md index 5783f30e6..2791f2aad 100644 --- a/content/identity/what-is-authentication/index.md +++ b/content/identity/what-is-authentication/index.md @@ -1,70 +1,344 @@ --- -title: "What is Authentication" +title: "What is Authentication? Definition and How It Works" date: "2021-03-29" -coverImage: "cover-auth.jpg" -tags: ["authentication","data security","mfa"] -author: "Manish Tiwari" -description: "Authentication is the process of uniquely identifying an individual via a set of credentials. In the digital world, authentication is termed as verifying a person's identity or an electronic device. Authentication becomes necessary because it increases the security of consumer's data." -metatitle: "What is Authentication?" -metadescription: "Learn the basics of authentication and how it is used. We have also covered how authentication works and what are the benefits to the organizations." +updated_date: "2025-03-28" +coverImage: "what-is-authentication.webp" +tags: ["Authentication","Data Security","MFA","Identity Management"] +author: "Rakesh Soni" +description: "Authentication is the digital gatekeeper that verifies identity—from unlocking smartphones to accessing enterprise cloud applications. But authentication goes beyond passwords; it's about protecting digital identities and ensuring only authorized access to data and systems. In this guide, we'll break down authentication's fundamentals, explore various methods, and highlight how innovative businesses implement modern protocols to stay secure." +metatitle: "What is Authentication? Types, Factors, and Protocols" +metadescription: "Learn what authentication is, its types, methods, and real-world use cases. Explore MFA, SAML, biometrics, and more in this complete guide." --- -# A Beginner's Guide to Authentication +## Introduction -We all have witnessed a spike in online user platforms from the past few years, catering to every service you can think of. This is because making things digitally available has eased the consumer’s struggle. +From unlocking your smartphone to signing in to enterprise cloud tools, authentication has become a key part of our digital lives. It’s the gatekeeper—deciding whether someone should be allowed access to a particular application, platform, or service. -For example, now you can order your food just by logging in to a food catering website. Easy, right? Everything is now just a click away. Your banking transactions, business, things of entertainment like movies and Netflix. Everything! +As cyber threats continue to evolve, it's more important than ever for developers, businesses, and everyday users to grasp the intricacies of authentication, understand how it works, and appreciate its significance in maintaining digital security. -But with all these services comes a massive task for the service providers, and that task is to verify that you are their actual consumer and not an imposter trying to steal data. So, to verify users, businesses use a technical approach called authentication. +But authentication isn’t just about typing in a password or logging in. It’s about safeguarding digital identities and ensuring systems and data remain accessible only to the right individuals under the right conditions. -## What is Authentication +With the rise of zero-trust security models, [identity-first strategies](https://www.loginradius.com/blog/identity/decoding-ethics-identity-first-security/), and privacy-by-design approaches, authentication is at the very heart of modern digital security. -Authentication is the process of uniquely identifying an individual via a set of credentials. In the digital world, authentication is termed as verifying a person's identity or an electronic device. +In this insightful guide, we’ll walk through what authentication means, explore different types and methods, and show how forward-thinking businesses are using modern authentication protocols to keep users secure and compliant. -Authentication becomes necessary because it increases the security of consumer's data. Without verifying or authenticating oneself, no one can enter the website and access your data. The most popular example of authentication is entering into a system using login credentials. +## What is Authentication and How Does User Authentication Work? -With the huge increase in the number of digital platforms, the demand for various authentication processes has been increasing for both online and physical systems. +Authentication is the process of confirming that someone (or something) is genuinely who they claim to be. The word comes from the Greek "authentikos", which means real or genuine. -![What is Authentication](authentication.jpg) +When we talk about a digital environment, authentication acts as a foundational security layer—preventing unauthorized access to systems, apps, and data. This role of authentication provides a sense of security and protection in the digital world. -## How Authentication Is Brought Into Use +In a nutshell, authentication checks whether the credentials provided—like a password, fingerprint, or digital token—match what’s stored in the system. It happens before authorization and is a critical part of digital safety to ensure only the authorized person/machine has access to the resources/platforms. -Authentication can be divided into two major categories. +![An image showing a mobile device and a security official asking for authentication.](mobile-data-security.webp) -1. Human to machine authentication -2. Machine to machine authentication +## What Does Authentication Mean in a Digital Context? -In any of the above types of authentication, there is a requirement for certain credentials. In human verification, we have a user ID and password set by the consumer, while for machines, we have certificates and IP addresses, along with other information. +In today’s modern digital landscape, authentication ensures that only legitimate users and systems can access sensitive resources. It’s a core part of building trust, stopping fraud, and staying compliant with privacy regulations like [GDPR, HIPAA, and CCPA](https://www.loginradius.com/blog/identity/stay-compliant-with-data-privacy-laws-2023/). This role of authentication reassures us and instills confidence in the digital systems we use. -Generally, a consumer has to select or create a User ID and corresponding password for that unique ID that the system will use to verify user credibility. Many companies make use of authentication to verify the users who try to login into their digital platforms. But if consumers' data falls into cybercriminals' hands, it can cause some severe problems. Hence companies ensure using high-level security measures, which involves using another advanced authentication level such as [multi-factor authentication](https://www.loginradius.com/resource/ebook/buyers-guide-to-multi-factor-authentication/). +From a user perspective, good authentication means a secure but seamless login experience. For businesses, it’s about protecting data, avoiding breaches, and maintaining a trustworthy brand. +Looking to deliver both security and user experience? Explore how the LoginRadius authentication platform simplifies authentication and registration for modern apps: -## How Does Authentication Work +[![Loginradius resource named securing user authentication understanding the basics and best practices with free download button.](securing-user-auth.webp)](https://www.loginradius.com/resource/whitepaper/user-authentication-security/) -As mentioned above, the consumer needs to create a unique user ID and password at registration. The system will use this data to validate the consumer whenever they attempt to log in next time. These credentials will be stored in the companies database or on the local operating system through an authentication server. +## How Does User Authentication Work? -Now when the consumer enters these credentials on login, the entered credentials are matched with the ones stored in the database. If the credentials match, the consumer is given access into the portal; else access is denied. +Here’s how a typical authentication process works: -Now the question comes how to create such credentials which can be remembered easily? +![Flowchart illustrating the user authentication process from credential submission to validation, leading to either granted access or authentication failure.](flowchart.webp) -There are a few ways that can help you in simplifying your validation. These ways are: +1. **Credentials Submission:** A user provides an identifier (username or email) along with an authenticator, like a password, fingerprint, or one-time passcode (OTP). -1. **Things you know (knowledge)**: This method involves questions that only you can answer. What is your mother's maiden name? Or what is your child's name? The purpose is to verify your identity via these questions because you are the only one who can answer these. +2. **Validation Check:** The system compares this information against stored credentials. -2. **Things you have(possession)**: This method involves verification from the things you have or possess, such as a mobile phone. A verification notification will be sent to your phone screen, and when you allow it from that screen only, you will be able to log in to your account. +3. **Token or Session Creation:** If the credentials match, the system starts a user session or generates an authentication token (e.g., a JSON Web Token or JWT). -3. **Things you are(inheritance)**: A fingerprint or retinal scan commonly verifies this factor. This method's purpose is clear; only you can have your fingerprint and no one else. +4. **Access Granted:** Once authenticated, the user gains access to the appropriate system or service. -## How Authentication Is Useful for Business +## The Evolution of Authentication -With data breaches continually on the rise in headlines and consumers becoming more personally involved in their information security, most businesses already understand the importance of cybersecurity. +### 1. The Password Era (1960s) -Even small businesses have some sort of authentication for their systems. This is done by asking the employees to enter a single sign-on password to access company data. This way, businesses ensure that sensitive information is accessed only by authorized individuals. +Authentication began with passwords in the 1960s, first implemented in the [Compatible Time-Sharing System](https://en.wikipedia.org/wiki/Compatible_Time-Sharing_System) (CTSS) at MIT—one of the earliest operating systems to offer password authentication. While passwords were simple and easy to implement, their security weaknesses soon became apparent, especially as systems moved online. + +### 2. Session-Based Authentication (1990s) + +With the rise of dynamic websites in the 1990s, session-based authentication became common. When users log in, servers generate a unique session ID, typically stored in browser cookies ([MDN Web Docs](https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies)). While effective for traditional web applications, session-based methods struggled with scalability and weren’t ideal for mobile or API-driven systems. + +### 3. Token-Based Authentication (Early 2010s) + +The growth of mobile apps, single-page applications (SPAs), and cloud-based services highlighted the need for stateless and scalable authentication. This led to the popularity of OAuth 2.0, standardized by the IETF in 2012 (RFC 6749), and JSON Web Tokens (JWTs), which allowed clients to carry identity information securely without relying on session storage. + +### 4. Multi-Factor Authentication (MFA) Adoption (Mid-2010s) + +As cyberattacks and credential theft grew more prevalent, MFA moved from optional to essential. The [NIST Digital Identity Guidelines](https://pages.nist.gov/800-63-3/sp800-63b.html) (SP 800-63B), released in 2017, emphasized MFA as a best practice for modern authentication. MFA enhances security by combining multiple identity proofs, such as something you know, have, or are. + +### 5. Adaptive and Passwordless Authentication (Late 2010s–Present) + +To balance security with user experience, organizations began adopting adaptive authentication, which evaluates login context: like location, device, or behavior—to apply the right level of verification. + +Simultaneously, passwordless authentication gained traction, driven by innovations like Microsoft’s 2019 push toward eliminating passwords. These approaches aim to reduce friction while maintaining robust protection. + +[![Loginradius resource named a complete guide to website authentication with a free download button.](website-auth.webp)](https://www.loginradius.com/resource/guide/secure-website-authentication) + +## What are the Different Types of Authentication Factors? + +Authentication has evolved far beyond the simple password. As digital threats grow more sophisticated, relying on a single method of verification just isn’t enough. + +That’s why modern systems turn to a multi-layered approach built on four key types of authentication factors, each offering a unique layer of protection: + +### Knowledge Factors – Something You Know + +Knowledge factors, the most commonly used type of authentication, involve users proving their identity by entering information only they’re supposed to know. While simple and easy to implement, they are also the most vulnerable—passwords can be guessed, stolen, or leaked, hence the need for additional security measures. + +To boost security, knowledge factors should be combined with other types—this is where MFA becomes essential. For example, passwords, PINs, answers to security questions, etc. + +![A person trying to authenticate using a password.](authenticate-using-password.webp) + +### Possession Factors – Something You Have + +These methods rely on a physical item that the user owns. That could be a mobile device receiving a one-time code or a hardware token used to verify access. Even if someone knows your password, they still need your device to complete the login. + +Possession-based authentication is a key pillar of MFA and is widely adopted across both personal and enterprise systems. Examples include smartphones, OTP tokens, smart cards, and authenticator apps, including Google authenticator codes, etc. + +### Inherence Factors – Something You Are + +These factors use a person’s unique biological traits to confirm identity. Biometric methods offer high security and a frictionless user experience since there’s nothing to remember or carry for identity authentication. They’re common in smartphones, banking apps, and high-security environments. + +However, because biometric data is permanent and unique, businesses must ensure this data is stored and handled securely—for example, fingerprints, facial recognition, and iris scans. + +### Behavioral Factors – Something You Do + +Behavioral authentication is all about how a user interacts with their device. These subtle patterns—like typing rhythm, mouse movement, or swipe gestures—are difficult to mimic and can help detect fraud in real time. + +Often used in adaptive authentication, behavioral factors allow the system to respond dynamically based on user behavior, adding a hidden yet powerful layer of security without disrupting the user experience. + +Combining behavioral signals with other user authentication methods strengthens identity authentication and reduces the risk of unauthorized access. + +Want to see how adaptive authentication uses these signals to defend against evolving digital threats? Download our eBook on navigating the digital apocalypse with smarter authentication: + +[![Loginradius resource named adaptive authentication in the age of digital apocalypse with a free download button.](adaptive-mfa.webp)](https://www.loginradius.com/resource/ebook/adaptive-authentication-digital-apocalypse/) + +## Types of Authentication + +As digital security grows more advanced, so do the methods of verifying users. Choosing the right type of authentication depends on your security needs and the user experience you want to provide. Here's a closer look: + +### Single-Factor Authentication (SFA) + +Single-factor authentication is the most basic form—usually just a password or PIN. It’s simple and fast, but not very secure. It might work for low-risk accounts but isn't ideal for anything sensitive. + +### Two-Factor Authentication (2FA) + +2FA is an authentication type that adds an extra layer by combining two different authentication factors. Typically, it’s something you know (password) and something you have (OTP on a phone). Even if someone gets your password, they can’t log in without the second factor. + +Need a quick comparison between single-factor authentication, two factor authentication, and multi factor authentication?[ Read this blog. ](https://www.loginradius.com/blog/identity/1fa-vs-2fa-vs-mfa/) + +### OTP Authentication + +[One-time passwords (OTPs)](https://www.loginradius.com/blog/identity/what-is-OTP-authentication) are temporary codes sent to users via SMS, email, or an app. They’re valid for a short period and can’t be reused. OTPs are common in 2FA setups and are great for preventing password reuse or simple phishing attacks. + +### Multi-Factor Authentication (MFA) + +MFA requires two or more factors before granting access—like a password, a fingerprint, and a token. It’s one of the most secure ways to authenticate users and is now considered a best practice for businesses. + +![Visual representation of LoginRadius’ adaptive authentication verifying user access based on time, device, IP address, and geographic location.](how-mfa-works.webp) + +Explore more about [what is Multi-Factor Authentication](https://www.loginradius.com/blog/identity/what-is-multi-factor-authentication/) here. + +### Adaptive Authentication (Risk-Based Authentication) + +[Adaptive authentication](https://www.loginradius.com/blog/engineering/what-is-adaptive-authentication/#:~:text=Adaptive%20Authentication%20intelligently%20identifies%20malicious,Adaptive%20Authentication%20Risk%2Dbased%20Authentication) is a smart authentication that enables robust security in high-risk scenarios. It adapts based on context—location, device, behavior, etc. If something seems off (e.g., a login from a new country or new device), it asks for more verification. It balances security and convenience. + +![Illustration depicting adaptive multi-factor authentication with device, location, IP, and time-based access controls.](adaptive-multi-factor-authentication.webp) + +Learn more about [MFA vs RBA](https://www.loginradius.com/blog/identity/mfa-vs-rba/) to make the right decision for your diverse business needs. + +### Passwordless Authentication + +[Passwordless authentication](https://www.loginradius.com/blog/identity/what-is-passwordless-login/) ensures that users need not remember complex passwords; instead, they authenticate via biometrics, email magic links, or push notifications. It’s secure, reduces friction, and prevents password-related attacks. + +### Token-Based Authentication + +With [token authentication,](https://www.loginradius.com/blog/identity/what-is-token-authentication) users log in once and receive a secure token (like a JWT). This token lets them make future requests without entering credentials again. It’s efficient and popular in APIs and web apps. + +### Biometric Authentication + +**Biometric authentication** verifies a user’s identity using physical traits like fingerprints, facial recognition, or iris scans. If you’ve ever wondered what type of authentication is biometrics, it falls under inherence factors—something you are. It’s a highly secure and user-friendly method, especially popular in mobile and high-security environments. + +### Push Notification Authentication + +[Push notification authentication](https://www.loginradius.com/blog/identity/push-notification-authentication/) is a modern, fast, and secure authentication method. It works by sending a push notification to a registered device after a login attempt. The user taps approve or deny on their screen—simple, fast, and hard for attackers to spoof. + +![Screenshot of a push-notification multi-factor authentication prompt verifying email, browser, location, and time details through loginradius CIAM.](push-notification-mfa.webp) + +### Voice Authentication + +Voice authentication uses a user's unique vocal patterns as a biometric identifier by having them speak a specific phrase. It's especially useful in call centers and hands-free scenarios where typing passwords isn’t feasible or secure. + +Each method has its strengths. Combining them—especially with [MFA](https://www.loginradius.com/platforms/multi-factor-authentication)—offers the strongest protection. + +## Machine Authentication vs User Authentication + +In the modern digital landscape, where smart devices and apps continuously surround us, authentication isn’t just limited to humans. + +Machines and smart applications also need to communicate with each other, and for that, they need to authenticate themselves first. This machine-to-machine communication should be secure and reliable, for which the crucial role of [machine-to-machine authentication(M2M)](https://www.loginradius.com/products/machine-to-machine) comes into play. + +Let’s understand the difference between user authentication and machine authentication: + +### What is User Authentication + +User authentication confirms a real person using credentials like passwords, biometrics, or MFA. It’s about giving the right humans access to systems and data. For example: A user trying to sign in to their banking portal and requiring second factor authentication through an OTP on phone/email. + +### What is Machine Authentication + +Machine authentication is used for apps, APIs, or services. Machines prove their identity using API keys, tokens, or digital certificates. For instance, a mobile app can access backend services using OAuth 2.0 credentials. This is critical in automated systems like cloud, IoT, and microservices. + +![Diagram illustrating JWT access token flow using Client Credentials Grant between client applications, servers, and LoginRadius Authorization Server.](jwt-access-token.webp) + +## Authentication vs Authorization: What's the Difference? + +While authentication and authorization may sound similar, they do very different things. Here’s how: + +* **Authentication:** Verifies *who* you are—say, via credentials. + +* **Authorization:** Determines *what* you can access once verified. + +Let’s understand this with a real-life example: You sign into a work dashboard (authentication). If you’re in HR, you see salary info. If you’re in IT, you manage infrastructure (authorization). + +To better understand authentication vs authorization, you can [check out this detailed blog.](https://www.loginradius.com/blog/identity/authentication-vs-authorization-infographic/) + +## Authentication Use Cases + +When we talk about authentication use cases, the list is endless for individuals and businesses. Authentication is foundational to secure digital systems. Here are three ways it plays a vital role: + +### Access Control + +Ensures only approved users get into specific systems or data. Authentication supports access strategies like RBAC (role-based) and ABAC (attribute-based). + +Check out our [case study](https://www.loginradius.com/resource/case-study-page-safebridge/) to see how SafeBridge, a leading e-learning and certification platform, successfully implemented RBAC. + +Without proper authentication, these boundaries become weak points. + +### Regulatory Compliance + +Laws like GDPR, HIPAA, and PCI DSS require strong identity controls. MFA, secure password rules, encryption, and access logs help meet these demands. + +Authentication also enables traceability—tying every action back to a verified user. This helps with audits and significantly reduces breach risks and legal exposure. + +[![Loginradius resource named LoginRadius and GDPR compliance with a free download button.](gdpr-compliance.webp)](https://www.loginradius.com/resource/ebook/loginradius-gdpr-compliance/) + +### AI Security + +AI systems are handling more sensitive data than ever. Authentication ensures that only trusted users or applications interact with AI models or dashboards. + +Behavioral biometrics and adaptive authentication also help detect unusual access patterns—protecting against misuse before it escalates. + +In the AI age, securing access is critical. + +## Authentication Protocols + +* **Password Authentication Protocol (PAP)** + +Password authentication protocol is an early and insecure protocol that transmits passwords in plain text. It's outdated and should be avoided in modern systems. + +* **Challenge Handshake Authentication Protocol (CHAP)** + +Improves on PAP by using a challenge-response mechanism to verify identity without sending passwords directly. + +* **OpenID Connect (OIDC)** + +[OpenID Connect (OIDC)](https://www.loginradius.com/docs/single-sign-on/federated-sso/openid-connect/overview/?q=open+id+) is a modern protocol built on OAuth 2.0, OIDC enables secure login and single sign-on (SSO) for web and mobile applications. + +* **Lightweight Directory Access Protocol (LDAP)** + +[LDAP](https://www.loginradius.com/blog/identity/what-is-ldap-authentication-and-how-it-works/) is widely used in enterprise networks, LDAP allows systems to access and manage directory information like usernames and credentials. + +* **Security Assertion Markup Language (SAML)** + +[SAML](https://www.loginradius.com/blog/identity/saml-sso/) authentication is an XML-based protocol that facilitates SSO by securely exchanging authentication data between identity and service providers. + +* **Extensible Authentication Protocol (EAP)** +Flexible and extensible, EAP supports various authentication methods and is often used in wireless networks and VPNs. + +* **JSON Web Token (JWT)** +[JWT ](https://www.loginradius.com/blog/engineering/jwt/)is a compact, self-contained token format used to securely transmit identity information—ideal for APIs, SPAs, and microservices. + +## API Authentication Methods + +APIs also need secure access control. Here are some standard methods: + +* **Basic HTTP Authentication:** Username and password are sent with each request. Only safe over HTTPS. + +* **API Keys:** Unique keys passed in requests. Often used for service-to-service communication. + +* **OAuth 2.0:** Allows apps to access user resources securely without sharing login credentials. + +To get started with API authentication by LoginRadius, you can[ check our detailed developer docs.](https://www.loginradius.com/docs/api/v2/customer-identity-api/?q=api+authentication) + +## Best Practices for Authentication Security + +Building authentication that’s both secure and user-friendly isn’t just a checkbox—it’s a competitive advantage. Whether you're securing customer accounts or internal systems, the right approach helps reduce risk without frustrating users. Here are key best practices to get it right: + +### Enable Multi Factor Authentication (MFA) + +MFA is one of the simplest yet most effective ways to strengthen your security posture. By requiring users to provide two or more verification factors—like a password and a one-time code—you dramatically reduce the chances of unauthorized access, even if one factor is compromised. It’s no longer optional; it’s expected. + +Quick guide and [implementation docs for MFA](https://www.loginradius.com/docs/security/customer-security/multi-factor-authentication/overview/?q=multi). + +### Go Passwordless Where Possible + +Let’s face it—passwords are a weak link. They’re often reused, easily guessed, and vulnerable to phishing. [Passwordless user authentication](https://www.loginradius.com/products/passwordless) methods like biometrics, email magic links, or push notifications offer a more secure and seamless experience. Plus, users love not having to remember yet another complex password. + +Quick guide and[ implementation docs for passwordless](https://www.loginradius.com/docs/authentication/passwordless/passwordless-login/?q=passwordless+) authentication. + +### Use Adaptive MFA for Context-Aware Security + +Why challenge every login when you can be smarter about it? Adaptive MFA analyzes factors like location, device, behavior, and login time to determine risk. If something seems unusual, it prompts for additional verification—if not, it lets the user through. It’s a great way to balance security and convenience. + +Quick guide and [implementation docs for adaptive MFA.](https://www.loginradius.com/docs/security/customer-security/risk-based-auth/?q=adaptive+mfa) + +### Set Up Single Sign-On (SSO) + +Single Sign-On (SSO) lets users access multiple apps and services with just one set of credentials. Not only does this reduce password fatigue, but it also minimizes the number of attack surfaces. It streamlines access through a central authentication service while giving IT teams centralized control over authentication across platforms. + +Quick guide and [implementation docs for SSO](https://www.loginradius.com/docs/single-sign-on/overview/?q=single+sign). + +### Implement Role-Based Access Control (RBAC) + +Not every user needs access to everything. Role-based access control helps you assign permissions based on roles, ensuring people only see what they need to do their jobs. It limits overexposure of sensitive data, simplifies access management, and reduces the risk of insider threats. + +Quick guide and [implementation docs for RBAC.](https://www.loginradius.com/docs/user-management/roles-and-permissions/?q=role+based) ## Conclusion -In this article we have talked about the basics of authentication and how it is used. We have also covered [how authentication works](https://www.loginradius.com/blog/engineering/webauthn-authentication-application/) and what are the benefits to the organizations. +Authentication isn’t just a technical step—it’s the foundation of digital trust. As threats grow more sophisticated, businesses must adopt authentication methods that are secure, scalable, and user-friendly. + +Whether it’s MFA, SSO, passwordless, or adaptive options, LoginRadius provides a modern CIAM authentication portal to secure every digital interaction. + +Ready to upgrade your authentication strategy? +[Connect with LoginRadius](https://www.loginradius.com/contact-us) to protect your business and users with confidence. + +## FAQs + +### 1. What happens first, authorization or authentication? + +**A:** Authentication comes first to verify identity. Authorization follows to decide access rights. + +### 2. What types of authentication solutions are available? + +**A:** Single-factor, multi factor, passwordless, biometric, token-based, and adaptive authentication. + +### 3. What are examples of three-factor authentication? + +**A:** A password (knowledge), an OTP on your phone (possession), and a fingerprint (inherence). + +### 4. What’s authentication’s role in cybersecurity? + +**A:** It ensures only verified users access systems, reducing breaches and unauthorized actions. + +### 5. Are passwordless logins more secure? -Cheers! +**A:** They remove weak password dependencies and block phishing or credential theft. -[![book-a-demo-loginradius](../../assets/book-a-demo-loginradius.png)](https://www.loginradius.com/book-a-demo/) \ No newline at end of file +[![book-a-demo-loginradius](../../assets/book-a-demo-loginradius.png)](https://www.loginradius.com/contact-us) \ No newline at end of file diff --git a/content/identity/what-is-authentication/jwt-access-token.webp b/content/identity/what-is-authentication/jwt-access-token.webp new file mode 100644 index 000000000..15d53f23a Binary files /dev/null and b/content/identity/what-is-authentication/jwt-access-token.webp differ diff --git a/content/identity/what-is-authentication/mobile-data-security.webp b/content/identity/what-is-authentication/mobile-data-security.webp new file mode 100644 index 000000000..2532a6373 Binary files /dev/null and b/content/identity/what-is-authentication/mobile-data-security.webp differ diff --git a/content/identity/what-is-authentication/push-notification-mfa.webp b/content/identity/what-is-authentication/push-notification-mfa.webp new file mode 100644 index 000000000..0f8aae9be Binary files /dev/null and b/content/identity/what-is-authentication/push-notification-mfa.webp differ diff --git a/content/identity/what-is-authentication/securing-user-auth.webp b/content/identity/what-is-authentication/securing-user-auth.webp new file mode 100644 index 000000000..9db8f6844 Binary files /dev/null and b/content/identity/what-is-authentication/securing-user-auth.webp differ diff --git a/content/identity/what-is-authentication/website-auth.webp b/content/identity/what-is-authentication/website-auth.webp new file mode 100644 index 000000000..db1809162 Binary files /dev/null and b/content/identity/what-is-authentication/website-auth.webp differ diff --git a/content/identity/what-is-authentication/what-is-authentication.webp b/content/identity/what-is-authentication/what-is-authentication.webp new file mode 100644 index 000000000..a35d9fa54 Binary files /dev/null and b/content/identity/what-is-authentication/what-is-authentication.webp differ