Atlassian Provider not working but its in the docs for v5

[tcarbs]

What is the improvement or update you wish to see?

I would like to see Atlassian implemented in v5. I see it is in v4, maybe you guys just haven't gotten around to it. All good, but remove it as an option from your v5 docs when you search for OAuth providers.

Is there any context that might help us understand?

These are the docs for v5. https://authjs.dev/getting-started/authentication/oauth

You can search for Atlassian but it is not in the v5 packages. https://github.com/nextauthjs/next-auth/tree/main/packages/core/src/providers

Does the docs page already exist? Please link to it.

https://authjs.dev/getting-started/authentication/oauth

[tcarbs]

found the actual link that is empty.

https://authjs.dev/getting-started/providers/atlassian

[arwanfiles]

same issue :(

Edit by maintainer bot: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!

[quinnsprouse]

Running into the same issue...

[balazsorban44]

I dropped the code in https://github.com/nextauthjs/next-auth/commit/cb1a260523d7b5c6a5af59b63f1e911a60a9edb1

but quite frankly I don't remember why. From my description, I assessed it was somehow relying on OAuth 1.0, which is not supported anymore.

Im fine if we re-add it. Here is the documentation https://developer.atlassian.com/cloud/jira/software/oauth-2-3lo-apps/

[github-actions[bot]]

This issue was marked with the good first issue label by a maintainer.

This means that it is a good candidate for someone interested in contributing to the project, but does not know where to start.

Have a look at the Contributing Guide first.

This will help you set up your development environment to get started. When you are ready, open a PR, and link back to this issue in the form of adding Fixes #1234 to the PR description, where 1234 is the issue number. This will auto-close the issue when the PR gets merged, making it easier for us to keep track of what has been fixed.

Please make sure that - if applicable - you add tests for the changes you make.

If you have any questions, feel free to ask in the comments below or the PR. Generally, you don't need to @mention anyone directly, as we will get notified anyway and will respond as soon as we can)

[!NOTE]
There is no need to ask for permission "can I work on this?" Please, go ahead if there is no linked PR :slightly_smiling_face:

[DevRish]

@balazsorban44 Thanks for providing the latest docs! I have made the necessary modifications for oauth2.0 and brought back the atlassian provider. Please review the PR.