Add account credentials for an alternative login provider such as Google.
Alternative logins allow users to login to an application through a different account; such as a Google, Facebook, LinkedIn, or Twitter account. When an Add Alternative Login to Current User action is defined, in addition to an authentication provider a list is also required. If you add a login for a different provider it this list control will be updated to show the change.
Configuring the Action
- Select Named Authentication Provider
The provider to use for login authentication. Providers are defined in the Web Project Properties. See Named Providers.
- List Control with Alternative Logins
An optional list control that contains the alternative authentication records. This control will refresh if a login is added.
For more on how to implement Alternative Login, watch the videos below. Skip to "Part 4 - Adding to the UX Component" for information about the Add Alternative Login to Current User action.
Alternative Logins - Logging into an Application using Google, Facebook, LinkedIn, or Twitter
When the Alpha Anywhere Security Framework is turned on, you can require a users to log into an application before they can use it. The user must provide their user id and password for their account in order to log into the application.
You can provide an option for users to log into your app using credentials from a social network, such as Facebook or Google. These alternative login options can be used to authorize an existing user as well as register new users in the Alpha Anywhere Security Framework
In this video series, we explain how to setup and configure an application to use alternative login to verify users have authorization to use your app.
- Part 1 - Provider Projects
- Part 2 - Creating Named Providers
- Part 3 - Configuring Web Security
- Part 4 - Adding to the UX Component
- Part 5 - Testing Alternative Login
UX Component Only