Third-party single sign-on

Andy HsuGuideAdvancedGuideAbout 4 min

Third-party single sign-on

Single sign-on client id

client ID

Single sign-on client secrets

secrets ID

matters needing attention

  1. Remember to write and save the background parameters of AList. After writing and saving, you have to go back to the bottom of the personal data and there will be a button that needs to be bound, otherwise it cannot be used

  2. Only one of the four types of single sign-on can be enabled temporarily. If you used other single sign-on methods before and then changed to a new single Unbind (just one click) and then bind the single sign-on method you want to use now.

Note

If you want to use GitHub to log in, you first need the machine you built Alist to be able to connect to GitHub before you can call and use it, otherwise you cannot use it if the link is not connected

Open https://github.com/settings/developersopen in new window Click New OAuth App

Register OAuth Instructions

  • Application name
    • Write whatever you want to call it
  • Homepage URL
    • home URL address
      • Both http and https can be used
  • Application description
    • write whatever you want
  • Authorization callback URL
    • Callback URL address
    • https://your_domain/api/auth/sso_callback
      • Both http and https can be used

Remember to get Client secrets after filling it out, and then fill it in the Alist background.

Remember to write and save the background parameters of AList. After writing and saving, you have to go back to the bottom of the personal data and there will be a button that needs to be bound, otherwise it cannot be used

Completely fill in the reference schematic

sso

GitHub login Video Tutorials

Loading...

If the video fails, you can watch it here: https://b23.tv/Fm8AkC5open in new window