Report Generation for SonarCloud using Bitegarden Report

 

 

 

java -Dsonar.token=SONAR_TOKEN -Dlicense.file=/home/mysupply/Downloads/bitegarden-sonarcloud-report-1.3.4/LICENSE.txt -Dsonar.projectKey=examplecode1_phpbackend -Dsonar.organizationKey=examplecode1  -Dreport.type=0 -jar bitegarden-sonarcloud-report-1.3.4.jar

ERROR for site owner: Invalid domain for site key google recaptcha

 

If you encounter the error message "Invalid domain for site key" when working with Google reCAPTCHA, it typically means that the site key you are using is not associated with the domain or website where you are trying to implement reCAPTCHA.

To resolve this issue, you need to ensure that you have registered the correct domain or website with Google reCAPTCHA and obtained the appropriate site key. Follow these steps to fix the problem:

1. Go to the Google reCAPTCHA admin console: https://www.google.com/recaptcha/admin.
2. Sign in with the Google account that is associated with the reCAPTCHA implementation.
3. If you haven't already done so, register your domain or website by clicking on the "+ Add" button under the "Register a new site" section.
4. Provide the necessary information, including the label for your site and the domain name(s) where reCAPTCHA will be used.
5. Once you have registered your site, you will receive a site key and a secret key.
6. Ensure that you are using the correct site key for the specific domain or website where you are implementing reCAPTCHA. The site key should match the domain you specified during registration.
7. Update your website's code with the correct site key. Double-check that you have entered the site key accurately and without any additional spaces or characters.
8. Save the changes and deploy the updated code to your website.

By following these steps and using the correct site key associated with the domain or website, you should be able to resolve the "Invalid domain for site key" error.

 

 

Add the site key to 

(search for recaptcha)

clients: supplier portal , admin portal , user portal (to their env.docker files)

Add secret key to

server: laravel back-end