Most small networks protect their applications one at a time. Each app has its own login page, its own idea of who an administrator is, and its own exposure to the internet, so the security of the whole depends on the weakest app’s settings. ResorsIT changes the shape of the problem by putting one front door in front of everything the Site runs.
One Front Door
Every web request arrives at the Site over HTTPS through Traefik, which terminates TLS and routes the request to the right application on the Site’s internal network. Each route Traefik serves carries a forward-auth check, so Traefik pauses on every request and asks for a verdict before it passes anything along.
Identity and Policy on Every Request
The verdict comes from Cedar forward-auth, a small ResorsIT service that sits between Traefik and the policy engine. It validates the caller’s Authentik session, sending a first-time visitor to sign in, then puts the person, the action and the application to Cedar and translates the answer into allow or deny. When the policy engine cannot be reached, it holds the request at the proxy instead of letting it through. Every decision is buffered and forwarded to the audit trail.
Applications Without Their Own Sign-On
Plenty of useful applications were never built for single sign-on. Behind Secure Access they do not need to be: the session is validated before the request arrives, and the person’s identity is passed to the application in the request itself, so an app with no SSO support still receives only authenticated, authorized users.
Apps Outside the Site
Applications that run elsewhere in the same data center are reached through the same front door and the same checks. Software-as-a-service apps that speak SAML or OIDC sign people in through the Site’s identity provider directly, and their accounts are governed by Identity and Governance.