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

Recognize iam auth database login #1574

Closed
kishubhatta opened this issue Jan 17, 2022 · 5 comments
Closed

Recognize iam auth database login #1574

kishubhatta opened this issue Jan 17, 2022 · 5 comments

Comments

@kishubhatta
Copy link

Is this a request for help?: No


Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Version of Helm and Kubernetes: NA

Which chart: jfrog/artifactory

What happened: Unused values can crash the artifactory pod

What you expected to happen: Values not needed are not required

How to reproduce it (as minimally and precisely as possible): Deploy the chart using Google SQL IAM auth

Anything else we need to know:

@peleduri
Copy link

Hi @kishubhatta ,

Can you kindly add some details about your use case and why you are seeking JFrog to implement support for IAM database authentication?

@kishubhatta
Copy link
Author

@peleduri you don't need to support IAM db auth. You only need to gracefully handle the case where the helm value for password is not specified. Currently, the artifactory application simply crashes if one does not specify password value. One needs to set some dummy value, even when using IAM auth and cloud sql proxy sidecar.

@chukka
Copy link
Collaborator

chukka commented May 24, 2022

@kishubhatta can you please share the reproducible steps

@kishubhatta
Copy link
Author

@chukka it is in the description.

@johnjelinek
Copy link

johnjelinek commented Jan 26, 2024

This works already. I'm using a cloud-sql-proxy sidecar and then just passing in db-user (no password) to connect with the IAM GCP service account.

Although, it might be a nice feature to use the CloudSQL JDBC Socket Factory in place of the MySQL driver. No sidecar needed then.

@gitta-jfrog gitta-jfrog closed this as not planned Won't fix, can't repro, duplicate, stale Aug 11, 2024
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

5 participants