You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Zoltán Umlauf edited this page Feb 1, 2019
·
6 revisions
When creating self signed certificates for testing purposes, you have 3 options to choose from:
Using Keystore Explorer or a similar program
Running the ah_gen_system.sh script
Making a request towards the Certificate Authority Core System (later this will be an internal part of the onboarding procedure)
Using Keystore Explorer
We made a simple video guide for this option. The video description also lists each step.
Running the shell script
If you have a Debian packages installation of the framework already configured, you just simply have to execute the script (see the relevant part of the installation guide) that comes with the installation. The resulting certificate will be in the active user's home folder.
Using the Certificate Authority Core System (BETA)
The provider and consumer client skeletons have a CertificateBootstrapper class, which automatically requests a signed certificate from the Certificate Authority core system, if creating an SSL context failed with the certificates provided in the configuration file.
If you want to use this feature, make sure the cert_authority_url property points to an URL where the CA system is running (e.g. http://127.0.0.1:8458/ca locally), and that the secure_system_name (provider) or consumer_system_name (consumer) property is modified to your application system name. The system name will determine the common name of the certificate!
This process is planned to be automated with the Onboarding core system, meaning the interfaces of the Certificate Authority system will be internal only in the future.