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.

Sign up for GitHub

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

Jump to bottom

[management] manage properly dbname for mongo backend #5836

Closed
leleueri opened this issue Jul 8, 2021 · 0 comments
Closed

[management] manage properly dbname for mongo backend #5836

leleueri opened this issue Jul 8, 2021 · 0 comments
Assignees
@leleueri
Labels
project: AM type: bug
Milestone
AM - 3.5.8

Comments

@leleueri
Copy link
Contributor

leleueri commented Jul 8, 2021 •
edited
Loading

When MongoDB is configured using URI, the Mongo IdentityProvider configured by default use the "gravitee-am" dbname.
If the URI contains another dbname, the Idp will used the default one.

Also, we should manage the case where the URI doesn't contain the DB name
@leleueri leleueri added this to the AM - 3.5.8 milestone Jul 8, 2021
@leleueri leleueri self-assigned this Jul 8, 2021
@leleueri leleueri mentioned this issue Jul 8, 2021
Merged
tcompiegne pushed a commit to gravitee-io/gravitee-access-management that referenced this issue Jul 8, 2021
@leleueri @tcompiegne
fix: initialize DBName from URI if available
72bb242 
fixes gravitee-io/issues#5836
tcompiegne pushed a commit to gravitee-io/gravitee-access-management that referenced this issue Jul 8, 2021
@leleueri @tcompiegne
fix: initialize DBName from URI if available
dfb3b82 
fixes gravitee-io/issues#5836
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@leleueri leleueri

Labels
project: AM type: bug
Projects
None yet
Milestone
AM - 3.5.8
Development

No branches or pull requests
2 participants
@tcompiegne @leleueri