Can't get oauth for on-prem datacenter working

[icsy7867]

I am sure I have done something stupid... but I can't get the oauth_setup process to not try to auth against the cloud instance.

I have tried following this:
#856

docker run -i --rm --name mcp-jira -p 9000:9000 \
    -e JIRA_OAUTH_CLIENT_ID="XXXXXXX" \
    -e JIRA_URL="https://testjira.company.com" \
    -e JIRA_OAUTH_CLIENT_SECRET="YYYYYYYYYY" \
    -v $(pwd)/mcp-atlassian:/home/app/.mcp-atlassian:z \
  ghcr.io/sooperset/mcp-atlassian:latest --oauth-setup -v

I also found some references to:
-e ATLASSIAN_OAUTH_INSTANCE_TYPE="datacenter"
In the pull but nothing seems to work.

I also noticed that the PR above was closed, in favor of this:
#952

It looks like there is a --jira-url, and I tried this too.

But the "open-browser for authentication" points to:
https://auth.atlassian.com/authorize

So I am not sure what I am missing to make this work for a datacetner on-prem server.

[Troubladore]

Hi — could you confirm which Docker image version/tag you're using? The DC OAuth support landed in PR #952 (merged Feb 20), so images built after that date should have it.

In the community fork, we have passing tests that cover the exact scenario you described — setting JIRA_URL to a non-Cloud server and using OAuth:

• test_from_env_dc_detection — confirms that a non-Cloud JIRA_URL sets base_url and is_data_center=True (test_oauth.py)
• test_dc_authorize_url — confirms the authorize URL points to {your_server}/rest/oauth2/latest/authorize, not auth.atlassian.com
• test_from_env_dc_defaults_redirect_and_scope — confirms DC gets sensible defaults for redirect_uri and scope

A couple of things to check:

1. Does the wizard show "Detected Server/Data Center instance: https://testjira.company.com" when it starts? If it shows "Detected Atlassian Cloud instance" instead, the URL detection may not be working for your domain.
2. Are you using ATLASSIAN_OAUTH_CLIENT_ID/SECRET or JIRA_OAUTH_CLIENT_ID/SECRET? Both should work, but the wizard reads the env vars in a specific order.
3. For the DC OAuth setup, you need an Application Link configured as OAuth 2.0 (Incoming) in your Jira admin — is that set up on your server?

[icsy7867]

Thanks for your reply! I had definitely pulled the latest container at the time of the post.

I also also have an oauth2 application link setup. But tomorrow at work ill give it another shot! Thanks!