Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

JIRA DVCS Redirect URL Will Not Generate?

Sam Chan
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!
Oct 10, 2023

Trying to integrate GitLab and Jira using Jira DVCS by following Linking GitLab accounts | Administering Jira applications Data Center and Server 9.4 | Atlassian Documentation 

 

I'm stuck at generating a redirect url after populating the authorize endpoint and token endpoint. Following the instructions for authorize endpoint, <Gitlab instance with https:>/oauth/authorize and for token endpoint, <Gitlab instance with https:>/oauth/token

The "generate" button greyed out after I click on it and no redirect url generated. I'm wondering if my Jira instance could be the issue. It's in a test environment using http, not setup for https yet. Could this be the issue?

I looked into the console and saw a 400 error: GET http://jira.instance.com:8080/rest/oauth2-client/latest/config/get-redirect-uri/?authorizationEndpoint=https://gitlab.instance.com/oauth/authorize 400 (Bad Request) 

1 answer

1 accepted

0 votes
Answer accepted
Sam Chan
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!
Oct 10, 2023 • edited

Looking into the dump log, the "{"errors":["Due to security risks OAuth 2 is not allowed with an insecure connection. Please ensure that your server is using HTTPS and that your application base URL is configured appropriately."],"fieldErrors":{}}" 

Haven't tested this using https for my Jira Instance yet but this makes my guess highly probable about needing a https instance for Jira.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events