Docs ยท Projects
App Authentication & Authorization
Authentication is a way of controlling who can access your app by requiring users to log into your application. Authorization then allows you to restrict what users can see and do once logged into your application. You can read more about this here.
By enabling authentication, you are asking users to provide information about who they are, usually through a set of credentials. Once a user is authenticated, then you can leverage the inbuilt authorization framework to control that users access to various parts of your App.
Authentication can be implemented using the following protocols:
| Protocol | Description |
|---|---|
| Username & Password | Authentication flow is handled by Toca, each user has a username and password which they use to access the Application. |
| OAuth2 | Your app links to another identity provider (e.g. Microsoft or Google), allowing users to log into your app using a preexisting account. |
| OpenID) | Much like OAuth2 but allows you to gather more information about the user due to the user information provided in this protocol. E.g. User email, profile picture |
Once you have been able to identify who a user is, you can control what they are authorized to view and do. You can control access to the following parts of an App:
- Each page of your app
- Each resource your app links to (Datastores and Listeners)
- Content within your pages
App Users in Automation
You can also carry out administrative tasks such as creating App users or deleting App users from your Automation by using the App actions. You can also access information about an App User from your automation, this is useful when you want to do something like modify an App User, an App Group or an App Role dynamically rather than manually. To identify which App User ran a workflow, it will add an input called "AppUserId", more information about this can be found on the Inputs, Outputs and Context section of the Workflow page. You can then use this "AppUserId" input with the Get App User action to get more information about the current App User.
You can also use this information to control what access an App user has to table data by leveraging Row Level Permissions.
More Reading
For more info about authentication and authorization see: