Broadleaf Commerce Discussion Forums

I don't fully understand your question. The OOB Broadleaf implementation stores a password in the BLC_CUSTOMER table already.

You can determine how the password will be hashed by setting the "password.site.encoder" property. In development mode, this is set to a PlaintextPasswordEncoder.

In "production.properties", the OOB implementation sets this to the following:


You could override your production.properties (or common.properties) to use "MD5PasswordEncoder" instead.

Hi Brian,

Thumbs up for your solution,even i was looking for the same.
I also have one doubt, like in the default workflow whenever a user lands on the checkout page, a null entry is made in the "blc_customer" table and if the user walks away from that page without purchasing that null entry persists in the database.

I am sure that in production this could be a serious problem.
Is there any way to stop that null entry??

Thanks

A null entry isn't actually created in the customer table, an anonymous customer entry is created whenever that user adds something to their cart. This is one mechanism to allow insight into such things as cart abandonment rate etc...

However, we do understand in high traffic sites this can cause excess load on your production DB. There is an effort to create a configurable cleanup job to purge abandoned carts and anonymous users.

You can follow the progress here: https://github.com/BroadleafCommerce/Br ... issues/215