Import from Confluence / Jira - SSO
Hi All,
We have an instance of Confluence and Jira installed on a third-party cloud. Those instances are using our corporate SSO for login.
I've created a Personal Access Token in Confluence.
I'm trying to import some data from Confluence in our YouTrack instance by using my email address and the token. But, I still get http 401.
Is there anything I'm missing?
Thanks!
Please sign in to leave a comment.
Hi!
I'm Sergey from the YouTrack team.
This error indicates that the URL is likely correct, but there's an issue with either a username (email) or token. So firstly, please double check that you entered correct data as described in the doc: https://www.jetbrains.com/help/youtrack/incloud/import-from-confluence.html.
If you're sure that everything is correct, please share the following details:
As this is a public forum, you can always contact us directly via https://youtrack-support.jetbrains.com/hc/en-us/requests/new or youtrack-support@jetbrains.com and share the details there.
Thanks Sergey.
My confluence import has the following settings (I can't post it here or anywhere else, for privacy reasons)
URL: the Confluence URL (https://...)
Username or Email: my email address
Password of Token: the token I've generated in Confluence.
I'm using YouTrack standalone (JAR service install on an AWS EC2 instance).
And, I want to mention this again, in case it was missed: my login on Confluence is exclusively done via SSO to my company.
Here's an excerpt from the import log:
Thanks!
And, if I browse to <URL>/rest/api/space (in Chrome), I do get a JSON with the data.
Thanks for your response.
When you browse in Chrome, you don't pass a token with a username as you need to do in the import setting. In general, YouTrack just takes your entered data and sends a request to the Confluence API.
You can perform a request manually, i.e., via a cURL:
You can check if the request returns any data.
Hi Sergey,
I'm getting the same http401.
And, we're not hosting with Atlassian... We are on a separate provider. (Valiantys)
Thanks for your response.
Well, the API should still be the same, as it's a part of the product.
I then recommend reaching our to your provider and clarify why you can't use the API with your credentials.
Thanks Sergey!