new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Better Auth · Authentication · all subjects

social sign-on/atlassian

4 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Atlassian developer console credential setup

To get Atlassian OAuth credentials, sign in to your Atlassian account and navigate to the Atlassian Developer Console at https://developer.atlassian.com/console/myapps/. Click 'Create new app', fill out the app details, configure the redirect URI (for example https://yourdomain.com/api/auth/callback/atlassian), and note your Client ID and Client Secret. The redirect URI must match your application's callback URL, and if you change the base path of the auth routes, you should update the redirect URI accordingly.

Atlassian OAuth default scopes

The default OAuth scopes for Atlassian are 'read:jira-user' and 'offline_access'. Additional scopes are available and documented in the Atlassian OAuth 2.0 (3LO) apps documentation.

Configure Atlassian provider in better-auth

Import betterAuth and configure the Atlassian provider in the socialProviders option. The provider requires clientId and clientSecret, which should be passed as strings from environment variables.

Sign in with Atlassian using client

To sign in with Atlassian, use the signIn.social function from the auth client with the provider set to 'atlassian'. The function takes an object with a provider property.

Give your agent this brain