Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Cloudfront 403 when authenticating custom Jira site in VS Code extension

Indrek July 31, 2023

Upon pressing "Add custom Jira site" and entering our base URL (formatted as https://ourjira.atlassian.net), auth prompt should appear. Instead, we are presented with:

---

403 ERROR

The request could not be satisfied.


Request blocked. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.

---

We were hoping it would resolve itself after some time but unfortunately it hasn't. Neither have we found any references of this issue anywhere.

How could we resolve this issue to use the VS Code extension?

3 answers

1 accepted

0 votes
Answer accepted
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 2, 2023

Hello, 

We had a few additional reports of this behavior example:

But the Dev team identified an error with oAuth on the back end and deployed a fix.  

Can you retry the action and let us know if you are still encountering an error?

Regards,
Earl

Indrek August 3, 2023

It's fixed now! Thank you!

Like • Earl McCutcheon likes this
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 4, 2023

Hi @Indrek ,

Awesome to hear and thank you for confirming!

Regards,
Earl

1 vote
Indrek August 1, 2023

Bump

Michael Evangelista August 1, 2023

double bump

Like • arrigozanette-exorint likes this
0 votes
Kwabena Sarfo
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 1, 2023

I had the same issue and tried logging into VS Code as administrator and it seems to have worked!

Suggest an answer

Log in or Sign up to answer