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,628
Community Members
 
Community Events
176
Community Groups

Jira jwt installed but sharedSecret is not returned

Hello,

I created an atlassian connect addon in my atlassian DEV environement.

I added an installed callback to the addon descriptor, the callback is used to get and save the JSON payload (security context).

I installed the addon and everything is working fine.

the only issue is that when I checked the JSON payload returned by the atlassian product (jira) I found that the 'sharedSecret' is missing from the JSON object.

The JSON payload is looks like this

{"key":"key","clientKey":"xxxxxxxx","publicKey":"xxxxxxxxx","baseUrl":"https://xxx.atlassian.net","productType":"jira","description":"xxx ","eventType":"enabled"}

 

It's normal? Or have I forgotten something?

 

Thank you.

1 comment

Hi,

I finally find the cause of the issue described above. On my addon descriptor the installed and enabled callbacks are the same so when I install the addon both callbacks are called and the payload of the last callback (enabled) is saved. Knowing that the sharedSecret is not returned on the enabled callback this is why I did find it on the JSON object.

 

Thx

Comment

Log in or Sign up to comment