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

Why do I get IllegalArgumentException for rest api call in "enabled" lifecycle method

Recently we have released a new version of our cloud connect add-on and with that, we implemented some business logic in the "enabled" lifecycle method for backward compatibility support.  

This new code invokes a rest api call and retrieves some property values from user jira cloud instance databases.

The rest api call is being failed and return the following error in the event of upgrading already installed add-ons with the new version released.  But this error does not occur for fresh installation and api call returns successful response.

java.lang.IllegalArgumentException: The provided AtlassianHostUser did not specify a user to act as

Can you please provide us the source of the issue and possible resolution for it?

Additional information :

  • In our add-on descriptor, we have defined both "ADMIN" and "ACT_AS_USER" for add-on scopes.
  • We also have a private pre-review version of the add-on for testing purposes and we have tested the above functionality using it successfully. In that case, we always upgraded the add-on by providing the descriptor url using "Add-ons->Manage add-ons->Upload add-on"  button.

Thank you

 

 

 

 

 

 

 

 

 

1 answer

Hello

Did you manage to have an explanation for such a behavior ?

Thanks

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events