durin
Book A Demo
Knowledge base
Security & activity

Credential security

Understand how Durin and provider credentials stay separate.

Admin · Security1 min readUpdated

Separate authentication boundaries

Your client authenticates to Durin. Upstream requests use the configured provider credential, bound to the tenant, identity, provider, scopes, environment, and intended audience. Durin does not pass its own bearer token to the upstream provider.

Keep secrets out of diagnostics

Use request IDs, connection IDs, timestamps, and error messages when investigating access. Do not paste provider tokens or secret configuration into support messages. An issued endpoint URL identifies an entry point; it does not replace authentication.

Frequently asked questions

Does disconnecting my provider disable it for everyone?

No. Personal disconnect affects your access. An administrator uses Disable installation to stop normal routing for the workspace.

Does AI policy drafting see request content or member details?

No. It receives an administrator’s description, workspace connection, tool and client IDs, and published custom rules with member identities removed. It runs only after an administrator turns it on.

Does adding Durin revoke credentials used elsewhere?

No. Your team must separately manage other client endpoints, direct provider credentials, and network controls.

Try Durin with your MCP workflow.

Book a demo to explore agent access, policy checks, approvals, and audit records with our team.

Book a demo

Choose which optional purposes this browser allows. Cookies that keep the site working, keep you signed in and remember this choice are always on, as is the referral cookie a referral link sets for up to 90 days. Your choice is stored in a first-party cookie for 180 days. Saving a choice that turns analytics off reloads this page if analytics was running on it. Read the privacy notice.