How A3L Authentication works
A3L Authentication provides a single SDK that behaves differently depending on the device on which it’s used, while keeping the user experience as similar as possible. A3L Authentication is an abstraction over Google Sign-In and AppAuth. The solution used by A3L Authentication depends on whether the device the app is used on supports Google Play services. There are differences in the sign-in flow that depend on whether a device has Google Play services available. When a user signs in on a Google Play services supported device, they see an app-based authentication. On devices that don’t support Google Play services, the authentication is Custom Tab based, and the user is redirected to a Custom Tab where they need to sign in. This is because, unlike Google’s in-app sign-in, AppAuth provides a Custom Tab based sign-in.Feature comparison
The following table describes the features offered in A3L Authentication compared to AppAuth and Google Sign-In.| Feature | Google Sign-In | AppAuth | A3L Authentication |
|---|---|---|---|
| Configuring Sign In | |||
| Sign In | |||
| Fetching Profile Information | |||
| Sign out | |||
| Disconnect accounts | |||
| Authenticate with a backend server | |||
| Enabling Server-Side Access |

