Atlassian authentication

Atlassian authentication lets your users sign in with an Atlassian account they already use for Jira, Confluence, and other Atlassian products. Once connected, you can add a “Continue with Atlassian” button in your WeWeb app.

What this integration supports

• Social sign in with Atlassian
• Redirect to different pages for success, error, and first-time users

Setup in the Atlassian developer console

You create an OAuth app in Atlassian and register WeWeb’s callback URL (the URL Atlassian sends users back to after they approve sign in).

1. Create an OAuth 2.0 (3LO) app

1. Open the Atlassian Developer Console.
2. Click Create new app.
3. Fill in your app details.

2. Add the callback URL

1. In your app, open Authorization.
2. Next to OAuth 2.0 (3LO), click Configure.
3. Set the Callback URL to your WeWeb callback URL:
   • https://<your-domain>/api/auth/callback/atlassian
4. Save your changes.

If you use multiple environments, add a callback URL for each environment you use (preview, staging, production).

3. Copy your credentials

In the app’s Settings, copy:

• Client ID
• Client Secret

Connect Atlassian in WeWeb

1. In the WeWeb editor, go to Data & API → Auth → Integrating providers.
2. Find Atlassian and expand it.
3. Turn on the Enable toggle.
4. Fill in:
   • Client ID
   • Client Secret
5. Click Save.

WeWeb stores these values as environment variables (for example PROVIDER_ATLASSIAN_CLIENT_ID and PROVIDER_ATLASSIAN_CLIENT_SECRET) and uses them to complete the sign-in flow.

Test sign in

1. In Interface, add a “Continue with Atlassian” button.
2. Create a workflow on click and add Sign in with social provider.
3. Set:
   • Provider: atlassian
   • Success page, Error page, And (optional) New user page
4. Preview your project and complete the Atlassian sign-in flow.

For how roles and protected pages behave after sign in, see Users and roles overview →.

Common pitfalls

Callback URL mismatch

If Atlassian shows a redirect or callback error, the callback URL in Atlassian usually doesn’t match what your app is using.

• Make sure the callback URL in Atlassian exactly matches https:///api/auth/callback/atlassian for the environment you are testing.
• Check that you are using the right domain (preview vs production) and the right protocol (https://).

Missing permissions (scopes)

If users can’t complete sign in or the consent screen fails, the app may be missing required permissions.

• In the Atlassian developer console, open Permissions and confirm your app has the scopes needed to identify the user.
• If you change scopes after users already approved the app, users may need to approve again.

Reference

WeWeb settings

Setting in WeWeb	Description	Where to find it in Atlassian
Client ID	Identifies your Atlassian OAuth app.	App Settings in the Atlassian developer console.
Client Secret	Secret used to securely complete sign in.	App Settings in the Atlassian developer console.

FAQs

Which URL do I add as the callback URL?

Use your WeWeb callback URL: https://<your-domain>/api/auth/callback/atlassian. Add one callback URL per environment you use.

What provider value should I use in the workflow action?

Use atlassian as the Provider value in the Sign in with social provider action.

Can I use different credentials for staging and production?

Yes. Configure the Atlassian provider in each WeWeb environment so staging and production can use different apps and keys.

Continue learning

Connect a provider is only the first step. Next, learn how to manage users and roles so you can protect pages and data.

Users and roles overview →