Closed frajos100 closed 5 years ago
I can confirm the same LoginFailed error. Just registered F0 service (tried with both Speech (preview) and Custom Speech(preview)) on Azure, tried North Europe and North America token endpoints in the sample app (such as https://northeurope.api.cognitive.microsoft.com/sts/v1.0/issueToken).
I can get the token fine with my key using PowerShell:
$FetchTokenHeader = @{
'Content-type'='application/x-www-form-urlencoded';
'Content-Length'= '0';
'Ocp-Apim-Subscription-Key' = 'MYKEY'
}
$OAuthToken = Invoke-RestMethod -Method POST -Uri https://northeurope.api.cognitive.microsoft.com/sts/v1.0/issueToken -Headers $FetchTokenHeader
# show the token received
$OAuthToken
Is there a workaround for this @frajos100 @jpalo ?
We need to use the Bing Speech API rather than the Azure Speech API.
Are those not 2 totally different things?
For the sample in this GitHub repository we need to use the Bing Speech API key and not the Azure Speech API key.
From the official page, I can not distinguish between Bing and Azure speech API. Can some one help me find out the correct API?
We recommend to use the new Speech Service API. And you can find samples for new Speech Service API here:
In VIsual Studio 2017 getting the error LoginFailed transport error