Answered by:
TranslateArray not working anymore (error: No bearer information found in the token)

Question
-
I started getting this error (No bearer information found in the token) for new Bing account I signed up for.
I am using the php code listed at http://msdn.microsoft.com/en-us/library/ff512422.aspx which was working fine before.
Anyone else having the same issue?
Tuesday, June 12, 2012 12:15 PM
Answers
-
Can you let me know on which line you get the error? Is this when you are calling the AdmAuthentication service to get the token, or is it when you're passing the token to the translator API?
I saw this thread from someone that had a similar issue and the same failure code -- and they were working behind a proxy that changed some of the headers to cause it. Could that be the case here? http://social.msdn.microsoft.com/Forums/en-US/windowsazuresecurity/thread/749596ea-0dc1-4cd1-b125-fbbf17d0b73f
- Proposed as answer by Laurence Moroney Tuesday, June 19, 2012 2:42 PM
- Marked as answer by Microsoft TranslatorMicrosoft employee Monday, July 20, 2015 7:01 PM
Thursday, June 14, 2012 4:45 PM
All replies
-
It looks like it is not able to get the access token.
I am getting
{"error":"invalid_request","error_description":"ACS90007: Request method not allowed.
Wednesday, June 13, 2012 12:21 PM -
The Bing App ID methodology has been deprecated. You'll need to sign up with the Windows Azure Data market for a (free) translator account -- details here:
http://blogs.msdn.com/b/translation/p/gettingstarted1.aspx
Then, to use translation in PHP, you could do something like this:
http://blogs.msdn.com/b/translation/p/phptranslator.aspx
- Proposed as answer by Laurence Moroney Wednesday, June 13, 2012 3:08 PM
Wednesday, June 13, 2012 3:08 PM -
Thanks for the reply, but I am aware of the new change, and if you look at the URL I posted, it has the same example as the page you linked (your link is likely a copy of the official msdn link I posted).
It was working just fine for a couple of weeks, and not just stopped authenticating.
Wednesday, June 13, 2012 10:18 PM -
Can you let me know on which line you get the error? Is this when you are calling the AdmAuthentication service to get the token, or is it when you're passing the token to the translator API?
I saw this thread from someone that had a similar issue and the same failure code -- and they were working behind a proxy that changed some of the headers to cause it. Could that be the case here? http://social.msdn.microsoft.com/Forums/en-US/windowsazuresecurity/thread/749596ea-0dc1-4cd1-b125-fbbf17d0b73f
- Proposed as answer by Laurence Moroney Tuesday, June 19, 2012 2:42 PM
- Marked as answer by Microsoft TranslatorMicrosoft employee Monday, July 20, 2015 7:01 PM
Thursday, June 14, 2012 4:45 PM -
Thanks Laurence, it may have been the issue, I was abroad and now that I'm back home it seems to be working fine.
Monday, June 18, 2012 4:22 PM -
Awesome! Glad it's working now!Thursday, July 26, 2012 2:05 PM
-
I occur similar issue like this.
But I try to change token information as follow:
header["Authorization"] = "Bearer " + token
and it will work.
Request Header Description Authorization
Required. Specify the the value of access_token in format "Bearer" + " " + Access Token Value
Refer spec in https://msdn.microsoft.com/en-us/library/ff512422.aspx
- Edited by Evan Lin Monday, July 13, 2015 8:49 AM
Monday, July 13, 2015 8:19 AM