Partner access
The common request: a contractor, auditor or integration partner needs one internal application, and nothing else, for a limited time. This is the case a VPN handles worst and Proxility handles well.
The pattern#
- A realm of their own. Create
partner-<name>rather than putting them inprod. Delegation, logging and teardown all become one object. - Their own connector. They run it in their network; you never hold their credentials and they never hold yours.
- One rule, one service, one port.
1 2 3 4 5 6 7 8 | |
Make it expire#
--expires is the difference between an access grant and a permanent hole.
Set it to the contract end date. An expired rule stops allowing traffic and
stays visible in policy history, so the next audit can see what was granted and
when it lapsed.
Review what is outstanding:
1 | |
Human access without a connector#
For a named individual rather than a partner system, use a ScaiKey-backed human identity and let them connect from the Proxility client without running a connector:
1 2 3 4 5 | |
Their session identity is short-lived and tied to their ScaiKey authentication, so revoking the person in ScaiKey revokes their Proxility access too.
Teardown#
1 | |
This revokes every identity in the realm and removes its rules. The decision log is retained — you want to be able to answer what they reached, after they are gone.