Hello,
Our MCP client is blocked at the Atlassian consent step even though its domain is on our organization's allowlist.
Setup
- Organization: PROGMBH
- Site: progmbh.atlassian.net
- MCP server: https://mcp.atlassian.com/v2/mcp (OAuth 2.1, dynamic client registration through auth.atlassian.com)
- Redirect URI: https://swissai.sharedlayer.ai/connect/callback
- Scopes requested: offline_access read:account read:me read:jira:agent-interface search:jira:agent-interface write:jira:agent-interface
Admin configuration
- In Atlassian Administration → Connectors → Atlassian MCP server → Domains, under "Your domains", we added
https://swissai.sharedlayer.ai/**. - "Allow Atlassian supported domains" is on.
What happens
When the user starts the OAuth flow, the consent page shows:
Access to this domain is restricted. Your admin has blocked this domain "https://swissai.sharedlayer.ai/connect/callback" in your organization's settings.
What we have tried
- Waited after adding the domain and retried several times over [fill in how long, e.g. "about 2 hours"], each in a new browser session.
- Registered a new client by dynamic client registration.
- Reduced the requested scopes to Jira only.
- Confirmed that the redirect_uri sent in the authorize request is exactly the one above.
All attempts fail with the same error. The most recent were on 18 Nov 2026, [fill in time, e.g. "around 17:30"] CET.
Questions
- Why is this redirect URI blocked when
https://swissai.sharedlayer.ai/** is in our allowed domains? - Is the domain policy taken from a different organization than PROGMBH, for example the org that manages the user's account or another org the user belongs to? If so, which one?
- Does the allowlist entry need a different format, or is there a delay or cache before custom domains take effect?
Thank you,
Valentin I.
CTO, PROGMBH