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

[FeatureRequest]-Choice of using IAM and IBM Cloud Identity #147

Open
maverickash8889 opened this issue Jan 22, 2019 · 2 comments
Open

[FeatureRequest]-Choice of using IAM and IBM Cloud Identity #147

maverickash8889 opened this issue Jan 22, 2019 · 2 comments

Comments

@maverickash8889
Copy link

Hi All,

Submitting a feature request for upgrading repo to support IAM way of authenticating services. The current implementation used in samples uses UserName and Passwords(IBM Cloud Identity) mechanism for authentication. With Oct 2018 press release! IBM suggests moving all services from cloud foundry to resource groups which supports IAM. We need to update the samples and middleware to accommodate both ways of authentication.

@jfmartinez
Copy link
Contributor

@maverickash8889 hey, thanks for bring this up.

You can use an IAM API key authentication with environment variables, in your docker deploy.yaml file, configure the following environment variables with your API key information and token service provider URL.

  • Watson Assistant:
      WATSON_CONVERSATION_APIKEY=YOUR_API_KEY
      WATSON_CONVERSATION_TOKEN_SERVICE_PROVIDER_URL=https://iam.bluemix.net/identity/token
  • Speech to Text:
      WATSON_STT_APIKEY=YOUR_API_KEY
      WATSON_STT_TOKEN_SERVICE_PROVIDER_URL=https://iam.bluemix.net/identity/token
  • Text to Speech:
      WATSON_TTS_APIKEY=YOUR_API_KEY
      WATSON_TTS_TOKEN_SERVICE_PROVIDER_URL=https://iam.bluemix.net/identity/token

More info on authentication: https://www.ibm.com/support/knowledgecenter/SS4U29/authentication.html

@maverickash8889
Copy link
Author

@jfmartinez I have submitted Pull Request (#161 ) considering the backward compatibility for the issue. Lemme know if it suffices.

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