Re #8708 - Improved generate_pkcs_identity tests in such way that the identity's friendlyName attribute is now checked
Re #8708 - Changed the behaviour of the generate_pkcs_identity method in the CryptographyService that now does not use the -CAfile argument when the passed chain of trust is empty
Added a unit test verifying that the changed method works as expected when empty chain of trust is passed
Re #8708 - Implemented a new method in the CryptographyService that allows the caller to create a PKCS12 identity of a certificate and it's chain of trust
Covered the new method with unit tests.
Re #8585 - Fixed an issue where required extensions based on cert. usages were not present in the generated certificate
Created an utility that converts usages to extension configuration linesDefined which extension field flags are required for certain usages
Re #8575 - Renamed some variable names in create_crt_test.py
Re #8575 - Added unit tests verifying that serial number is correctly set when creating a certificate
Renamed some create_crt_test.py tests.
Re #8575 - Added unit tests verifying that serial number is set when creating a self signed certificate
Re #8571 - CertificateService tests
Re #8571 - certificate_service.py revocation support end tests
Re #8573 - Added some CertificateService tests and improved CryptographyService tests of methods that extract public keys
Re #8573 - Improved testing of extract_public_key_from_certificate and extract_public_key_from_private_key methods
Re #8573 - Implemented extract_public_key_from_certificate
Re #8573 - Changed extract_public_key method in such way that it now extracts a public key from a private key instead of a certificate
Re #8573 - Implemented extract_public_key method that allows the caller to extract a public key from a certificate
Re #8472 - Added a parameter to the craete_sscrt method in CryptographyService in order to be able to specify tha number of days for which the generated certificate will be valid.
Re #8472 - Improved SQL connection/cursor fixtures in such way that connection to DB happens only once per test module