-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
KeyStoreConfiguration loaded too late in bootstrap #762
Comments
I think this is related to #760 |
Sorry I've been on holiday. Is this included in the released version 1.3.2? |
@spencergibb I tried with 1.3.3.BUILD-SNAPSHOT. Doesn't work for me. |
Of course I’ll do it. 1.3.3-BUILD-SNAPSHOT is correct? |
yes, thanks |
@spencergibb I created a small sample demonstrating the issue. One part is the ConfigServer and one the ConfigClient. If you start both and open http://localhost:8080/test you should get "goodpassword" as a result. Hope this helps. If you need any further information feel free to contact anytime. |
|
So the solution here is to note that for config server
|
Costed few hours to point out it's caused by recent changes after upgrading to Dalston.SR4. Pls update this IMPORTANT note in doc. |
After updating to the latest 1.3.2 release we found out our ConfigServer isn't decrypting {cipher} values anymore.
After digging deep into the ConfigServer I noticed that the KeyStoreConfiguration is loaded after the EncryptorConfiguration.
This results in an SingleTextEncryptorLocator (with a NoOpTextEncryptor) being used instead of the desired KeyStoreTextEncryptorLocator.
I've been able to workaround it moving the encrypt.key-store.location property from the application.ym to the bootstrap.yml.
There are two possible solutions for this:
The text was updated successfully, but these errors were encountered: