You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

OIC MCP Server — Support OAuth 2.0 Auto-Discovery via .well-known Endpoint for External AI Clients

in Idea Lab – Integration Cloud 1 comment

Organization Name (Required - If you are an Oracle Partner, please provide the organization you are logging the idea on behalf of):

NCS Multistage

Description (Required):

As AI agent platforms such as Claude Enterprise (Anthropic), Microsoft Copilot, and others become mainstream integration consumers, they rely heavily on OAuth 2.0 auto-discovery to connect to MCP servers. These clients are designed to automatically discover authorization endpoints by calling the standard .well-known/oauth-authorization-server endpoint (RFC 8414) on the MCP server before initiating the OAuth Authorization Code flow.

Currently, the OIC MCP Server does not support this discovery mechanism. The .well-known/oauth-authorization-server endpoint either returns 401 Unauthorized or does not advertise the correct IDCS authorization URL to external clients. This makes it impossible for external AI clients that rely on auto-discovery to connect to OIC MCP Servers using the Authorization Code flow.

Tagged:
1
Up Down
1 votes

Submitted · Last Updated

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!