Identity on most small and mid-sized networks grows one application at a time. Each tool keeps its own accounts, each departure means a checklist, and the question an auditor eventually asks, who had access to what and who approved it, has no single place to find an answer. ResorsIT answers it in one place by splitting the work across three open-source engines and tying them together with its own User Manager and Journal.
Sign-On With Authentik
Authentik is the identity provider: the system people actually sign in to. With Authentik integrated into ResorsIT, users log in once and reach every application through their Hub, with no separate credentials per application. Multi-factor authentication is configured at the platform level, so it applies consistently across every integrated app. External web applications that support SAML or OIDC join the same sign-on. Organizations that already run an SSO or IAM product can keep it, and ResorsIT adapts its configuration to the existing environment.
Governance With MidPoint
MidPoint governs the lifecycle of identities and entitlements. When someone joins, changes roles or leaves, MidPoint works out what that person should hold and the platform carries the change to their accounts and group memberships. Scheduled access reviews ask the right people to confirm that access is still needed, and segregation-of-duties rules stop conflicting roles from being combined. Approvals, review decisions and blocked requests are recorded in the Journal, so the answer to an audit question is a lookup rather than a project.
Permissions With Cedar
Cedar is the policy engine that decides what a signed-in person may do. Its policies cover every application on the platform, from which tiles appear in a person’s Hub down to individual resources, and they live in one place with a full version history. Cedar’s evaluation is formally verified, which matters when the policies are what stand between a person and sensitive data.
One Person, Several Identities
Some systems should not share the sign-on password. Mail clients store passwords on every device, and Windows keeps password hashes that are a well-known target, so ResorsIT gives email and Windows logins identities of their own with separate passwords. The User Manager still presents them as one person, and deactivating that person disables every identity at once.