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

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.

Atlassian Community about banner
4,456,929
Community Members
 
Community Events
176
Community Groups

JSM API - Oauth2 and service-to-service

Hi,

I am new to JSM and trying to do som sync and automation with Jira and our other systems.

It might be because I am trying out Atlassian Access but when I try to authenticate with the base64 API key, I get the error that basic auth is deprecated. Okay fair enough Oauth is better and more secure.

However the access code flow does not support service-to-service.

How have you guys tackled this? 

1 answer

1 accepted

1 vote
Answer accepted

Hm, from what I know Basic Auth with Password is deprecated but Basic auth with an api key should still work, I usually get the deprecation message when there is an error in the header (specificly the b64 part or the keyword). Did you just provide the b64 API key or did you provide the b64ed email:apiKey string? I've also seen people use the Bearer keyword rather than the Basic keyword. In full you should have something along the lines of:

Authorization: Basic {b64(userEmail:apiKey)}

Hope this helps. Feel free to let me know if you run into any problems.

Greetings 
Gideon

You were absolutely right. I fu**ed up the header. Thanks! 

No problem - been there done that and also saw way to many people throw the towel at this exact point. It's a common problem with an absolutely unhelpful error message.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events