Migrating

Migrating from the Original Plugin

If you are currently running the SSO Authentication plugin from the original 9p4/jellyfin-plugin-sso repository, migration to this fork requires no manual steps. Your existing configuration is fully preserved.

Why No Migration Is Needed

This fork keeps the same:

• Plugin GUID: 505ce9d1-d916-42fa-86ca-673ef241d7df
• Assembly namespace: Jellyfin.Plugin.SSO_Auth
• Configuration XML schema: all fields in SamlConfig, OidConfig, and FolderRoleMap are unchanged

Jellyfin stores plugin configuration in an XML file identified by the plugin's GUID and namespace. Because both are identical, Jellyfin reads the existing configuration file transparently after the update.

Migration Steps

If you installed the original plugin from a repository catalog

1. Go to Administration → Plugins → Repositories.
2. Remove the old repository URL (if it is still listed).
3. Add the new repository URL:

   https://raw.githubusercontent.com/K0lin/jellyfin-plugin-sso/manifest-release/manifest.json
   

4. Go to Administration → Plugins → Catalog, find SSO Authentication, and install / update it.
5. Restart Jellyfin.

Your provider configurations, account links, and canonical mappings are all preserved.

If you installed the original plugin manually

1. Stop Jellyfin.
2. Download the latest release ZIP from Releases.
3. Replace the DLL files in <jellyfin-config>/plugins/SSO-Auth/ with the new ones:
   • SSO-Auth.dll
   • Duende.IdentityModel.OidcClient.dll
   • Duende.IdentityModel.dll
4. Start Jellyfin.

Do not delete the <jellyfin-config>/plugins/configurations/Jellyfin.Plugin.SSO_Auth.xml file, that is where your configuration lives.

Compatibility

What	Status
OIDC provider configurations	Fully preserved
SAML provider configurations	Fully preserved
Account canonical links	Fully preserved
Folder role mappings	Fully preserved
API endpoint paths	Unchanged
Redirect URIs in your IdP	No change needed

After Updating

• A Jellyfin server restart is required after any plugin update.
• Open the plugin settings page to verify your configuration loaded correctly.
• Test a login through each configured SSO provider.

Known Problems

• If the process gets stuck at the “restart” stage during the update, you need to delete the old plugin folder and then restart

Rollback

If you need to go back to the original plugin, simply replace the DLLs with the previous version's files. The configuration XML is forward and backward compatible.