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

Next challenges

Recent achievements

Recognition

  • Give kudos
  • My kudos

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Post a message to a chat slack bearer token auth failure

Hi All,

 

followed all the steps here for generating a bot auht token from the resource below.

https://scriptrunner.adaptavist.com/latest/jira/builtin-scripts.html

However it always says token authentication failed - new to this and cant figure out what I might be missing, 

I am on an internally hosted Jira instance and have looked the through the bot scope just in case that was a factor. Any ideas?

3 answers

I'm having the same issue.

Can we bump this?

Hi Govind

After you add the "bot scope" permission and re-install your slack app it will show the required auth key at the top of the slack "OAuth and permissions" page under the heading "Bot User OAuth Access Token"

This token, when added as the Bearer Token in the scriptrunner "Post a message to Slack"/"Post to chat Service" built-in script will cause the built-in script page to reload and then it should show your available slack channels in the "Target room" dropdown.

If you see the built-in script display a loading animation and then immediately say "Token authentication failed!" in the "Target room" dropdown, the reason should be shown in the altassian-jira.log file if you turn on debug level logging as shown here.

One thing to watch out for is if you have your browser set to automatically fill in password and username fields for some websites, this can sometimes replace the token you just entered after the page reloads and then cause the authentication to fail. So make sure you have this disabled or try an incognito browser when you are setting up this built-in script.

 

Regards

Matthew

I fell over a "bug" in the chrome browser.

I entered the bearer token and after that chrome adds into the project field my saved jira login name and overwrites(!) the bearer token with my saved jira password.

Maybe a bug with the field identifiers? I have no other clue why chrome would do sth like that.

Hi Roland

I was not able to get my browsers to auto-fill but I can see the browsers treat the bearer token field as a password field and offers to auto-fill.

I created a feature request here so the developers are aware of the issue and can look into a different method if they feel it works better for users. Feel free to vote if you would like.

Regards

Matthew

Thank you, Matthew! :)

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

5 mobile apps for Jira Cloud to boost productivity

  It’s very important to have access to the workflow process from anywhere. Especially if you manage the work of others. There is no difference whether you’re out of office, or drive a ca...

265 views 2 5
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you