Skip to main content

Encrypting stored passwords in spring web application

We take security very seriously and have taken steps to harden our services so if some one has ssh access to the box he wont be able to read the files but the webapp has to be able to read the spring config which has passwords to database so we need to protect it from any file download vulnerability.

So the plan was to encrypt passwords stored in spring files and decrypt it at runtime. As we had to decrypt the passwords back this has to be a symmetric encryption but with salt.  After doing some research I found jasypt library that would be able to do this. The steps I followed were:

1) move all passwords to a separate  file called as XXX_passwords.properties
2)changed spring xml to use property placeholders like ${mysql.user.password}.
3) added spring beans to load the password and decrypt them using the ENV variable ENCRYPTION_PASSWORD and added two jars to class path jasypt-1.9.1.jar and jasypt-spring31-1.9.1.jar

    <bean id="encryptablePropertyPlaceholderConfigurer" class="org.jasypt.spring31.properties.EncryptablePropertyPlaceholderConfigurer">
       <constructor-arg ref="configurationEncryptor" />
       <property name="location" value="classpath:xxx_passwords.properties" />
    </bean>
    <bean id="configurationEncryptor" class="org.jasypt.encryption.pbe.StandardPBEStringEncryptor">
       <property name="config" ref="environmentVariablesConfiguration" />
    </bean>
    <bean id="environmentVariablesConfiguration"
          class="org.jasypt.encryption.pbe.config.EnvironmentStringPBEConfig">
       <property name="algorithm" value="PBEWithMD5AndDES" />
       <property name="passwordEnvName" value="ENCRYPTION_PASSWORD" />
    </bean>
4)Wrote a sample property file encoder that will take a normal file and encode the passwords.
public class PPFileEncoder {
    public static void main(String[] args) throws Exception {
        String filePath = args[0];
        File file = new File(filePath);
        if (!file.exists()) {
            System.out.println("File " + filePath + " doesnt exits");
        }
        Properties inputProps = new Properties();
        FileReader reader = new FileReader(filePath);
        inputProps.load(reader);
        reader.close();
        EnvironmentStringPBEConfig config = new EnvironmentStringPBEConfig();
        config.setAlgorithm("PBEWithMD5AndDES");
        config.setPasswordEnvName("ENCRYPTION_PASSWORD");
        StandardPBEStringEncryptor encryptor = new StandardPBEStringEncryptor();
        encryptor.setConfig(config);

        Properties outputProps = new Properties();
        for (Entry entry : inputProps.entrySet()) {
            String key = (String) entry.getKey();
            String value = (String) entry.getValue();
            outputProps.setProperty(key, getEncryptedProperty(encryptor, value));
        }
        FileWriter writer = new FileWriter(file);
        outputProps.store(writer, "Encrypted file");
        writer.close();
    }

    private static String getEncryptedProperty(StandardPBEStringEncryptor encryptor, String value) {
        if (value == null || value.trim().startsWith("ENC(")) {
            return value;
        } else {
            return "ENC(" + encryptor.encrypt(value) + ")";
        }
    }
}

5)Changed install process to encrypt passwords as the last step of install and overwrite the original property file.
6)Now ops will unset the env variable once app is up.

with jasypt if your original file was

mysql.user.password=KalpeshPatel
it would become
mysql.user.password=ENC(B4UEFvcfdIJqavADLRTZqw\=\=)






Good thing about this solution is that devops  can choose a completely random value for ENCRYPTION_PASSWORD variable everytime they install the installer and different value for different machines.

Comments

Post a Comment

Popular posts from this blog

Haproxy and tomcat JSESSIONID

One of the biggest problems I have been trying to solve at our startup is to put our tomcat nodes in HA mode. Right now if a customer comes, he lands on to a node and remains there forever. This has two major issues: 1) We have to overprovision each node with ability to handle worse case capacity. 2) If two or three high profile customers lands on to same node then we need to move them manually. 3) We need to cut over new nodes and we already have over 100+ nodes.  Its a pain managing these nodes and I waste lot of my time in chasing node specific issues. I loath when I know I have to chase this env issue. I really hate human intervention as if it were up to me I would just automate thing and just enjoy the fruits of automation and spend quality time on major issues rather than mundane task,call me lazy but thats a good quality. So Finally now I am at a stage where I can put nodes behing HAProxy in QA env. today we were testing the HA config and first problem I immediat...

Adding Jitter to cache layer

Thundering herd is an issue common to webapp that rely on heavy caching where if lots of items expire at the same time due to a server restart or temporal event, then suddenly lots of calls will go to database at same time. This can even bring down the database in extreme cases. I wont go into much detail but the app need to do two things solve this issue. 1) Add consistent hashing to cache layer : This way when a memcache server is added/removed from the pool, entire cache is not invalidated.  We use memcahe from both python and Java layer and I still have to find a consistent caching solution that is portable across both languages. hash_ring and spymemcached both use different points for server so need to read/test more. 2) Add a jitter to cache or randomise the expiry time: We expire long term cache  records every 8 hours after that key was added and short term cache expiry is 2 hours. As our customers usually comes to work in morning and access the cloud file server it ...

Spring 3.2 quartz 2.1 Jobs added with no trigger must be durable.

I am trying to enable HA on nodes and in that process I found that in a two test node setup a job that has a frequency of 10 sec was running into deadlock. So I tried upgrading from Quartz 1.8 to 2.1 by following the migration guide but I ran into an exception that says "Jobs added with no trigger must be durable.". After looking into spring and Quartz code I figured out that now Quartz is more strict and earlier the scheduler.addJob had a replace parameter which if passed to true would skip the durable check, in latest quartz this is fixed but spring hasnt caught up to this. So what do you do, well I jsut inherited the factory and set durability to true and use that public class DurableJobDetailFactoryBean extends JobDetailFactoryBean {     public DurableJobDetailFactoryBean() {         setDurability(true);     } } and used this instead of JobDetailFactoryBean in the spring bean definition     <bean i...