-
Notifications
You must be signed in to change notification settings - Fork 1.3k
POST to /encrypt always comes back with KeyNotInstalledException #767
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
Comments
Yes this is a known issue in |
@ryanjbaxter Thanks for the tip :-) |
@ryanjbaxter Was this fixed in
|
@Fydon unfortunately we did not release spring cloud config for Dalston.SR3, it was a mistake on our part. The fix will be included in Dalston.SR4, sorry about that. |
…add config server encryption module.
just wanted to add that this is still an issue with Dalston.SR4. I've downgraded to Camden.SR7 for now. This also fixed another problem of mine. While using a keystore and {cipher}'d passwords, config server was returning the hash as the password, simply removing the {cipher} prefix. |
@Dr4K4n This issue was fixed in Spring Cloud Config |
I've setup i little example project to illustrate the problem, simply build the application with maven und test with test.sh. On my machine it works with Dalston.SR4, but not with Camden.SR7. |
I did some more testing with different Versions of Spring Cloud Config |
I've further investigated, the underlying problem seems to be that the |
Needs to be in bootstrap.properties |
@spencergibb thanks. |
if you write in the application yaml/properties, get this error. So, a simple solution is just creating bootstrap yaml/properties file. |
Hi everyone I have the same problem using java 11 and spring-cloud.version 2020.0.0-M5 is there any alternative version that works |
Try 20.0.0 for now. |
Hi,
I'm using the Spring Cloud Config (Dalston.SR2) to use a git repo to get the application properties. All works fine till i try and use the /encrypt endpoint. With Dalston.SR2, the call to /encrypt ALWAYS comes back with a
I've made sure that the environment variable ENCRYPT_KEY is set properly.
If I change the version to Camden.SR5. The same configuration works fine and I can use both the /encrypt & /decrypt endpoints. I'm not sure if there's anything else that I need to do apart from
Here's a copy of my pom xml.
Any help is greatly appreciated. :-)
Cheers
Kunal
The text was updated successfully, but these errors were encountered: