generated from cyberark/conjur-template
-
Notifications
You must be signed in to change notification settings - Fork 8
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
@ConjurPropertySource Not only applied to the properties of a class. #75
Labels
Comments
bnasslahsen
added a commit
to bnasslahsen/conjur-spring-boot-sdk
that referenced
this issue
Apr 6, 2023
13 tasks
bnasslahsen
added a commit
to bnasslahsen/conjur-spring-boot-sdk
that referenced
this issue
Apr 6, 2023
bnasslahsen
added a commit
to bnasslahsen/conjur-spring-boot-sdk
that referenced
this issue
Apr 6, 2023
bnasslahsen
added a commit
to bnasslahsen/conjur-spring-boot-sdk
that referenced
this issue
Apr 6, 2023
bnasslahsen
added a commit
to bnasslahsen/conjur-spring-boot-sdk
that referenced
this issue
Apr 6, 2023
bnasslahsen
added a commit
to bnasslahsen/conjur-spring-boot-sdk
that referenced
this issue
Apr 7, 2023
bnasslahsen
added a commit
to bnasslahsen/conjur-spring-boot-sdk
that referenced
this issue
Apr 7, 2023
bnasslahsen
added a commit
to bnasslahsen/conjur-spring-boot-sdk
that referenced
this issue
Apr 7, 2023
13 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
The
@ConjurPropertySource
annotation is Not only applied to the properties of a class.It is applied to all the application properties, causing so many calls to conjur.
ConjurPropertySource
configuration.Steps to Reproduce
Expected Results
*Only a single call should be made to the conjur API for retrieving a secret
Actual Results
Too many call are made to conjur for all the application properties, causing performance issues
Reproducible
Version/Tag number
1.0.2
Environment setup
Additional Information
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: