Skip to main content
Unlisted page
This page is unlisted. Search engines will not index it, and only users having a direct link can access it.
Version: 11.3.0

Gateway Settings

Advanced → Gateway Settings holds the cross-cutting settings of HYPR AgentPass™. They cover how the gateway:

  • Validates inbound requests
  • Decides which MCP clients may register
  • Signs people in
  • Times out approvals
  • Drafts policies
  • Reaches your HYPR tenant
  • Receives directory changes, and sends email

The page has a tab for each group. Each card saves on its own, and some controls save as soon as you choose them. A role that can view settings but not manage them sees every control as read-only. Each table on this page names a tab's cards and fields, and links to the page that explains them.

Gateway​

A card that still holds its default value shows a Default tag.

The Gateway tab has two cards.

CardFieldsWhat it decides
MCP Session ValidationStrict, Lenient or Strict with graceHow the gateway treats an inbound gateway-issued MCP token it does not recognize. Strict, the default, rejects it. Lenient logs and accepts it, while you validate a deployment. Strict with grace rejects unknown tokens, except that it promotes them on first sight after a deploy, so existing clients keep working until their access tokens expire
Connector Request SamplesSamples kept per toolHow many recent request samples each connector keeps per tool, for its Recent Requests tab. From 1 to 50. The default is 10. A new sample replaces the oldest. Credentials and secret fields are redacted before a sample is stored

OAuth / DCR​

CardFieldsWhere it is explained
Redirect hostsApproved https:// hosts, exact or wildcard, and Add hostControlling MCP Client Registration
Custom URL schemesApproved custom schemes for desktop and command-line clients, and Add schemeControlling MCP Client Registration
DCR registration controlsRegistrations accepted over a number of seconds, maximum active clients, days before an inactive client is removed, and Save DCR controlsControlling MCP Client Registration
Registered clientsA read-only list of the MCP clients that registered in the last 24 hours: client ID, redirect addresses and last usedControlling MCP Client Registration

Registration is open, and both lists are deny-unless-listed. The lists, not registration, therefore decide which MCP clients the gateway trusts. Redirects to localhost and the loopback addresses are always allowed, and are not configurable.

Authentication​

CardFieldsWhere it is explained
Console SSO (OIDC)Issuer or auth-server URL; authorization, token, userinfo, JWKS, end-session and revocation endpoints; client ID; client secret; PKCE required; scopes; principal claim; display name claims; email claim; role claim path; maximum session length, from 5 to 1440 minutes, with a default of 480; and an Advanced section for client authentication method, token audience, extra authorization parameters, token issuer override and logging of login request and response bodiesSigning In to the Console

Approvals​

CardFieldsWhat it decides
Approval TimeoutsOnboarding approval timeout and Policy-triggered approval timeoutHow long a held request waits for a supervisor before it expires. An expired request is not an approval. The onboarding timeout covers a new agent's first request. The policy-triggered timeout covers a request held by a policy that requires approval. Each is from 1 to 1440 minutes. The default is 30
Approved Onboarding ValidityOnboarding access validityHow long an approved onboarding grants access before the agent must be approved again. From 1 to 8760 hours. The default is 24

A changed value applies to new approvals only. Pending approvals keep their deadline, and approved onboardings keep the validity they were granted with.

Both work with a connector's onboarding mode. See Onboarding Mode.

Policy Authoring​

CardFieldsWhere it is explained
Policy authoring (LLM)Anthropic API key and Author modelSetting Up AI Authoring
AI policy spendInput and output tokens, draft requests and LLM errors, and RefreshSetting Up AI Authoring
Who drafts your policiesA routes table of When drafting, Use and Deadline, and + Add routeChoosing Who Drafts Your Policies
Inference Stream InspectionMaximum hold time, from 5000 to 300000 ms, with a default of 30000; and Maximum held size, from 4096 to 4194304 bytes, with a default of 262144Governing Inference Traffic
Policy MCP clientsRegister a clientPolicy MCP Server

To check a streamed tool call before the agent runs it, the gateway holds the call until it has fully arrived. The two stream inspection bounds cap that hold. Maximum hold time is how long the gateway waits for one tool call to finish arriving. Maximum held size is how much of one tool call it holds. Where an inference policy in Enforce mode applies, a call that exceeds either bound is cut, and the user sees a block notice that names the bound. In Observe mode, the overflow is recorded and the call is released.

Passkeys (FIDO2)​

CardFieldsWhere it is explained
HYPR FIDO2 IntegrationHYPR tenant base URL, RP API access token, RP Application ID and Gateway public origin, the optional HYPR mobile APK key-hashes, and Check connectionConnecting to Your HYPR Tenant
Mobile App AssociationsFor iOS, App IDs. For Android, Package name and Signing-cert SHA-256 fingerprintsConnecting to Your HYPR Tenant
Passkey approval policyPolicy: Strict (HYPR Mobile only), Any passkey or Custom allowlist; Require signed approvals: Optional (soak) or Required (production); HYPR Mobile AAGUIDs; custom allowlist; display labelsConnecting to Your HYPR Tenant

Directory / SCIM​

The Directory / SCIM Provisioning card connects your identity provider's directory:

  • Enable provisioning.
  • Copy the tenant's SCIM Base URL.
  • Generate the write-only Bearer token for your identity provider. Rotating the token invalidates the previous value.
  • Select the provider, for tailored mapping hints.
  • Use Recent SCIM activity to check synchronization requests.

Provisioned people appear on the Humans tab of Oversight → People. See Supervisor Identity.

Email / Invitations​

CardFieldsWhere it is explained
Email deliverySending provider: Platform default, Own AWS SES or Own SMTPInviting Administrators
InvitationsAuto-invite on provision; Invite link lifetime (hours), from 1 to 8760, with a default of 168; Automatic reminders; Reminder interval (hours), from 1 to 8760, with a default of 48; Max reminders, from 0 to 50, with a default of 3Inviting Administrators

On the Invitations card, Auto-invite on provision sends an invitation as soon as a person is provisioned, through SCIM or by hand. Automatic reminders resends the invitation to people who have not enrolled. After Max reminders, a person still pending is marked Lapsed.