Login Providers Configuration

Configure social authentication providers and external login options

Login Providers Overview

Login Providers enable users to authenticate using their existing social media and platform accounts. IdentitySuite supports integration with major authentication providers to streamline the user registration and login process.

Supported Login Providers:

Google
Facebook
Microsoft
Twitter (X)

Key Benefits:

  • • Reduces user friction by eliminating the need to create new accounts
  • • Leverages trusted authentication systems for enhanced security
  • • Provides access to user profile information from social platforms
  • • Improves user experience with familiar login interfaces

Provider Configuration

Each login provider requires specific configuration parameters obtained from the respective platform's developer console. These settings establish the connection between IdentitySuite and the external authentication service.

Required Configuration Fields:

Name: Display name for the login provider as it appears in the user interface. This helps users identify which authentication option they want to use.
ClientId: Public identifier for your application as registered with the login provider. This value is used to identify your application during the OAuth authentication flow.
ClientSecret: Private key used to authenticate your application with the login provider. This sensitive value should be kept secure and never exposed in client-side code.

Order Configuration:

Display Order: Numeric value that determines the position of the login provider button in the authentication interface. Lower numbers appear first, allowing you to prioritize the most commonly used providers.
Visual Impact: The order directly affects user experience by positioning preferred login options more prominently in the interface layout.

Provider Status Control:

Enabled:
Provider appears in the login interface and accepts authentication requests
Disabled:
Provider is hidden from users and authentication requests are rejected

Security Features

IdentitySuite includes built-in security features to protect sensitive configuration data, particularly the ClientSecret values that must be kept confidential.

Credential Protection:

Encryption Toggle: The eye icon button next to ClientId and ClientSecret fields allows you to encrypt these sensitive values before they are stored in the configuration file.
Encrypted Storage: When encryption is enabled, the sensitive data is encrypted using IdentitySuite's built-in data protection mechanisms before being written to the configuration file.
Configuration File: Encrypted values are safely stored in the IdentitySuite.[environment].json file without exposing the original sensitive data.
🔐

How Encryption Works:

  • • Click the eye icon to toggle encryption for ClientId and ClientSecret fields
  • • Encrypted values are automatically decrypted when the application starts
  • • Original values remain accessible to IdentitySuite while staying protected in storage
  • • Learn more about IdentitySuite encryption →
💡

Configuration File Management:

Login provider settings are automatically saved to your environment-specific configuration file. Learn more about IdentitySuite configuration files →

Managing Login Providers

IdentitySuite provides a user-friendly interface for adding, configuring, and managing multiple login providers to meet your application's authentication requirements.

Adding New Providers:

Add Provider: Use the "Add a new login provider" section to configure additional authentication options. Simply fill in the provider details and credentials.
Provider Selection: Choose from the supported providers (Google, Facebook, Microsoft, Twitter/X) based on your user base and authentication strategy.

Provider Management Actions:

Enable/Disable: Toggle provider availability without removing configuration
Reorder: Adjust display order to prioritize commonly used providers
Update Credentials: Modify ClientId and ClientSecret as needed
Remove Provider: Delete login providers that are no longer needed
Encryption Control: Protect sensitive credentials with built-in encryption
Configuration Export: Settings are automatically saved to configuration files

User Experience Impact:

  • • Enabled providers appear as clickable buttons on the login page
  • • Provider order determines the visual sequence in the authentication interface
  • • Users can choose their preferred authentication method from the available options
  • • Disabled providers are immediately hidden from the login interface