Table of Contents |
---|
Recommended test case
settset for Switchover
Netcentric usage verification
Test scenarios Netcentric certificates
Nr | Testcase | Expected test result |
1 | Perform an Authentication with the Netcentric BankID which was created before cutover using HA1 (generated code) | Authentication is done with ok result |
2 | Perform an Authentication with the Netcentric BankID which was created before cutover using HA2 (generated code) | Authentication is done with ok result |
3 | Perform Sign with the Netcentric BankID which was created before cutover | Signing is done with ok result |
BIM internet usage verification
Test scenarios BankID on mobile
Nr | Testcase | Expected test result |
1 | Perform an Authentication with a BankID on mobile which was created before cutover | Authentication is done with ok result |
2 | Perform Sign with a BankID on mobile which was created before cutover | Signing is done with ok result |
3 | Perform a Netcentric authentication with BankID on mobile as OTP | Authentication is done with ok result |
BIM extranet usage verification
Test scenarios BankID on mobile certificates (Nettbank)
Nr | Testcase | Expected test result |
1 | Perform an Authentication with a BankID on mobile which was created before cutover | Authentication is done with ok result |
2 | Perform Sign with a BankID on mobile which was created before cutover | Signing is done with ok result |
3 | Perform a Netcentric authentication with BankID on mobile as OTP | Authentication is done with ok result |
Issuing verification
Test scenarios Netcentric certificates created before cutover
Nr | Testcase | Expected test result |
1 | Perform a Suspend on Netcentric BankID which was created before cutover | Verify that the BankID is suspended in RA |
2 | Perform an Revoke on Netcentric BankID which was created before cutover | Verify that the BankID is revoked in RA |
3 | Perform a Renew on Netcentric BankID which was created before cutover. | Verify that the BankID is renewed in RA |
4 | Perform an Authentication with the Netcentric BankID which was Renewed above | Authentication is done with ok result |
5 | Perform a Sign with the Netcentric BankID which was Renewed above | Signing is done with ok result |
6 | Perform an Reissue (order new password) on Netcentric BankID which was created before cutover | Verify that renewal of certificate is ok |
7 | Perform an Authentication on Netcentric BankID which was Reissued above | Authentication is done with ok result |
8 | Perform a Sign with Netcentric BankID which was Reissued above | Signing is done with ok result |
9 | Perform a Reinstate on a certificate which was Suspended before cutover | Certificate was successfully Reinstated and is in Activated status |
10 | Perform an Authentication on Netcentric BankID which was Reinstated above | Authentication is done with ok result |
Test scenarios Netcentric certificates created after cutover
Nr | Testcase | Expected test result |
1 | Perform an Authentication with the Netcentric BankID which was created after cutover | Authentication is done with ok result |
2 | Perform Sign with the Netcentric BankID which was created after cutover | Signing is done with ok result |
3 | Perform a Suspend on Netcentric BankID which was created after cutover | Verify that the BankID is suspended in RA |
4 | Perform a Reinstate on Netcentric BankID which was created after cutover | Verify that the BankID is activated and auth/sign is OK |
5 | Perform an Authentication with Netcentric BankID which was Reinstated above | Authentication is done with ok result |
6 | Perform an Revoke on Netcentric BankID which was created after cutover | Verify that the BankID is revoked in RA |
7 | Perform a Renew on Netcentric BankID which was created after cutover | Verify that the BankID is renewed in RA |
8 | Perform an Authentication with Netcentric BankID which was Renewed above | Authentication is done with ok result |
9 | Perform a Sign with Netcentric BankID which was Renewed above | Signing is done with ok result |
10 | Perform Reissue (order new password) on Netcentric BankID which was created after cutover | Verify that the BankID is renewed in RA |
11 | Perform an Authentication with Netcentric BankID which was Reissued above | Authentication is done with ok result |
12 | Perform a Sign with Netcentric BankID which was Reissued above | Signing is done with ok result |
BankID on mobile certificates
Test scenarios BankID on mobile certificates created before Cutover
When BankID on mobile is renewed, generation of new certificates will be done immediately (requires some process time)
Nr | Testcase | Expected test result |
1 | Perform an Suspend on a BankID on mobile which was created before cutover | Verify that the BankID is suspended in RA |
2 | Perform an Revoke on a BankID om mobile which was created before cutover | Verify that the BankID is revoked in RA |
3 | Perform a Renew on a BankID on mobile which was created before cutover | Verify that the BankID is renewed in RA |
4 | Perform an Authentication with the BankID on mobile which was Renewed above | Authentication is done with ok result |
5 | Perform a Reinstate on a certificate which was Suspended before cutover | Certificate was successfully Reinstated and is in Activated status |
6 | Perform an Authentication with the BankID on mobile which was Reinstated above | Authentication is done with ok result |
Test scenarios BankID on mobile certificates created after cutover
When BankID on mobile is renewed, generation of new certificates will be done immediately (requires some process time)
Nr | Testcase | Expected test result |
1 | Perform an Authentication with a BankID on mobile which was created after cutover | Authentication is done with ok result |
2 | Perform Sign with a BankID on mobile which was created after cutover | Signing is done with ok result |
3 | Perform an Suspend on a BankID on mobile which was created after cutover | Verify that the BankID is suspended in RA |
4 | Perform a Reinstate on a BankID on mobile which was created after cutover | Verify that the BankID is activated and auth/sign is OK |
5 | Perform an Authentication with the BankID on mobile which was Reinstated above | Authentication is done with ok result |
6 | Perform an Revoke on a BankID on mobile which was created after cutover | Verify that the BankID is revoked in RA |
7 | Perform a Renew on a BankID on mobile which was created after cutover. | Verify that the BankID is renewed in RA |
8 | Perform an Authentication with the BankID on mobile which was Renewed above | Authentication is done with ok result |
Renew RA XML or SSL certificate
Renew RA certificate via BankID support portal for production: https://servicedesk.bankidnorge.no/jira/servicedesk/customer/portal/3/create/107
- Customer must create a support case on BankID Support portal
- The support case requires the following information:
- RA SSL Certificate, RA XML Certificate or both
- Details about the expiry date
- Customer Originator (4 digits)
- RA-Name
- Old certificate - Nice to have old information from the old certificates, however not needed as long as they have given information about their Originator and RA-Name.
- RA XML Signing Certificate the customer must come to BankID with an RA request. The request must be done on their system for example through HAT and customer must bring their PrimaryCAO "dongle", upon the visit.
- RA SSL the customer must come to BankID, but do not require any request as BankID has the details and customer must bring their PrimaryCAO "dongle", upon the visit.
- Arrange the meeting details before creating the change, keep in mind that it requires some lead time on the change.
Renew RA certificate via BankID support portal for preproduction: https://servicedesk.bankidnorge.no/jira/servicedesk/customer/portal/1/create/105
- Customer must create a support case on BankID Support Portal
- The support case requires the following information:
- RA SSL Certificate, RA XML Certificate or both
- Details about the expiry date
- Customer Originator (4 digits)
- RA-Name
- Old certificate - Nice to have old information from the old certificates, however not needed as long as they have given information about their Originator and RA-Name.
- RA XML Signing Certificate the customer need to make a RA request. The request must be done on their system for example through HAT.
CA / RA TSP - Overview
(07.10.2020)
View file | ||||
---|---|---|---|---|
|
Key Custodian - Overview
View file | ||||
---|---|---|---|---|
|