![\"Flowchart](\"/f29edbf2978577390c7ffa02e9bc4dda/lr-JWT-authentication.webp\")
Ever wondered how apps like Spotify, Netflix, or Slack manage seamless login experiences across devices? Many of them use JWT, or JSON Web Tokens, a compact, stateless method for securely transmitting user identity and session data across services.
\nWith JWT token authentication, identity information is embedded in a signed token, allowing you to maintain user sessions without server-side storage. This approach is highly scalable and ideal for modern architectures like SPAs, mobile apps, and microservices.
\nIn this blog, we’ll walk you through what is JWT, why use it, and how to implement JWT authentication using LoginRadius.
\nYou’ll learn what JWT is, why it’s effective, and how it works in real-world applications. We'll cover both integration methods (IDX and Direct API), generating your signing key, managing sessions, storing the JWT token securely, and applying best practices throughout.
\nWhether you're a developer, product manager, or IAM architect, this guide offers a complete foundation for implementing JWT token authentication into your application stack.
\nJSON Web Token (JWT) is an open standard (RFC 7519) used to transmit information securely between parties as a JSON object. It’s compact, self-contained, and digitally signed, making it a reliable format for authentication and authorization across modern applications.
\nA JWT consists of three parts:
\nExample of a token structure:
\n<base64Header>.<base64Payload>.<signature>
\n
JWT simplifies identity verification, especially when you're building apps that talk to APIs or need to scale without centralized session storage.
\nLoginRadius provides robust support for JWT (JSON Web Token) authentication, which allows for flexible and secure access control across different digital platforms. Whether you're building a fully custom identity flow or using a pre-built interface, the platform supports various integration approaches depending on your architecture.
\nIf you're looking to understand how to implement JWT token authentication effectively, LoginRadius offers two primary implementation models that cater to different levels of customization and control:
\nThe IDX-hosted login approach enables secure, standards-compliant, JWT-based authentication without requiring you to build a custom login interface. This is a strategic option for fast, compliant, and user-friendly deployments.
\n![\"Screenshot](\"/9fb19dd9c88c7916aeebd03ab6e661b7/lr-admin-console.webp\")
{
\n\"access_token\": \"eyJhbGciOiJIUzI1NiIsInR...\",
\n\"expires_in\": 1800
\n}
\nThis integration approach works best for all teams that want effective identity workflows without the complexity of building proprietary login screens, something that is crucial for customer portals, onboarding of mobile applications, and even managing access for business partners.
\nIf you’re building a custom login UI or working in a headless environment, LoginRadius lets you generate and handle JWTs directly through its Authentication APIs. Here’s how you can programmatically perform token authentication using the classic method:
\nSend a POST login request to the LR Authentication URL:
\nPOST /identity/v2/auth/login
\nInclude the user’s credentials (email + password) in the request body.
\n{
\n\"access_token\": \"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...\",
\n\"expires_in\": 3600
\n}
\nWith LoginRadius, it is possible to customize the payload to include user roles and/or any additional metadata. You can set custom JWT claims on the Admin Console.
\nWith this method, you have complete customization over login flows while using LoginRadius to issue signed JWTs for user session management.
\nNOTE- With either method, LoginRadius ensures that JWTs are securely signed, optionally short-lived, and compatible with standard token validation libraries, making integration seamless for everyone.
\nTo get started with JWT implementation, you can read our complete developer documentation.
\n![\"Illustration](\"/15ec02ac98d24a9f1f28e5d0f06b9174/IDX-vs-Direct-API-JWT.webp\")
Session management is how your app keeps track of a user after they log in so they don’t have to prove who they are with every request.
\nIn traditional apps, sessions are stored on the server using session IDs. Every time a request comes in, the server checks that session ID to verify the user.
\nIn modern apps, especially SPAs and APIs, JWTs are used to manage sessions without needing server-side storage; this is called stateless session management. The token itself carries the user’s identity, roles, and expiration details. As long as the token is valid, the user stays logged in.
\nGood session management ensures:
\nUser Logs In
\nClient Stores the Token
\nAccess Token Expiry
\nToken Renewal
\nWhen the user logs out, both the access token and refresh token should be cleared from client storage.
\nHowever, access tokens are stateless and cannot be revoked mid-lifecycle unless:
\nCombining these strategies gives you greater control over token misuse and enables a robust, enterprise-grade logout flow.
\n![\"illustration](\"/e55ae4bbc8ce62e13f03e46e29ebe7cc/api-economy.webp\")
When you implement JWT-based authentication, the client (browser or mobile app) needs a way to store the access token and, optionally, the refresh token after they are issued by the authentication server. This stored token is then attached to every subsequent request to prove the user's identity.
\nChoosing where to store the JWT is a crucial security decision. The most common storage options are:
\nEach option has trade-offs between security, accessibility, and persistence, and the right choice depends on your application's architecture and threat model.
\nAccess Tokens
\nRefresh Tokens
\nJWT authentication with LoginRadius offers a modern, stateless approach to managing sessions across distributed systems. The IDX integration is ideal for rapid deployment, while the Direct API model is best for organizations needing deep customization and integration flexibility.
\nWith robust token signing, refresh capabilities, and centralized control, LoginRadius provides a future-ready foundation for secure, scalable identity architecture. Contact us to know more about JWT authentication and implementation guide.
\nA: JWT authentication securely verifies user identities, enabling stateless session management across web, mobile apps, and microservices without server-side session storage.
\nA: LoginRadius simplifies JWT integration by offering hosted IDX login pages and direct API-based authentication methods, enabling rapid deployment and deep customization.
\nA: Yes, JWT authentication is secure when implemented with best practices like short-lived tokens, secure storage methods, signature validation, and refresh token rotation.
\nA: Yes, LoginRadius allows revocation of JWT refresh tokens explicitly, and supports strategies like short-lived tokens and key rotation to manage token lifecycles securely.
\n","frontmatter":{"date":"April 15, 2025","updated_date":null,"description":"Discover JWT (JSON Web Token) authentication, its advantages, and how to integrate it seamlessly using LoginRadius' hosted IDX and Direct API methods for secure, scalable identity management.","title":"JWT Authentication with LoginRadius: Quick Integration Guide","tags":["JWT","JSON Web Token","Authentication","Authorization"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":0.7782101167315175,"src":"/static/4cedb7829f98208cbc6d5a9aea4e983d/58556/how-to-integrate-jwt.webp","srcSet":"/static/4cedb7829f98208cbc6d5a9aea4e983d/61e93/how-to-integrate-jwt.webp 200w,\n/static/4cedb7829f98208cbc6d5a9aea4e983d/1f5c5/how-to-integrate-jwt.webp 400w,\n/static/4cedb7829f98208cbc6d5a9aea4e983d/58556/how-to-integrate-jwt.webp 800w,\n/static/4cedb7829f98208cbc6d5a9aea4e983d/1cc9f/how-to-integrate-jwt.webp 896w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Kundan Singh","github":null,"avatar":null}}}},{"node":{"excerpt":"Introduction Imagine logging into your bank account, your favorite online store, or even your company dashboard—and all it takes is a…","fields":{"slug":"/identity/what-is-strong-authentication/"},"html":"Imagine logging into your bank account, your favorite online store, or even your company dashboard—and all it takes is a password. Convenient? Yes. Safe? Not anymore!
\nIn a world where cyberattacks are no longer just occasional headlines but daily realities, relying on a password alone is like locking your front door but leaving the key under the mat. That’s where strong authentication steps in—and it’s fast becoming the gold standard for authentication in cyber security.
\nLet’s understand in detail the aspects associated with strong authentication.
\nFirst, you learn about what authentication really means — it's the process of verifying that someone is who they say they are in the digital world. Once you understand that foundation, you’ll see why simply entering a username and password just doesn’t cut it anymore.
\nStrong authentication is more than just a buzzword. It’s a robust, layered approach to verifying a user’s identity by requiring two or more independent credentials from different categories:
\nIt’s designed so that if one factor is compromised, the others are still standing strong—blocking unauthorized access. So yes, strong authentication is required if you’re serious about protecting digital identities.
\nNow, you might be wondering—isn't that just multi-factor authentication? Great question. Let's dive in.
\n![\"Illustration](\"/cf5c8c66eb98045e4e11adff45c288ee/security-personnel-safeguarding-a-laptop.webp\")
Not quite, though they’re often used interchangeably.
\nMulti-factor awuthentication (MFA) means using more than one method of verification. But not all MFAs are strong. If you use a password and then get a code via SMS, that’s technically MFA—but SMS can be intercepted, spoofed, or stolen.
\nTo be considered strong authentication, each factor should be:
\nSo, strong authentication raises the bar, ensuring that security authentication methods are truly airtight.
\nWe’re not just talking about better security. We’re talking about preventing breaches that could cost millions and damage your brand forever.
\nHere’s why strong authentication in cybersecurity is critical:
\nLet’s be honest—authentication in cyber security isn’t just IT’s problem anymore. It’s a brand issue, a revenue issue, and a customer trust issue.
\nLet’s look at strong authentication examples you probably use (or should be using):
\nIn each case, the authentication methods are diverse, secure, and difficult to fake.
\nDifferent businesses need different security authentication methods, depending on their risk profile, industry regulations, and user experience goals. Here are the most common types of strong authentication:
\nWhere it uses your unique physical traits—like a fingerprint, retina scan, or face—to verify identity. It’s widely adopted due to convenience and difficulty to replicate.
\n![\"Illustration](\"/3220d722c73393488eb707a088be54f0/mobile-biometric-authentication.webp\")
These are physical objects like USB keys or access cards that generate time-based codes or store secure certificates. Ideal for high-security industries.
\nThink of getting a pop-up on your phone asking if it's really you logging in. Just add push notification MFA to your apps and you’ve got a double layer of assurance. Here’s how it looks like with the LoginRadius push notification MFA:
\n![\"Illustration](\"/39ffbc6ade2d265f77e9993fbc10b260/push-notification.webp\")
You just need to sign up for LogiRadiusto add push notification MFA into your applications/ website.
\nA bit more technical, PKI uses encrypted keys and digital certificates. Common in email encryption, internal systems, and enterprise-level authentication management.
\nPasskeys are a modern passwordless method that uses cryptographic key pairs, stored securely on your device, for seamless yet strong authentication. They're phishing-resistant and incredibly user-friendly.
\n![\"Illustration](\"/eb26d52af33f4366c6843a6a15e0014b/Passkeys-lr.webp\")
This removes passwords altogether and uses other factors like biometrics, device recognition, or one-time login links. It's gaining popularity for reducing password fatigue and eliminating common password-related risks. Want to learn more about passwordless authentication? Check out this insightful blog.
\nOTP authentication generates codes for one-time use, often sent via SMS or app. While convenient, OTPs are more secure when combined with stronger, independent authentication factors.
\nWant to make strong authentication even smarter? Enter adaptive authentication. This approach adjusts the verification level based on user behavior, device, location, and time.
\nFor instance, if you always log in from New York, but suddenly there’s a login attempt from Moscow, the system will demand extra verification. It’s like your digital bouncer.
\n![\"Illustration](\"/1036b277e890b424b579e4a827ee33a0/adaptive-authentication-factors.webp\")
To quickly add adaptive authentication, you can register on the LoginRadius platform in a couple of minutes. It’s quick, easy, and works flawlessly.
\nStill on the fence? Let’s put it this way—cybersecurity is no longer a \"nice-to-have.\" It’s mission-critical. And when it comes to protecting your systems, customers, and reputation, strong authentication isn’t just a tool—it’s your first and most powerful line of defense.
\nHere’s what’s at stake:
\nStrong authentication also future-proofs your business. As cyber threats evolve, a flexible, multi-layered authentication approach allows you to stay one step ahead. Plus, implementing it now positions your business as a leader in authentication cyber security, showing customers and stakeholders you take privacy and protection seriously.
\nStrong authentication isn’t just an IT upgrade—it’s your brand’s safety net, competitive edge, and trust engine all rolled into one.
\nStrong authentication is a modern security essential that combines two or more independent verification methods—such as biometrics, one-time passwords, or hardware tokens—to verify user identity.
\nIn a time when passwords alone are no longer enough, this layered approach plays a crucial role in blocking unauthorized access, preventing fraud, and building user trust.
\nWhether you're safeguarding financial transactions, securing enterprise systems, or simply aiming for better compliance, strong authentication ensures your digital assets stay protected.
\nWant to understand the basics first? Start with what strong authentication means in cybersecurity.
\nReady to explore the types of layered protection? Here are the types of multi-factor authentication methods you can choose from.
\nTo sum it up, what is strong authentication? It’s a must-have security layer that combines multiple independent, verifiable methods to ensure users are exactly who they say they are.
\nWhether you're handling payments, protecting sensitive data, or simply trying to avoid the next big breach—strong authentication is required. Period.
\nAt LoginRadius, we help businesses implement secure, scalable, strong customer authentication solutions that meet today’s threats without sacrificing user experience. Reach us to know more about our authentication platform.
\nWant to learn how you can modernize your authentication management? Explore our Authentication Solutions
\nA. It’s a method that uses two or more independent factors—like a biometric scan and a secure app—to verify identity. These are often required in financial regulations to reduce fraud.
\nA. This is the process of confirming a person’s identity using unique, hard-to-replicate credentials like fingerprints, digital certificates, or smart cards.
\nA. Adopt strong authentication, limit user privileges, and monitor all access points. Encrypt all data in transit and at rest. Also, update your authentication management regularly.
\nA. Because passwords alone aren’t enough. The benefits of multi factor authentication include reduced risk, compliance with laws, and enhanced user trust.
\n![\"book-a-demo-loginradius\"](\"../../assets/book-a-demo-loginradius.png\")
In today’s hyper-connected world, cyber threats don’t just knock—they break in. From social engineering and deepfakes to threat groups like Scattered Spider, the risks targeting user identities are more advanced than ever. These evolving challenges—explored in our recent breakdown of CISO’s top cybersecurity concerns for 2025—highlight just how critical robust authentication has become.
\nWith remote work, cloud ecosystems, and hybrid infrastructures dominating the digital landscape, the need for strong, adaptive authentication methods has become critical—not optional.
\nAs we’ve stepped into 2025, safeguarding access isn’t just about protection—it’s about building trust, ensuring compliance, and staying resilient in the face of next-gen attacks.
\nIn this blog, we’ll break down what user authentication really means, why it’s essential, the top user authentication methods you need to know, and how to quickly implement them in your apps with LoginRadius.
\nAuthentication or user authentication is the process of verifying the identity of a user attempting to access a system. It ensures that only authorized individuals gain access to sensitive data and resources.
\nTraditionally, this was done using passwords. However, in 2025, user authentication techniques have become much more sophisticated, using a combination of factors such as biometrics, tokens, and behavioral data.
\nModern methods for authentication go beyond the basics (passwords), using a layered approach to defend against evolving threats and ensuring minimal disruption to the user experience.
\nAs cyberattacks grow more advanced, the need for secure authentication methods has never been greater. Breaches caused by weak or stolen credentials are among the most common.
\nStrong authentication methods protect organizations from unauthorized access, data breaches, and reputational harm. They also support compliance with regulations like GDPR and HIPAA.
\nFurthermore, implementing advanced authentication methods increases customer confidence, promotes brand trust, and supports seamless digital experiences.
\nHere are nine proven user authentication methods that every business should consider in 2025:
\nThis method eliminates the need for traditional passwords by using other identifiers such as biometrics, one-touch login, or one-time passcodes (phone/email) sent to trusted devices.
\nPasswordless systems are a part of advanced authentication methods, improving security while reducing friction for users.
\nHere’s how you can configure passwordless authentication in the LoginRadius Dashboard with ease:
\n![\"Illustration](\"/0510e02632193c45d03d78c028f8ac27/passwordless-authentication.webp\")
Multi-Factor Authentication (MFA) is a security process that requires users to verify their identity using two or more independent factors—like a password, a device, or a biometric. It significantly reduces the risk of unauthorized access by adding extra layers of protection beyond just a password.
\nMFA requires users to provide two or more verification factors:
\nThis layered approach combines different types of authentication to reduce the risk of credential compromise. Moreover, businesses these days rely on a more advanced form of MFA i.e. adaptive authentication. Adaptive authentication automatically adjusts the level of security by adding additional authentication factor if anything suspicious related to login is detected (we’ll learn in detail below). Here’s how you can configure MFA in the LoginRadius Dashboard with ease:
\n![\"Illustration](\"/7e7f4c26a2cddf0c5657bf84bbe45524/multi-factor-authentication.webp\")
Using unique biological traits like fingerprints, facial recognition, or retina scans, biometrics are a reliable form of identity verification.
\nBiometric-based authentication mechanisms are harder to replicate and ideal for mobile apps and enterprise environments alike.
\nTo quickly configure biometric authentication, you can read our insightful developer docs here.
\nTokens, either hardware or software-based, provide time-sensitive codes for login. They are used widely in financial services and internal enterprise tools.
\nThese tokens strengthen methods for authentication by introducing an external factor that attackers cannot easily access.
\nHere’s how to configure token-based authentication for your applications.
\nSocial login allows users to sign in using credentials from platforms like Google, Apple, LinkedIn, or other social channels. It simplifies access and reduces password fatigue.
\nThis method leverages existing network authentication systems from trusted providers, creating a secure and fast user experience. For instance, a user can sign in or sign up for a platform just by using their existing Facebook or Google account.
\nHere’s how you can configure Social Login in the LoginRadius Dashboard with ease:
\n![\"Illustration](\"/274e8a2b67d7d022125ea50b077ffa4d/social-providers.webp\")
Adaptive authentication evaluates login context—such as location, device, and user behavior—to dynamically apply stricter verification when needed.
\nThis smart approach is gaining traction as one of the most effective secure authentication methods for enterprises.
\nIf you wish to add risk-based authentication to your application, here’s our developer docs offering complete implementation guide.
\nDigital certificates are used to verify identity, particularly for device and network authentication. This method is widely adopted in enterprise VPNs and machine-to-machine communications.
\nIt supports various authentication methods in zero trust environments, providing encrypted and scalable protection.
\nHere’s a quick guide for implementing certificate-based authentication for your applications.
\nPasskeys are cryptographic keys that replace traditional passwords. Stored securely on a device, passkeys use biometric or device-based verification to authenticate users across devices and platforms.
\nAs a form of advanced authentication methods, passkeys eliminate phishing risks and simplify login experiences, making them a future-proof option for modern applications.
\nHere’s how you can configure passkey authentication in the LoginRadius dashboard with ease:
\n![\"Illustration](\"/39e9dfe839cefc8df7f598b66f63a893/passkeys-configuration.webp\")
Push-notification MFA sends a prompt to a registered device asking the user to approve or deny the login attempt. It provides a quicker and more secure alternative to SMS-based one-time passcodes.
\nThis method strengthens secure authentication methods by reducing the reliance on manually entered codes and enhancing protection against phishing and social engineering attacks.
\nHere’s how you can configure Push-Notification MFA in the LoginRadius Dashboard with ease:
\n![\"Illustration](\"/7a5c742f19b89820b1cd57e9bd2952eb/push-notification-mfa-configuration.webp\")
Behind these authentication mechanisms are standard protocols that ensure consistency, security, and interoperability. These protocols act as the backbone of any modern authentication system, helping different systems communicate securely and efficiently while protecting user identity data.
\nHere are some of the most widely used protocols in 2025:
\n![\"illustration](\"/dce2d7af3a212b2cf75c6b810d4444e2/api-economy.webp\")
Understanding these protocols helps ensure that your user authentication techniques are both secure and scalable.
\nIn 2025, relying solely on passwords is no longer a viable strategy. Businesses must adopt different types of authentication that align with the evolving threat landscape and user expectations. Whether you're deploying various authentication methods for consumers or employees, the goal is the same: protect access without compromising usability.
\nBy combining multiple authentication methods, leveraging contextual data, and using industry-backed protocols, organizations can offer both convenience and robust protection.
\nNeed expert help implementing modern authentication mechanisms? Contact LoginRadius to secure your platform with the right mix of security and user experience.
\nA. Password-based login remains the most widely used form, although it is being rapidly replaced by advanced authentication methods like MFA and biometrics for improved security.
\nA. Authentication verifies identity, while authorization determines what a user can do after logging in. In short: authentication asks \"Who are you?\", authorization asks \"What can you access?\"
\nA. Users are authenticated to the network through network authentication protocols such as RADIUS, LDAP, and certificate-based systems. These systems ensure secure access control.
\nA. Servers authenticate by verifying credentials through established authentication mechanisms like digital certificates or token-based systems. This process ensures secure communication and user validation.
\nA. The process that authenticates clients to a network typically involves validating credentials using protocols like RADIUS or EAP. This ensures that only authorized users can connect securely.
\n![\"book-a-demo-loginradius\"](\"/8fce571f703a5970dbb1359a2fe0e51a/book-a-demo-loginradius.webp\")
In a world where cyber threats like data breaches and identity theft are making headlines almost daily, securing digital systems isn’t just important — it’s essential. That’s where two commonly confused terms come in: authentication and authorization. You’ve probably heard them used together (or even interchangeably), but they serve very different purposes.
\nWhether you're building secure apps, managing access for a team, or simply curious about how systems stay protected, understanding the difference between authentication and authorization is key.
\nIn this blog, we’ll unpack both concepts with relatable examples and clear insights — so you can confidently grasp how each one keeps your data and users safe.
\nAuthentication is the process of verifying who a user is. It answers the question: Are you really who you say you are?
\nFor authentication, users typically provide credentials — such as a username and password, biometric data, or a one-time code — to prove their identity. It acts like a digital passport that validates a person before letting them into a system.
\nImagine you walk into a secured office building. At the entrance, a security guard checks your ID. If it matches the employee database, you’re allowed in. That’s authentication.
\nIn technical aspects, imagine a user logs into an online banking app with a password and receives a 2FA code on their phone. Only after both credentials are verified is the user granted access. This is a prime example of authentication in cyber security.
\n![\"Illustration](\"/ee797716491ac0075887c9b8ecb04e5b/user-authentication-flow.webp\")
The core goal of authentication is to ensure that only verified users can access a system. It prevents impersonation, data theft, and breaches by validating user identities before granting entry.
\nIn today’s digital landscape, where everything from cloud apps to enterprise databases is remotely accessible, robust authentication methods — like biometrics, OTPs, and social logins — are critical for security.
\nAuthentication lays the foundation. Without it, systems wouldn’t know who they are dealing with — making any additional security effort meaningless.
\nAuthorization, on the other hand, determines what an authenticated user is allowed to do. It answers: Do you have permission to access this resource or perform this action?
\nIf authentication is the security guard verifying your ID, authorization is the list showing what rooms or data you're allowed to access.
\nIn simple terms, authorization in cybersecurity is about assigning privileges and access levels to different users based on their role, location, or behavior.
\nThere are various ways to authorize users, depending on the system’s needs. Here are some of the most common:
\nIn role-based access control, users are granted permissions based on roles (admin, editor, viewer). For example, in the LoginRadius console below, the “Admin” has permission to broadcast, download, edit, and read. On the other hand, the “Customer” is only authorized to download and read.
\n![\"Image](\"/5c73289ef2a5b462569dd964b782d2f9/roles-and-permissions-settings.webp\")
Explore how Role-Based Access Control (RBAC) simplifies permissions and strengthens security.\nIn a nutshell, RBAC simplifies access management by assigning permissions based on user roles, such as admin, editor, or viewer, rather than handling access at the individual level.
\nIn a B2C context, this often means differentiating capabilities between everyday users and internal staff. For instance, a streaming platform might allow viewers to consume content, while admins manage uploads and settings.
\nIn B2B scenarios, this concept scales to entire organizations. For example, a retail company which collaborates with suppliers, franchisees, and distributors, requires precise control over who can access what across partner ecosystems.
\nOur Partner IAM feature enables role-based permissions at the organization level, such as Partner Admin or Franchise Manager with access defined down to specific resources or workflows.
\nDiscover how LoginRadius Partner IAM enables precise, organization-level RBAC tailored for complex B2B environments.
\nAttribute-based access ensures that access is granted based on a combination of user attributes such as department, role, location, time of day, or device type.
\nFor example, an employee from the finance department can access payroll data only during working hours and only when using a company-issued device—ensuring granular and context-aware security controls.
\nYou can read our RBAC vs ABAC guidefor a detailed comparison between RBAC and ABAC to ensure you make the right decision that meets your business requirements.
\nJWT (JSON Web Token) authorization is a widely used method for securely transmitting user data between parties—particularly in modern web applications and services. It's especially popular in systems that use stateless authentication, such as RESTful APIs. For instance, after a user logs in, the server issues a JWT that the client includes in subsequent requests to authenticate without needing to re-enter credentials.
\nIf you’d like to dive deeper into how JWTs work and when to use them, check out our full guide on JWT authorization best practices.
\nOAuth 2.0 is a widely adopted protocol for delegating access without exposing user credentials. For example, when you log into Spotify using your Google account, Google handles the authentication, and Spotify receives limited, authorized access to your basic profile—without ever seeing your Google password. This secure delegation is ideal for third-party integrations and API-based systems.
\nTo understand how OAuth 2.0 works, its core flows, and when to use it, check out our in-depth breakdown on OAuth 2.0 and its role in modern identity management.
\nThe aforementioned types show the depth of authorization in cybersecurity, shaping how users interact with systems securely.
\nTo put it plainly, authentication and authorization are two sides of the same coin — often paired but serving different purposes.
\nLet’s go back to the real world: You check into a hotel (authentication), but your key card only grants you access to your room and the gym — not the penthouse suite (authorization).
\n| Feature\n | \nAuthentication\n | \nAuthorization\n | \n
| Definition\n | \nVerifies identity\n | \nDetermines access rights\n | \n
| Function\n | \n\"Who are you?\"\n | \n\"What are you allowed to do?\"\n | \n
| Process\n | \nDone before authorization\n | \nDone after authentication\n | \n
| Data\n | \nRequires login credentials\n | \nRequires permission policies\n | \n
| Visibility to user\n | \nVisible (e.g., login form)\n | \nOften invisible to the user\n | \n
| Use case\n | \nLogin portals, biometric scans\n | \nAccessing internal dashboards or APIs\n | \n
This comparison helps answer the question: How is authentication different from authorization? If you need a more detailed comparison, read this insightful blog.
\nWhen we take a closer look at auth vs authorization, it's evident that both processes serve different purposes and rely on separate sets of criteria to function effectively. Understanding these underlying components helps demystify how modern systems maintain security without compromising user experience.
\nAuthentication is all about identity verification — confirming that a user is who they claim to be. This is typically done through one or more of the following factors:
\nThese layers form the foundation of secure access. For example, logging into your online banking account may require both your password (something you know) and a fingerprint scan (something you are), especially when sensitive transactions are involved.
\nAuthorization, on the other hand, determines what that authenticated user is allowed to do once access has been granted. It sets boundaries and defines permissions based on rules, roles, or policies. Common types of access include:
\nBoth authentication and authorization are vital to protecting sensitive data and ensuring users only have access to the resources they genuinely need.
\n![\"Illustration](\"/e018640575733adb330d8e33bc42d3ed/securing-user-auth.webp\")
Authentication always comes before authorization. This sequence is non-negotiable in cybersecurity and access control. Why? Because a system must first verify who the user is before it can determine what the user is allowed to do.
\nThink of it as meeting someone at your front door. You wouldn’t ask them which rooms they’d like to enter before confirming they’re a trusted friend or family member. Similarly, in digital systems, authentication validates identity, and only then can authorization define access levels.
\nHere’s a breakdown to illustrate this better:
\nThe system checks the user’s credentials — such as a username and password, fingerprint, or OTP — to confirm their identity. During this step, encryption protocols like TLS are typically used to protect credential data as it travels between the client and server, ensuring it can’t be intercepted or tampered with.
\nOnce the identity is verified, the system evaluates what resources that identity has permission to access — like read-only access to a report, admin rights on a dashboard, or restricted areas in a company portal.
\nWhile encryption supports both steps, it becomes even more critical once access is granted. Sensitive data that the authorized user accesses—whether in transit or at rest—should be encrypted to maintain confidentiality and integrity throughout the session.
\nSkipping authentication and jumping straight to authorization would be like giving someone the keys to your office without knowing if they even work there. It's not just risky — it's a security failure waiting to happen.
\nThis foundational flow—authentication first, followed by authorization, and supported by encryption throughout—ensures your digital ecosystem remains secure and logically controlled.
\nLearn more in our guide on Authentication, Authorization, and Encryption.
\nIn cybersecurity and identity management, knowing the difference between authorization and authentication is foundational. While they’re often mentioned together, they perform distinct — and equally vital — roles in protecting systems.
\nWhether you’re building a secure app, managing employee access, or integrating APIs, always start with authentication and then apply authorization based on roles, policies, or attributes.
\nBy mastering both, you’ll reduce vulnerabilities, improve user experience, and align with best practices in authentication and authorization.
\nNeed help implementing secure authentication and authorization for your applications? Contact LoginRadius to get expert guidance today.
\nA. Yes. Being authenticated simply proves identity. A user might log in (authenticated) but lack the right permissions (not authorized) to access certain features or data.
\nA. Common types include:
\nThese are essential for authentication in cyber security.
\nA. Authentication checks identity; authorization checks access rights. It’s the classic authorize vs authenticate debate — where both are needed, but for different reasons.
\nA. Authorization testing ensures users can only access what they are permitted to. It checks for access control vulnerabilities and misconfigurations — key in authorization in cybersecurity.
\nA. Authentication works by matching provided credentials against stored user data. If the credentials match, access is granted. Methods include passwords, biometric scans, OTPs, and digital certificates.
\n
Have you ever logged into a website by clicking “Login with Google” or “Sign in with Facebook,” without entering your password? Or used a web app that keeps you logged in even after closing your browser?
\nThese seamless experiences often rely on JSON Web Tokens (JWTs) — a way to authorize users after they have been authenticated.
\nIn today’s digital landscape, securing user identity and managing access is critical. JWT is a compact and secure method for transmitting claims between parties, typically used after authentication to handle authorization, session management, and secure API access.
\nBut what exactly is a JWT, how does it work, and why is it important? This blog offers a comprehensive explanation.
\nTokens are digital artifacts used in authentication systems to represent user identity. Instead of maintaining session state on the server, modern applications issue tokens to clients. These tokens are sent along with each request to authorize access to protected resources.
\nWhen a user makes an authenticated request, the token is included in the request header. The server verifies the token’s validity—typically by checking its signature and expiration time. If the token is valid, access is granted. This approach supports stateless and scalable systems, compared to traditional session-based models.
\n![\"Illustration](\"/dd1314dc0f7dba888ea4df48ac00ccbe/token-authentication-method.webp\")
A JWT (JSON Web Token) is a compact, self-contained token used to securely transmit claims between parties. JWTs are digitally signed using a secret (with HMAC) or a public/private key pair (with RSA or ECDSA).
\nOne of the main advantages of JWT authentication is that it doesn't require storing session data on the server—making it ideal for distributed applications.
\nThere are two main types of JWT based on how the payload is protected- JWS and JWE. Let’s learn more about them.
\nJWS is a type of JWT where the payload (data) is digitally signed, ensuring integrity and authenticity of the token.
\nUse Case: Verifying that the data has not been tampered with.
\nJWE is a type of JWT where the payload is encrypted, ensuring confidentiality in addition to integrity.
\nUse Case: Protecting personal or confidential information during transit.
\n| Feature\n | \nJWT (General)\n | \nJWS (Signed JWT)\n | \nJWE (Encrypted JWT)\n | \n
| Security Focus\n | \nToken Format\n | \nIntegrity, authenticity\n | \nConfidentiality + integrity\n | \n
| Payload\n | \nNot specified\n | \nBase64URL encoded (readable)\n | \nEncrypted (not readable)\n | \n
| Signature\n | \nOptional\n | \nRequired\n | \nEncrypted along with payload\n | \n
| Encryption\n | \nOptional\n | \nNot encrypted\n | \nFully encrypted\n | \n
| Use Case\n | \nID and Access Tokens\n | \nOAuth 2.0, OpenID Connect\n | \nHighly sensitive information\n | \n
Note: JWT is the umbrella format. JWS and JWE are implementation types. The most commonly used JWTs in web apps are of the JWS type.
\nA JWT is composed of three parts:
\nEach part is Base64URL encoded and separated by a period (.).
\nExample:
\n<Header>.<Payload>.<Signature>
\nThe header typically includes the token type and the signing algorithm being used.
\n{
\n\"alg\": \"HS256\",
\n\"typ\": \"JWT\"
\n}
\nThe payload contains the claims—statements about an entity (usually the user) and additional metadata.
\n{
\n\"iss\": \"https://lrSiteName.hub.loginradius.com/\",
\n\"sub\": \"{uid}\",
\n\"jti\": \"unique string\",
\n\"iat\": 1573849217,
\n\"nbf\": 1573849217,
\n\"exp\": 1573849817,
\n\"Key1\": \"value1\",
\n\"Key2\": \"value2\"
\n}
\nNote: The payload is not encrypted by default, and can be decoded by anyone. Do not include sensitive information unless using an encrypted JWT (JWE).
\nThe signature ensures the token has not been altered. It is created by signing the encoded header and payload using a secret or private key.
\nHMACSHA256(
\nbase64UrlEncode(header) + \".\" +
\nbase64UrlEncode(payload),
\nsecret)
\nThis helps validate the token’s integrity and authenticity.
\nJWT-based authentication typically follows this flow:
\nThe user provides login credentials (e.g., username and password).
\nThe server validates the credentials against its data store.
\nUpon successful login, the server issues a JWT signed with a secret/private key (post authentication).
\nThe client stores the token (e.g., in localStorage, sessionStorage, or a secure cookie).
\nThe client attaches the token to the Authorization header (Bearer <token>) in future authorization/authentication API requests.
\nThe server checks the token's signature, expiry, and validity.
\nIf valid, the user is granted access to protected resources.
\nThis stateless model makes JWT ideal for scalable web and mobile apps.
\nOAuth 2.0 is an industry-standard protocol for authorization. It enables users to grant third-party apps access to their resources without sharing their credentials.
\nWhen integrated with JWT, OAuth 2.0 uses JWTs as access tokens to represent the user's authorization.
\nJWTs are commonly used as OAuth 2.0 access tokens—but not required by the specification. Some providers use opaque tokens instead.
\n
To implement JWT with LoginRadius:
\nSet up a JWT app in your LoginRadius Admin Console. Follow the JWT Admin Console Configuration guide.
\n![\"Illustration](\"/a3ccb47d5a3d66fc01c0eeac6c26328b/jwt-configuration.webp\")
If you are directly implementing your Login forms or already have an access token or want to generate a JWT based on email/username/Phone number or a password, you can leverage the following APIs:
\nAPI Response Example:
\n{
\n\"signature\": \"<JWTresponse>\"
\n}
\nThese tokens can then be used in your client app for authenticated requests.
\nTo implement JWT securely, follow these key practices:
\nPrivate keys or secrets used to sign JWTs must be stored securely.
\nPayload is only base64 encoded—not encrypted. Do not include passwords, PII, or credentials unless using encrypted JWT (JWE).
\nInclude only essential claims in the token to reduce size and exposure.
\nAlways transmit JWTs over HTTPS to prevent man-in-the-middle attacks.
\nUse short exp durations and implement refresh tokens to reduce impact if a token is compromised.
\nUse jti with a blacklist or maintain a revocation strategy for enhanced control.
\nJWTs offer numerous benefits in authentication systems:
\nJWTs are widely adopted in OAuth 2.0, OpenID Connect, and API security implementations.
\nJWT authentication is a robust, efficient, and secure method for protecting web and mobile applications. By understanding its structure, use cases, and best practices, you can confidently implement JWTs in modern authentication systems.
\nLooking to implement JWT in your application? Check out the developer documentation to get started with seamless JWT integration using LoginRadius.
\nA: By default, the expiry time of a JWT is 600 seconds (10 Minutes). It is shown in the form of seconds in the JWT configuration. The expiry time can be set from 1 second to 2592000 seconds (30 days) as per your use case.
\nA: OAuth is an authorization framework, that allows third-party apps to access user data without exposing their credentials.JWT is used at the end of authentication to securely transmit user info (identity and authorization). Use OAuth for delegated access; use JWT for stateless authentication and API authorization (verifying within your own system).
\nA: JWTs mainly come in two types, with one being JSON Web Signature (JWS) and JSON Web Encryption (JWE). In JWS, the token’s content is digitally signed to protect it from tampering during transmission between sender and receiver. While the data is secure from modification, its contents (claims) can still be visible to others.
\n","frontmatter":{"date":"April 07, 2025","updated_date":null,"description":"Understand JSON Web Tokens (JWT), their compact and secure structure, and their critical role in authentication and authorization. Learn how JWT enables stateless sessions, improves scalability, and secures APIs. This guide explores JWT's working principles and best practices for robust security implementation.","title":"Complete Guide to JSON Web Token (JWT) and How It Works","tags":["Oauth","Authorization Code Flow","Authorization","Authentication"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.6528925619834711,"src":"/static/91ea5ae9cba0662d9830e037814a0409/58556/guide-to-jwt.webp","srcSet":"/static/91ea5ae9cba0662d9830e037814a0409/61e93/guide-to-jwt.webp 200w,\n/static/91ea5ae9cba0662d9830e037814a0409/1f5c5/guide-to-jwt.webp 400w,\n/static/91ea5ae9cba0662d9830e037814a0409/58556/guide-to-jwt.webp 800w,\n/static/91ea5ae9cba0662d9830e037814a0409/99238/guide-to-jwt.webp 1200w,\n/static/91ea5ae9cba0662d9830e037814a0409/7c22d/guide-to-jwt.webp 1600w,\n/static/91ea5ae9cba0662d9830e037814a0409/a5bb9/guide-to-jwt.webp 5115w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Kundan Singh","github":null,"avatar":null}}}},{"node":{"excerpt":"Introduction In today's digital world, ensuring secure access to systems and data is more than a technical requirement—it's a business…","fields":{"slug":"/identity/how-to-choose-authentication/"},"html":"In today's digital world, ensuring secure access to systems and data is more than a technical requirement—it's a business necessity.
\nWhether you're managing user access for a mobile app, an enterprise platform, or a customer-facing portal, choosing the right authentication methods plays a critical role in safeguarding sensitive information and delivering seamless user experiences.
\nThis guide breaks down the core authentication types, why they matter, and how to choose the right fit for your needs. It also explains how modern user authentication methods and authentication protocols work together to secure digital ecosystems.
\nUser authentication is the process of verifying that a user is who they claim to be. It's the first line of defense in any digital environment, determining whether someone can access a system, app, or resource.
\nAt its core, user authentication compares credentials entered by the user (like a password or fingerprint) with the stored data to verify identity. If the information matches, access is granted.
\nModern user authentication techniques go far beyond just passwords. Today, businesses use a wide range of authentication mechanisms, including one-time passwords (OTPs), biometrics, smart cards, and more. These methods provide varying levels of security and user convenience.
\nAuthentication also plays a foundational role in digital transformation. As businesses shift to cloud environments and remote work, secure authentication methods help ensure users access the right systems at the right time—without compromising security.
\n![\"Illustration](\"/e2754b85ade243fdc7df6d71037aee2c/facial-recognition.webp\")
Cyber threats are evolving every day, and attackers constantly look for weak points in your digital systems. Without proper user authentication methods, sensitive data, intellectual property, and customer information are at risk.
\nHere are a few reasons why user authentication is so crucial:
\nWithout effective methods for authentication, even the most robust infrastructure can become vulnerable. Authentication supports everything from user onboarding to transaction security.
\nThere are several authentication types used today, ranging from basic to advanced. Each comes with strengths and trade-offs. Here's a breakdown of the most widely used authentication methods:
\nStill the most common method, password authentication involves users entering a secret password. While simple to implement, it's also the least secure if not paired with additional factors.
\nBest practices include enforcing password complexity, expiration policies, and using hashing algorithms for storage. However, as threats like credential stuffing rise, relying solely on passwords is no longer advisable—something we’ve covered in detail in our guide on username and password authentication best practices.
\nMulti factor authentication requires users to provide two or more credentials from different categories:
\nSecure authentication methods like MFA greatly reduce the likelihood of a breach. Organizations often deploy MFA for admin logins, financial transactions, and high-risk user activities.
\nRisk-based or adaptive MFA analyzes the context of each login attempt and adjusts authentication requirements accordingly. It considers factors like user location, device type, IP reputation, and time of access to assess risk in real time.
\nFor example, if a user logs in from an unfamiliar location or device, the system may prompt for additional verification (like a biometric scan or OTP). In contrast, if the login is from a known device in a trusted environment, the user may face fewer authentication steps.
\n![\"LoginRadius’](\"/1036b277e890b424b579e4a827ee33a0/access-decisions-based-on-time.webp\")
This is one of the most intelligent and advanced authentication methods, as it improves both security and user experience by minimizing unnecessary friction while responding dynamically to threats.
\nUses physical characteristics like fingerprints, facial recognition, or retina scans. These user authentication techniques are harder to spoof and offer a seamless experience.
\nAs a form of advanced authentication methods, biometrics are increasingly used in smartphones, airports, banking apps, and secure corporate systems.
\nUsers receive a unique token (often time-sensitive) that must be entered to access the system. Common in banking and high-security environments.
\nToken-based authentication systems, such as JSON Web Tokens (JWT), are widely used in APIs and microservices architecture. They support stateless authentication and secure session management.
\nThis method uses digital certificates issued by a trusted authority to verify identity. It's common in corporate and government environments, particularly in environments requiring machine-to-machine trust.
\nWith SSO, users log in once to access multiple services. It's one of the most user-friendly methods for authentication, often paired with MFA for added security.
\nSSO helps reduce password fatigue, streamlines access across enterprise systems, and enhances productivity.
\nThese are just some of the different types of authentication. Choosing the right one depends on several factors we’ll explore next.
\nPush-notification MFA sends an approval request to a user’s registered mobile device during login. Instead of manually typing a code, the user simply taps “Approve” or “Deny” in an authentication app (such as LoginRadius Authenticator or other TOTP apps with push support).
\n![\"Push-notification](\"/39ffbc6ade2d265f77e9993fbc10b260/Push-notification-authentication.webp\")
This method is highly user-friendly and significantly reduces the risk of phishing compared to traditional SMS or email codes. It’s widely used for its speed, convenience, and strong security, making it a popular option among secure authentication methods for both enterprises and consumer-facing platforms.
\nSocial login allows users to authenticate using their existing accounts from third-party platforms like Google, Facebook, Apple, or LinkedIn. This method simplifies registration and login by eliminating the need to create new credentials.
\nHere’s how to quickly set up social login in the LoginRadius console:
\n![\"Social](\"/274e8a2b67d7d022125ea50b077ffa4d/social-login-configuration.webp\")
From a user experience perspective, social login reduces friction and improves conversion rates. From a security standpoint, it delegates authentication to trusted identity providers that follow strong authentication protocols.
\nIt’s an ideal choice for consumer apps, ecommerce platforms, and services aiming to provide quick access while leveraging existing user authentication methods.
\nEvery organization has different security needs, user bases, and compliance requirements. When evaluating authentication methods, here are key considerations:
\nDoes your platform deal with highly sensitive data or personal information? If so, consider advanced authentication methods like MFA or biometrics. High-risk sectors like healthcare and finance often mandate these protocols.
\nSecurity shouldn’t come at the cost of usability. Opt for authentication mechanisms that are easy to use and don’t create friction for end users. For instance, biometrics offer both security and convenience.
\nA poor authentication experience can lead to user frustration and churn. Always balance security with user-centric design.
\nWill your authentication protocols support a growing user base and adapt to future needs? Ensure the solution is scalable and can integrate with new technologies.
\nOrganizations expanding to new markets or deploying cross-channel platforms should ensure their user authentication methods can scale accordingly.
\nDifferent sectors have different compliance needs. Financial institutions, for example, may need specific security authentication methods to meet regulatory standards like PCI-DSS.
\nCheck for support for industry standards like OAuth 2.0, OpenID Connect, and SAML in your authentication provider.
\n![\"LoginRadius](\"/667a71811d949abce0536b9d235259e2/lr-consent-management-datasheet.webp\")
Your chosen method should work seamlessly with existing infrastructure, third-party services, and CIAM platforms like LoginRadius.
\nModern businesses rely on multiple SaaS tools and backend systems. Interoperability is essential for effective authentication mechanisms.
\nFor higher-risk users (like admins or those accessing financial systems), apply stricter authentication mechanisms. Use contextual authentication to adapt based on location, device, or behavior.
\nUnderstanding your organization’s needs and matching them with the appropriate user authentication methods ensures both protection and performance.
\nSelecting the right authentication methods is no longer optional—it’s fundamental to digital trust, user satisfaction, and organizational resilience. Whether you’re looking at advanced authentication methods like biometrics or standard authentication protocols like passwords and tokens, the goal is to find the right balance of security, usability, and compliance.
\nAs threats become more sophisticated, your choice of authentication mechanisms can make or break your security posture. Make informed decisions that serve both your users and your business.
\nWhen done right, authentication becomes invisible yet secure, empowering users to interact with your brand confidently and securely.
\nNeed help implementing secure and scalable authentication? Contact LoginRadius to speak with an expert.
\nA. Common methods include:
\nA. Biometric user authentication techniques include:
\nA. In network environments, popular security authentication methods include:
\n
Identity is evolving, and developers are at the forefront of this transformation. Every day brings a new learning—adapting to new standards and refining approaches to building secure, seamless experiences.
\nWe’re here to support developers on that journey. We know how important simplicity, efficiency, and well-structured documentation are when working with identity and access management solutions. That’s why we’ve redesigned the LoginRadius website—to be faster, more intuitive, and developer-first in every way.
\nThe goal? Having them spend less time searching and more time building.
\nLoginRadius’ vision is to give developers a product that simplifies identity management so they can focus on building, deploying, and scaling their applications. To enhance this experience, we’ve spent the last few months redesigning our interface— making navigation more intuitive and reassuring that essential resources are easily accessible.
\nHere’s a closer look at what’s new and why it’s important:
\n![\"This](\"/f46881583c7518a93bb24e94c32320de/a-developer-friendly-dark-theme.webp\")
Developers spend long hours working in dark-themed IDEs and terminals, so we’ve designed the LoginRadius experience to be developer-friendly and align with that preference.
\nThe new dark mode reduces eye strain, enhances readability, and provides a seamless transition between a coding environment and our platform. Our new design features a clean, modern aesthetic with a consistent color scheme and Barlow typography, ensuring better readability. High-quality graphics and icons are thoughtfully placed to enhance the content without adding visual clutter.
\nSo, whether you’re navigating our API docs or configuring authentication into your system, our improved interface will make those extended development hours more comfortable and efficient.
\n![\"This](\"/e5358b82be414940f3fb146013845933/capabilities.webp\")
We’ve restructured our website to provide a straightforward breakdown of our customer identity and access management platform capabilities, helping you quickly find what you need:
\nThis structured layout ensures you can quickly understand each capability and how it integrates into your identity ecosystem.
\n![\"This](\"/a8c155c2b6faf3d5f4b4de4e2b14d763/developers-menu.webp\")
We’ve been analyzing developer workflows to identify how you access key resources. That’s why we redesigned our navigation with one goal in mind: to reduce clicks and make essential resources readily available.
\nThe new LoginRadius structure puts APIs, SDKs, and integration guides right at the menu bar under the Developers dropdown so you can get started faster. Our Products, Solutions, and Customer Services are also clearly categorized, helping development teams quickly find the right tools and make informed decisions.
\n![\"This](\"/b2f9a964a2da0ea83e2f8596b833bba7/we-support-your-tech-stack.webp\")
Developers now have a clear view of the tech stack available with LoginRadius, designed to support diverse business needs.
\nOur platform offers pre-built SDKs for Node.js, Python, Java, and more, making CIAM integration seamless across popular programming languages and frameworks.
\nCheck out our revamped LoginRadius website and see how the improved experience makes it easier to build, scale, and secure your applications.
\nDo not forget to explore the improved navigation and API documentation, and get started with our free trial today. We’re excited to see what you’ll build with LoginRadius!
\n","frontmatter":{"date":"February 21, 2025","updated_date":null,"description":"LoginRadius’ vision is to give developers a product that simplifies identity management so they can focus on building, deploying, and scaling their applications. To enhance this experience, we’ve redesigned our website interface, making navigation more intuitive and reassuring that essential resources are easily accessible.","title":"Revamped & Ready: Introducing the New Developer-First LoginRadius Website","tags":["Developer tools","API","Identity Management","User Authentication"],"pinned":true,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.7857142857142858,"src":"/static/80b4e4fbe176a10a327d273504607f32/58556/hero-section.webp","srcSet":"/static/80b4e4fbe176a10a327d273504607f32/61e93/hero-section.webp 200w,\n/static/80b4e4fbe176a10a327d273504607f32/1f5c5/hero-section.webp 400w,\n/static/80b4e4fbe176a10a327d273504607f32/58556/hero-section.webp 800w,\n/static/80b4e4fbe176a10a327d273504607f32/99238/hero-section.webp 1200w,\n/static/80b4e4fbe176a10a327d273504607f32/7c22d/hero-section.webp 1600w,\n/static/80b4e4fbe176a10a327d273504607f32/1258b/hero-section.webp 2732w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Rakesh Soni","github":"oyesoni","avatar":"rakesh-soni.webp"}}}},"pageContext":{"limit":6,"skip":0,"currentPage":1,"type":"///","numPages":164,"pinned":"ee8a4479-3471-53b1-bf62-d0d8dc3faaeb"}},"staticQueryHashes":["1171199041","1384082988","2100481360","23180105","528864852"]}