Ask AI
Skip to main content

Login with idp

Function: Login with Identity Provider​

This action allows your application's users to sign in using an external login service, also known as an Identity Provider (IDP). Instead of managing separate usernames and passwords within your application, users can leverage their existing accounts from services like Google, Microsoft, or your company's internal login system. This simplifies the login process for users and enhances security by delegating authentication to trusted providers.

Input​

  • Identity provider (Text): The specific name of the external login service you want to use for authentication. This name must match how the Identity Provider has been configured and set up within your NoCode-X platform. This is a required input.

Output​

This action does not produce a direct output value. Its primary function is to initiate a login process, which typically involves redirecting the user to the chosen Identity Provider's login page.

Execution Flow​

Real-Life Examples​

Example 1: Logging in with Google​

Imagine you have an application where users can sign in using their Google accounts.

  • Inputs:
    • Identity provider: "Google"
  • Result: The application redirects the user to Google's login page. After successfully authenticating with Google, the user is automatically logged into your application.

Example 2: Logging in with a Corporate Azure AD​

Your company uses Azure Active Directory (Azure AD) for employee authentication, and you want your internal application to use this system.

  • Inputs:
    • Identity provider: "Azure AD"
  • Result: The application initiates a login flow with your company's Azure Active Directory. Employees can then use their corporate credentials to securely access the application.

Example 3: Offering Multiple Login Options​

You want to provide users with a choice between logging in with Google or a custom enterprise login system. You might have a button for each.

  • Inputs:
    • Identity provider: "Enterprise SSO" (assuming this is the configured name for your custom system)
  • Result: The application attempts to log the user in using the "Enterprise SSO" identity provider, directing them to the appropriate login portal.