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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

All microservices should authenticate themselves when using mongo database #2380

Closed
difince opened this issue Feb 19, 2020 · 2 comments
Closed
Assignees
Labels
bug Something isn't working geneva security-services
Projects

Comments

@difince
Copy link
Member

difince commented Feb 19, 2020

馃悶 Bug Report

All microservices should authenticate themselves when using mongo database no matter if they are started up via docker or via snap. Once issue edgexfoundry/docker-edgex-mongo#77 is fixed (mongo is started with enabled access control), services started up using configuration.toml files that are directly under /res directory will got authentication exception when manipulating the database.

Affected Services

All microservices that use mongo database and are run usually locally or via snap

  • core-command
  • core-data
  • core-metadata
  • support-logging
  • support-notifications
  • support-sheduler
The issue is located in these files:

Is this a regression?

-

Description and Minimal Reproduction

All /edgex-go/cmd/*/res/configuration.toml files have empty Password and Username filed under [Databases]
Example with edgex-go/cmd/metadata/configuration.tolm file

[Databases]
[Databases.Primary]
Host = 'localhost'
Name = 'metadata'
Password = ''
Port = 27017
Username = ''
Timeout = 5000
Type = 'mongodb'

Username and Password files need to be updated accordingly.

馃敟 Exception or Error

Currently there is no exception, but once the mongo get started with enabled access control, all microservice will need to authenticate.




馃實 Your Environment

Deployment Environment:

EdgeX Version:

Anything else relevant?

@difince difince added the bug Something isn't working label Feb 19, 2020
@difince difince added this to New Issues in Security WG via automation Feb 19, 2020
@difince difince self-assigned this Feb 19, 2020
@bnevis-i bnevis-i moved this from New Issues to In progress in Security WG Feb 28, 2020
@bnevis-i
Copy link
Collaborator

@difince What is left to do here?

@difince
Copy link
Member Author

difince commented Mar 2, 2020

The issue was fixed by PR #2381

@difince difince closed this as completed Mar 2, 2020
Security WG automation moved this from In progress to Done Mar 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working geneva security-services
Projects
Security WG
  
Done
Development

No branches or pull requests

3 participants