Yep, you need something like an ${enc:value} and you need to export a seed
value that you can unset later in the karaf start script, but yeah. It works
Sent from my pressure cooker.
> On Nov 5, 2018, at 15:50, Leschke, Scott <[email protected]> wrote:
>
> Thanks for the response.
>
> So just to be clear, I’m correct in thinking that it should work?
>
> From: Johan Edstrom [mailto:[email protected]]
> Sent: Monday, November 05, 2018 4:47 PM
> To: [email protected]
> Subject: Re: Encrypting property values in .cfg files
>
> I think I have that in a Jira someplace, otherwise
> I have basic code for it against an older karaf
>
> Sent from my pressure cooker.
>
> On Nov 5, 2018, at 15:25, Leschke, Scott <[email protected]> wrote:
>
> I’m looking to encrypt passwords the are currently in plaintext in a few of
> my .cfg files. I’ve looked at how to do that and it seemed reasonably
> straightforward although I’ve had some difficulty getting it working. I’m
> wondering if there’s anything that prevents me from just supplying a service
> myself that implements the org.jasypt.encryption.StringEncryptor interface
> rather than using the Karaf jasypt-encryption service.
>
> I’ve tried it but that doesn’t seem to want to work either so I’m wondering
> if there’s a reason it doesn’t.
>
> Scott
>
>
