search

watson-intu / self

Intu is a Cognitive Embodiment Middleware for AI on the edge.
Other
28 stars 27 forks source link

Support for Identity and Access Management (IAM) #47

Closed daiki-kimura closed 3 years ago

daiki-kimura commented 4 years ago

IBM announced to all Watson users that migration of all Watson services to IAM was required by October 30, 2019

I think we might need to change around these files and related files. https://github.com/watson-intu/cpp-sdk/blob/develop/src/utils/ServiceConfig.h https://github.com/watson-intu/cpp-sdk/blob/develop/src/utils/IService.cpp

Or we might need to change for each service. https://github.com/watson-intu/self-plugins/tree/develop/watson/services

gradybooch commented 4 years ago

Agreed.

Who here is still actively using Intu?

On Oct 7, 2019, at 10:13, Daiki Kimura notifications@github.com wrote:

 IBM announced to all Watson users that migration of all Watson services to IAM was required by October 30, 2019

I think we might need to change around these files and related files. https://github.com/watson-intu/cpp-sdk/blob/develop/src/utils/ServiceConfig.h https://github.com/watson-intu/cpp-sdk/blob/develop/src/utils/IService.cpp

Or we might need to change for each service. https://github.com/watson-intu/self-plugins/tree/develop/watson/services

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

daiki-kimura commented 4 years ago

Thank you.

We are having an active Intu demo with Pepper-robot in THINK Lab at Tokyo. And we (with @takaomoriyama) are trying to tackle this issue. If anyone already tried to solve this issue, please comment at here

takaomoriyama commented 4 years ago

I reviewed documentation of IAM and API specifications of Watson services, and found that we don't need to change any of Intu code. What we need to do is as follows:

  1. For each of existing services, such as STT or TTS, migrate to IAM management by clicking "Migrate" button on the configuration screen of each service.
  2. Read out APIKey for each migrated service.
  3. Specify "apikey" as m_User and the APIKey you got above as m_Password for each service.

That's all.

I confirmed that this worked for Speech-To-Text service on my machine. Please verify.

daiki-kimura commented 4 years ago

Thank you. I understand and verify your steps. I'm gonna test on Pepper during next week about this.

And I feel it is better to rename the m_Password to m_ApiKey , remove the m_User fields for future users, and modify the related parts.

takaomoriyama commented 4 years ago

Ya. Renaming m_Password to m_ApiKey make sense. Please let me know when you confirm on your Pepper. Then I would start working on it.