Last Delivery was not successful. Not Authorized

[mattuuh7]

got the below message:
Last Delivery was not successful. Not Authorized
Any idea what the problem is? I used the token created in Asana and use it in the github repo settings

[npanchaud]

Same problem here. I was wondering if it had something to do with the different email addresses I used between Asana and GitHub.

[AlokBansal8]

Same problem. By the way I use different email ids for both services.

[abhimskywalker]

+1
And yes I too use different emails for both.

+1
and different emails

[abhimskywalker]

Ok, so I just noticed the syntax of key being added here:

heroku config:add ASANA_USERS='[{"username":"GitHubUsername1", "key":"XXXXXXXX.XXXXXXXXXXXXXXXXXX"}, {"username":"GitHubUsername2", "key":"XXXXXXXX.XXXXXXXXXXXXXXXXXX"}]'

I was trying to use the Personal Access Tokens from the Asana's My Profile Settings > Apps section.
But this seems like format of the API key.

Asana notes on this API key:

*API Key*
Asana has an API which allows integration with external applications. Applications that do not use Asana Connect use this key for authentication. 

@mattuuh7 @npanchaud @AlokBansal8 @olharsaude
Can you guys also once confirm if using this API key works out fine for you? And if you were originally using this Personal Access Tokens as well like me for this?

[marcboscher]

API keys are actually deprecated and on the way out.
If some of you would like a deeper integration, we built an Asana-GitHub sync service at http://unito.io . Still in private beta, but we invite users on the same or next day usually. We're a couple of weeks from public beta.

@abhimskywalker, using the "API key" works fine!

Thank you for the help!

[mattuuh7]

@marcboscher I can still use personal access token and can see that the test payload succeeded. But still not able to get proper sync up on the message. Might this be internal firewall setup you have seen before?

[marcboscher]

sorry @mattuuh7 , can't really help you with this project (I actually build the http://unito.io alternative). I don't think personal access tokens behave the same way as API keys.

Here's the link to the Asana article foretelling the end-of-life of API keys:
https://asana.com/developers/feed/api-key-deprecation

[mattuuh7]

Thanks. Will take a look. I am going to close the ticket.

Matt Chen

On Oct 19, 2015, at 17:22, Marc Boscher notifications@github.com wrote:

sorry @mattuuh7 , can't really help you with this project (I actually build the http://unito.io alternative). I don't think personal access tokens behave the same way as API keys.

Here's the link to the Asana article foretelling the end-of-life of API keys:
https://asana.com/developers/feed/api-key-deprecation

—
Reply to this email directly or view it on GitHub.