The authorized login SDK provides a clear account connection path for third-party services. Once the user confirms in Potato, your service receives the authorization information needed to complete the verification.
Applicable scenarios
When you want to reduce the registration steps, allow users to quickly bind existing accounts, or use Potato identities to log in to communities and services, you can use the authorized login capability. The interface should clearly state the purpose of the login and the information that will be requested.
Basic access process
Complete access in four steps
- Create an application in the developer backend and configure a trusted callback address
- Display the "Sign in with Potato" entry on your website or app
- Guide users to confirm authorization requests in Potato
- The server verifies the authorization result and creates or binds a local account.
Server side verification
The authorization result must be verified by the server. Please verify the signature, time, and callback address against the application configuration, and then establish a login session after passing the verification. Don't rely solely on parameters passed from the browser page, and don't put your application keys in the front-end code.
Privacy and user experience
Request only the information necessary to complete the service and describe the data usage, retention period and deletion methods in the privacy policy. Users should be able to return to the original page normally when canceling authorization, and should not collect additional information on the grounds that they cannot continue to use it.
Check before going online
Verify initial authorization, re-login, cancellation of authorization and callback failure in the test environment; the production environment uses HTTPS and provides understandable prompts and retry entries for error status.
Return to Developer Center