Gameyfin's SSO role mapping starts before login
Gameyfin's SSO role mapping starts before login Gameyfin is a self-hosted web library for video games. Its setup flow asks the operator to create an administrative account. Its configuration documentation includes user
Gameyfin's SSO role mapping starts before login
Gameyfin is a self-hosted web library for video games. Its setup flow asks the operator to create an administrative account. Its configuration documentation includes users, SSO, automatic user creation, and role mapping. Those features make the application a good example of a small service whose identity model deserves a larger review than its public page count suggests.
A count-only ZoomEye query executed on 2026-11-20 at 04:45 CST used page 1, pagesize 1, and sub_type=all. app="Gameyfin" returned 0 matches. title="Gameyfin" returned 52 matches. The exact application query did not identify a product fingerprint, while the title query found a small set of pages. Neither result is a count of exposed user libraries.
Gameyfin's SSO documentation says OIDC/OAuth2 login can be enabled, users can be created automatically after registration, and existing users can be matched by username or email. It also describes SSO provider guides that map identity-provider groups to Gameyfin roles, including superadmin and admin roles. That mapping is the important boundary.
Make the identity source authoritative
If SSO is enabled, the identity provider should be the authoritative source for account status and group membership. Decide whether a first-time SSO login should create a Gameyfin user automatically. Automatic creation is convenient for a trusted household or team, but it can turn a broad identity-provider audience into a library account population. If the provider allows self-registration, the application inherits that policy.
Match users by a stable claim. The documentation offers username and email as matching options. Whichever field is chosen, confirm that it is immutable at the identity provider and verified before it is used. An email change or a re-used username can remap an existing Gameyfin account if the application treats it as the same identity.
Role mapping should default to the least privileged user. Superadmin and admin groups should be explicit and small. Test how a user with no mapped group is handled, and test what happens when a user is removed from an administrator group. A login that succeeds after group removal may still carry an application role until the next synchronization.
Keep a local recovery path
SSO does not remove the need for a local administrative account, but that account should be protected and audited. If the identity provider is unavailable, a local break-glass account can restore service. Store its credential outside the SSO provider and review its use. Disable the account when a normal administrative path is available, or restrict it to a management network.
The library may contain game files, metadata, user lists, and plugin configuration. Separate the user role from the administrator role and review plugin permissions. Plugins can add routes, filesystem access, or external calls. The SSO role mapping should not automatically grant every plugin's administrative function.
The title count is a discovery signal. For each candidate within an authorized scope, verify the page and compare it with the organization's inventory. The security action is to review SSO enablement, automatic account creation, claim matching, group-to-role mapping, and local recovery. A small count does not make those controls less important.
References
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.