4.3.6.3 Login to an OpenCRVS server
Last updated
Last updated
Now that your database is seeded with your users you should be able to browse to OpenCRVS to login.
https://login.<your-domain>
For development & qa environments, your test employees () can log straight into your application with 2FA and notifications disabled and the username and password that exists in the csv.
For staging & production environments, your production National System Administrator employee () must immediately login and change the csv password to a strong, minimum 12 character long password.
Then the user will be logged out and will have to login again with 2FA and notifications enabled.
This is your first test of your SMTP service. The National System Administrator should receive an email containing the 2FA code. Emails can end up in your Spam folder so please check and advise staff accordingly.
Once logged in, the National System Administrator can create team members through the user interface.
If there is an issue and you are not receiving emails, this is a good opportunity to learn about monitoring and debugging your OpenCRVS installation.
To learn more about OpenCRVS monitoring and maintenance, visit the section.
As the SMTP API was configured in the countryconfig service, you can filter the appropriate logs in Kibana in the Observability > Logs > Stream section like so:
As you browse the logs you are looking for 500 errors and you can respond to any SMTP service error messages that you see appropriately. Perhaps you need to change the Github Action secrets. of OpenCRVS will refresh all microservices and so this is required when secrets are updated.