Ask AI
Skip to main content

Login with idp

Function: Login with IDP​

This function allows your application to initiate a login process for a user through an external identity provider (IDP). Instead of managing user accounts directly within your application, you can leverage existing login systems like Google, Microsoft, or a corporate Single Sign-On (SSO) solution. When this action is triggered, the user will be redirected to the chosen identity provider to authenticate, and upon successful login, they will be granted access to your application.

Input,

  • Identity provider (Text): The specific name of the external identity provider you want to use for login. This name must be configured within your NoCode-X platform to ensure the connection works correctly. For example, "Google", "Okta", or "Azure AD".

Output,

This function does not produce a direct output value. Its primary effect is to redirect the user to the specified identity provider for authentication, and upon successful login, the user gains access to your application.

Execution Flow,

Real-Life Examples,

Here are some examples of how you might use the "Login with IDP" function:

  1. Standard Google Login:

    • Inputs:
      • Identity provider: Google
    • Result: When a user clicks a "Login with Google" button in your app, they are redirected to Google's login page. After successfully logging in with their Google account, they are brought back to your application and granted access.

  2. Corporate Single Sign-On (SSO):

    • Inputs:
      • Identity provider: Okta
    • Result: An employee clicks a "Company Login" button. They are redirected to your company's Okta login portal. Once they authenticate with their corporate credentials, they are automatically logged into your application without needing a separate username and password.

  3. Partner Portal Access:

    • Inputs:
      • Identity provider: PartnerConnect
    • Result: Your business partners need to access a specific section of your application. When they click "Partner Login," they are sent to the "PartnerConnect" authentication system. After verifying their identity there, they gain access to the partner-specific features within your application.