ERROR 1819 (HY000): Your password does not satisfy the current policy requirements

This error usually pops up when you try to grant permissions on your database in MySQL.

In this case, you have two options.

Option 1:

Change your password so that it satisfies the current policy requirements in your MySQL installation.

You can check what conditions are required by executing the bellow command on the terminal where MySQL is running.

SHOW VARIABLES LIKE 'validate_password%';

It will list down a table like this,

Option 2 :

Set the password policy level lower.

For example, you can change the allowed password length using the below command. You also can do this for the fields shown in the image above.

SET GLOBAL validate_password_length = 6;

Cheers!

Comments

The JAR/ZIP file (...) seems corrupted, error: zip file is empty during maven build

You can easily solve this problem in 2 steps. Delete the file given in (...) this path, which is given in the error trace. Build the project again using mvn clean install . Cheers!

How to connect my database instance with elastic beanstalk instance in AWS?

If you have deployed your web application in Elastic Beanstalk in AWS and now you need to connect a database to this instance, and your database is actually residing in a different instance, how can you actually connect them? It's easy with Elastic Beanstalk. I will explain an example scenario that I used for connecting my elastic beanstalk web application with another instance containing my MongoDB database. By looking at this, you can customize as per your need. Don't worry. This is easy. :) The only things you need here are the details about the 1. Database name that you need to connect to. Ex:- "myDB" 2. Port at which the database instance is listening. EX:- In the case of MongoDB, the listening port is 27017 3. Host name of your database instance. EX:- Like localhost, in this case, it will be the Public DNS of your database instance 4. The password of your database if exists. First these details need to be set as environment variables in Elastic Be

How to import the Public Certificate of one WSO2 product to the trust store of another?

To demonstrate this point, I will use the 2 products WSO2 API Manager 2.1.0 (referred as APIM from here onwards) and WSO2 Enterprise Integrator 6.1.1 (referred as EI from here onwards). When using EI as the Business Process Server during configuration of Workflows in APIM, one step to perform is to import the public certificate of EI to the truststore of APIM [1]. So now let's see how this can be done. Step 1: Go to <EI_HOME>/repository/resources/security/ folder and execute the following keytool command. This command is used to export the public certificate of EI as a certificate file called wso2carbon.cer. Since the default keystore in EI is wso2carbon.jks, we have specified it as the keystore and the default alias is wso2carbon. Provide wso2carbon as the keystore password when prompted as it is the default password. After executing the above command from within the security folder in EI, you will see that a file with the name of wso2carbon.cer is created

TechFacts

Search This Blog