Before installation, make sure your system meets all the requirements.
CredoID installer might not start if there are "pending" Windows updates. Make sure you have latest Windows updates installed.
Required option to install main CredoID component as a Windows service.
Check this option if you want PostgreSQL database server installed.
Do not select this option if you are going to use your own PostgreSQL server.
Please read license terms before proceeding next.
Change installation location. By default it will be installed in
CredoID v4.8.x and earlier versions use Microsoft SQL Server as main database. Versions 4.9.x and above use PostgreSQL.
If you're updating from an older version, you can still use Microsoft SQL Server until July 31, 2023. At this date support for MS SQL will be discontinued. Read more.
C:\Program Files\PostgreSQL\14 is selected by default.
C:\Program Files\PostgreSQL\14\data is selected by default.
CredoIDPassword1 is set by default.
If you decide to change password for your database superuser in this step, you will have to update your password during the first launch of CredoID.
5432 is selected by default.
C – the default Locale.
The C locale, also known as the POSIX locale, is the POSIX system default locale for all POSIX-compliant systems. The Oracle Solaris operating system is a POSIX system. The Single UNIX Specification, Version 3, defines the C locale.
If you changed your superuser password during step 5 of PostgreSQL setup - password authentication will fail during your first launch. All you have to do is update the password field and click Update settings.
After succesful installation/update you will be greeted with login screen.
Default credentials are:
It is highly recommended to change operator password immediately after first launch.
If you have chosen to install only service part and use your own database, then DB setup screen will be shown.
PostgreSQL database setup:
5432 is used.
CREATEDB server role is required when starting fresh.
While updates are generally safe and it's very unlikely that it would result in data loss, it's your responsibility to have a proper backup of your database before performing an update. Note that it's not possible to go back to a previous version of CredoID once the database schema has been updated.
Please contact us if you want to update from version 2.X or 3.X.
The process of update is very straight forward.