AI-generated editorial illustration; not a documentary photograph.
AWS has introduced a managed Consent portal for Amazon Bedrock AgentCore, giving organizations a built-in way to collect and bind end-user OAuth approval when AI agents access external services. The capability is described in an AWS post dated September 14, 2026, and works with AgentCore Gateway and AgentCore Identity.
Replacing Custom Session Binding
Agents acting through services such as GitHub or Slack need users to authenticate, approve requested permissions and have the resulting OAuth grant associated with the correct identity. AgentCore Identity customers using the OAuth 2.0 authorization code flow previously had to operate this session-binding process themselves, including a public HTTPS callback, browser sessions and calls to CompleteResourceTokenAuth.
The new portal manages browser redirects and session binding. Administrators create a portal for an AgentCore Gateway, connect it to their organization's identity provider and share the generated URL. AgentCore Identity stores resulting tokens in its token vault.
Consent Before Tool Use
Users sign in through the organization's identity provider and approve each configured provider separately. A developer could connect GitHub while leaving Slack disconnected, then return to an IDE or Model Context Protocol client using the same gateway. AWS identifies Kiro, Claude Code, Cursor and Visual Studio Code as applicable client environments.
After consent, later tool calls can reuse the token associated with that user. Users can also disconnect a provider and reconnect it later, while renewed authorization is required if a grant is revoked, expires or otherwise needs fresh consent.
Administrative Requirements
Deployment still requires an AgentCore Gateway configured with JWT inbound authorization, an OIDC application for the corporate identity provider, outbound OAuth credential providers and registered applications for each external service. Administrators must also configure callback and return URLs and provide an IAM execution role with access to any required customer-managed secrets.
AWS allows one Consent portal per gateway, and the selected gateway cannot be changed after portal creation. The identity provider must issue a JWT access token that the portal can validate.
Token and Audit Limits
AgentCore Identity can use provider-issued refresh tokens to obtain new access tokens. If a provider does not issue a valid refresh token, or the token expires or is revoked, the user must return to the portal and authorize access again.
Consent operations are recorded in AWS CloudTrail, including events for starting OAuth authorization, completing session binding and obtaining gateway access. AWS says sensitive token and state values are redacted from those records.
Source: Manage end-user OAuth consent for AI agents with Amazon Bedrock AgentCore
SIGNAL TITANS
Leave a Reply