SSO is short for single sign on. It means users have only a single login across all the parts of the system. That can be something like "Login with Google" or i

SSO is short for single sign on. It means users have only a single login across all the parts of the system. That can be something like "Login with Google" or it can be they just have a single local user account that works everywhere. A really efficient way to make SSO work is to allow a reverse proxy to do all the work. A reverse proxy is a webserver (such as nginx or traefik) which receives all incoming requests and then hands them off to the correct bit of software, such as Plex or Heimdall. Reverse proxies do lots of things but they help glue different pieces of software together. It allows you to have "http://plex.example.com http://plex.example.com" and "http://heimdall.example.com http://heimdall.example.com" on the same server as a for instance. You can also have the reverse proxy handle authentication. Users get redirected to sign in if they don't have the right cookie and when the proxy forwards their request it includes headers that give the username, email, etc to the underlying software. This way instead of both Plex and Heimdall having to support a bunch of different sign in options, user management, password resets, etc all that is done by the reverse proxy. Your software just has to trust the reverse proxy and get it's data from the headers.