Use this file to discover all available pages before exploring further.
Native mobile applications can use native or browser-based login flows.In a browser-based login flow, the user is shown a web browser and redirected to the Auth0 login page for sign up or log in. For example: an iOS application opens a SafariViewController or an Android application opens a Custom Chrome Tab.With a native login flow, the user signs up or enters their credentials directly into the app.Regardless of which option you choose, Auth0 supports either.
Phishing/security concerns: an unauthorized party could decompile or intercept traffic to/from your application to get the and authentication URL. With this information the unauthorized party could create a rogue application, upload it to an application store, and use it to phish for usernames, passwords, and .
: users have to enter their credentials for each application.
Can implement SSO with native apps by storing refresh tokens on a shared keychain, but this is not compliant with the OAuth 2.0 specifications.
Takes more time to implement
No automatic improvements when Auth0 adds new features, have to update app code to take advantage of new features vs UL
Not compliant with best practices
RFC 8252 OAuth 2.0 for Native Apps: authorization requests from native apps should only be made through external user-agents, primarily the user’s browser
Limits are only applied to requests related to the Native Social Login flows, which are identified based on the body of the requests with the following initial criteria:
