Basics
Must read
Designer help guides
Test panel help guides
Team management
Account management
Reference
Configuring 3rd party authentication
Altogic allows your application users to authenticate to your application using third-party providers such as Google, Facebook, and Twitter. Currently, Altogic supports the following providers for authentication:
- Google
- Facebook
- Twitter
- Discord
- Github
The general flow of authentication using third-party providers stats with configuring the client id and client secret of the provider in Altogic. To create the client id and client secret you need to create an account in the provider's developer/cloud portal, create an application and configure the required permissions for the application and finally create your client id and secret. In addition, you also need to set the callback URI to the URL provided in the authentication settings view. The details about how to get the client id and client secret for each provider is explained in detail in our Third Party Authentication videos on our YouTube channel.
Following the creation of client id, client secret, and configuring the callback URL, you can complete the authentication configuration Altogic by specifying the success and error redirect URLs, which will be called in case of successful or non-successful user authentication respectively. These success and error URLs need to be part of your front-end application.
The final step in having third-party authentication is integration with your front-end application. In the authentication settings panel, Altogic provides the URL that you need to direct your users for authentication in your front-ent application. You just need to use this URL and add it to your front-end application and direct your app users to this URL when a button or link is clicked.
To configure a third-party authentication provider via the Designer, you need to navigate the App settings and select Authentication view.
Authentication view
In the authentication view:
- 1.Select the User Data Model where your authentication user information will be stored. The user data model needs to be a permanent model with the required exact field names and types. You can easily add the missing fields to the selected model if the model does not have those required fields already.
- 2.Specify the redirect URLs of your front-end application. When your app user is successfully authenticated, your frontend app will be redirected to the success redirect URL. A stringified JSON response data, which includes authenticated user data and if selected, the user session data, will be provided as a query string parameter named 'response.' Similarly, if the user cannot be authenticated, in that case, your frontend app will be redirected to the error redirect URL and a stringified error JSON object will be provided in the query string parameter named 'response.'
- 3.Select whether to create a user session or not. You can choose to create a new session and associated session token for authenticated users and return also this data in the success redirect response.
- 4.Enable the required authentication provider. Provide the required client id and client secret and configure the callback URL in the respective authentication provider's developer/cloud portal.
- 5.Hit Save Changes to save your authentication configuration settings
Copy link