🏴High
High Security Configuration
For the high security configuration of your project, you need to utilize both the secret_key from the software and a secret_key from an account, either yours or another staff member's, who has a group with the permission 'dbb.admin.request.validation'. You can find your secret_key in the 'https://your-site.com/settings' section under 'secret_key'.
It's important to note that if the secret_key is changed, software instances associated with the old secret_key will cease to function as they won't be able to verify the user's account. The secret_key serves the crucial purpose of verifying licenses and, soon, will be utilized for additional security measures within the software.
To enable validations for software instances in your project, you must ensure that both the software's secret_key and the account's secret_key with the appropriate permission are correctly configured. If the security configuration is changed from high to normal and existing software instances are already set up with the high security mode, you'll need to adjust the configuration accordingly.
To set the security state to high, simply modify the following line in your configuration file:
Set the value to 2 to enable the high security mode. Depending on your requirements, you can adjust this value accordingly to ensure the desired level of security.
This comprehensive security setup ensures robust validation for software instances within your project, enhancing overall security and safeguarding against unauthorized access or modifications.
Done.
Regards, Vuhp 📀
Last updated