Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
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

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,560,234
Community Members
 
Community Events
185
Community Groups

XRay Cloud REST API authentication

Edited
Anuraag K B
Anuraag K B Sep 30, 2022

Following the XRay documentation https://docs.getxray.app/display/XRAYCLOUD/Global+Settings%3A+API+Keys, I understand the authentication is based on POST request made to https://xray.cloud.getxray.app/api/v1/authenticate with the API key. 

Considering we generated an API key (Client Id and secret) via Jira server J1, is there any REST endpoint which could verify if the API key indeed belongs to server J1?

Answer
Watch
Like Be the first to like this
326 views

1 answer

0 votes
Stefan Salzl
Stefan Salzl
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Become a leader
Oct 03, 2022

Hi @Anuraag K B 

the authenticate endpoint generates a tocken (out of the provided ClientID & secret). Those information belongs to a specified user in Jira.

I can´t follow your information/question regarding "J1". What exactly is "server J1" and what would you like to verify?

Best
Stefan

View More Comments
Anuraag K B
Anuraag K B Oct 03, 2022

Hi @Stefan Salzl 

Assuming the client id and secret has been generated from a jira cloud instance www.dev.atlassian.net.

Suppose I have these details with me, as a developer I want to validate if the client Id belongs to www.dev.atlassian.net. Would this be possible?

Like
Stefan Salzl
Stefan Salzl
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Become a leader
Oct 03, 2022

Please appologize but I´m still not getting it =S

What is the use case behind it? The ID & secret belong to a specific user within a specific jira instance (eg. dev.atlassian.net). The easiest way to check the authentication is to run a GET call against the API of the mentioned instance with the generated token.

Best
Stefan

Like
Stefan Salzl
Stefan Salzl
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Become a leader
Oct 17, 2022

Hi @Anuraag K B ,

any feedback regarding this case?

Best
Stefan

Like
Reply

Suggest an answer

Log in or Sign up to answer
Product apps
Apps & Integrations
TAGS
AUG Leaders

Atlassian Community Events

See all events