Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Atlassian Confluence Cloud #28

Closed
Compy opened this issue Mar 20, 2023 · 2 comments
Closed

Support Atlassian Confluence Cloud #28

Compy opened this issue Mar 20, 2023 · 2 comments
Labels

Comments

@Compy
Copy link

Compy commented Mar 20, 2023

Issue

Currently only self-hosted Atlassian Confluence is supported. However Atlassian Cloud is widely adopted and has a nearly identical API endpoint structure.

Currently Gerev suggests creating a PAT in order for the system to authenticate and pull data. That PAT is then used as a bearer token to the upstream Atlassian API. For Cloud installations, account-specific API tokens are allowed, which are used as basic auth where the username is the account holder's email address, and the password is the generated API key.

From there, the same endpoint structure and payloads are used to scrape the /space endpoint

API Tokens are managed here

Further Questions

How do we distinguish auth types? It doesn't make sense to duplicate the entire data source logic just to support a different auth scheme.

@bryan-pakulski
Copy link
Contributor

Opened a pull request, created a solution locally to connect to my company confluence cloud;

#38

@Roey7
Copy link
Contributor

Roey7 commented Mar 22, 2023

Solved, thanks @bryan-pakulski

@Roey7 Roey7 closed this as completed Mar 22, 2023
@Roey7 Roey7 added the feature label Mar 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants