Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What is categoryID/clientSecret/clientID ? #14

Closed
felixhao28 opened this issue Nov 15, 2016 · 3 comments
Closed

What is categoryID/clientSecret/clientID ? #14

felixhao28 opened this issue Nov 15, 2016 · 3 comments

Comments

@felixhao28
Copy link

When I try to use DocumentTranslatorCmd, it prompts Invalid translation service credentials. Use "DocumentTranslatorCmd setcredentials", or use the Document Translator Settings option.. And DocumentTranslatorCmd setcredentials /? tells me to enter categoryID, clientSecret and clientID. I looked everywhere in my Azure Portal and cannot find those keywords.

I did find Subscription ID and KEY 1 and KEY 2. Are they related?

@felixhao28
Copy link
Author

Alright I got this after I found this document: http://docs.microsofttranslator.com/text-translate.html

clientSecret and clientID are both used to retrieve access tokens. However if you started from this welcome page, you will be prompted to create an Azure Cognitive Services APIs (preview) account and that eventually leads you to Azure Portal, where you don't use clientSecret/clientID but subscription key instead. This article tells you how you get access token with subscription key (either KEY 1 or KEY 2).

In this sense, I feel this demo tool is kind of outdated. I will see if I can manage to make a PR to fix this.

@felixhao28
Copy link
Author

felixhao28 commented Nov 15, 2016

And categoryID is related to a custom model used in https://hub.microsofttranslator.com. It is optional. I figured that out.

felixhao28 added a commit to felixhao28/DocumentTranslator that referenced this issue Nov 16, 2016
@chriswendt1
Copy link
Member

Sorry for being late. Document Translator is now ready to work with an Azure subscription, taking the Key form your resource as authentication. The newest binaries and the branch AzureAuth2 contain the version working with an Azure subscription.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants