...
In third steps Netconf-pnp-Simulator is Connected over TLS to SDNC-ODL and Validation is carried out to find if connection in properly made.
TC ID | Test Case Name | Test Case Description | Expected Result | Test Status |
---|
T01 | Test SDNC Keystore | Checking ODL Keystore after SDNC Installation. This check is basically conducted to validate Static Certificates (Certificates share by Netopeer2 for TLS connection) and Private Key is insatalled in ODL KeyStore. | PASS. HTTP/1.1 |
202200 | |
T02 | Test SDNC PNF Mount | Checking PNF if Mount after SDNC Installation. This testcase is carried out in two parts. - First step is adding PNF in SDNC-ODL, check is carreid out to find if the Node addition was successful.
- Second step is trying to get the Node configuration stored in SDNC-ODL, which can only be there after PNF is successfully added to SDNC0ODL, there after if GET configuration is successful testcase is marked passes..
| PASS. HTTP/1.1 |
202200 | |
T03 | Test SDNC Delete PNF Mount | Checking PNF mount Delete from SDNC. In this testcase PNF is delted from SDNC-ODL, along with Clearing SDNC-ODL KeyStore. | PASS. HTTP/1.1 |
202FAILHealth Check AAF CertService | Checking AAF CertService if its Up and Running to carry on further tests. | PASS, HTTP/1.1 |
401 | Reload AAF CertService Configuration | Checking Reload of Configuration : Cofiguration is reloaded in AAF Certservice Container and validated if the action was succesful. | PASS |
FAIL 401 | Check AAF CertService Application is Ready | Check if AAF CertService is Up and ready after configuration reload.
| PASS |
FAIL 401FAIL | Check AAF CertService Client Successfully Creates Keystore and Truststore for SDNC | Checking if AAF CertService Successfully able to create X509 Certificate for SDNC. EJBCA community version is used as External Certification Authority. Test case has four parts: - Run AAF Certservice Client Container with Enviroment details for SDNC, a valid CSR env file is inputed based on which X509 Certs, Private kay is generated by AAF Certservice continer.
- Once the Keystore.jks/truststore.jks file retrived both jks files are validated with the passphrase if they can be opened or not.
- Keystore.jks/truststore.jks files are uploaded in SDNC container and installCerts.py script is executed for uploading Certificate/Private key in SDNC-ODL keystore/truststore.
- AAF Certservice Client Container is deleted, results of all four steps are validated and if passed testcase is marked successful.
| PASS , HTTP/1.1 200 | |
T08 | Check SDNC-ODL Certificate Installation in Keystore | Checking ODL Keystore after keystore/truststore installation in SDNC-ODL. This check is basically conducted to validate Static Certificates (Certificates share by Netopeer2 for TLS connection) and Private Key is insatalled in ODL KeyStore. | PASS , HTTP/1.1 |
401200 | |
T09 | Check AAF CertService Client Successfully Creates Keystore and Truststore for Netconf-pnp-simulator | Checking if AAF CertService Successfully able to create X509 Certificate for Netconf-Pnp-Simulator. EJBCA community version is used as External Certification Authority. Test case has four parts: - Run AAF Certservice Client Container with Enviroment details for Netconf-Pnp-Simulator, a valid CSR env file is inputed based on which X509 Certs, Private kay is generated by AAF Certservice continer.
- Once the Keystore.jks/truststore.jks file retrived both jks files are validated with the passphrase if they can be opened or not.
- Keystore.jks/truststore.jks files are converted to Server_key.pem, Server_cert.pem, Ca.pem uploaded in Netconf-Pnp-Simulator container and reconfigure-tls.sh script is executed to reconfigure Certificates on Simulator.
- AAF Certservice Client Container is deleted, results of all four steps are validated and if passed testcase is marked successful.
| PASS , HTTP/1.1 200 | |
T10 | Check SDNC-ODL Netconf-Pnp-Simulatore TLS Connection Establishment | Checking PNF if Mount after SDNC Installation. This testcase is carried out in two parts. - First step is adding PNF in SDNC-ODL, check is carreid out to find if the Node addition was successful.
- Second step is trying to get the Node configuration stored in SDNC-ODL, which can only be there after PNF is successfully added to SDNC0ODL, there after if GET configuration is successful testcase is marked passes..
| PASS , HTTP/1.1 200 | |