2.3.1 PIV Middleware Test Configuration
All changes in this version
Title
PIV Middleware Test Configuration
Control changed
Before · SP 800-85A-2
The middleware test configuration is used to test a vendor’s middleware software application that implements the PIV client API and generates the appropriate commands in the PIV card command interface (refer to Table A-1 for mapping between the client API and card command interface). The middleware test configuration is depicted in Figure 3.
Figure 3: Middleware Test Configuration PIV Client Application Programming Interface
PIV Card Command Calls
Card Reader Driver
Card Reader
PIV Card Application
PIV Data Model PIV Card Command Interface PIV MIDDLEWARE – Implementation Under Test
Smart Card Reader
PIV CARD (SP 800-73-3 Conformant) Test Toolkit Application
OR
Dual Interface Card Reader
PIV Card Emulator (SP 800-73-3 Conformant) PIV Card
Host PC The following list shows the test system components included in this configuration: A test toolkit application software
Vendor provided PIV Middleware, which is the subject of this test (also called as Implementation Under Test or IUT) and
One of the following combinations:
Contact and contactless smart card readers or a dual interface reader together with
A PIN input mechanism together with
A dual interface FIPS 201 conformant PIV Card loaded with “SP 800-73-3 Part 2 conformant PIV Card Application” (for definition refer to section 7.2)
OR
A PIV card emulator that emulates the behavior of a PIV Card Application
A printer for reporting and documenting the test results
The test toolkit application software resides on the Test Computer, and facilitates the execution and management of both test suites explained in Section 3. For the PIV Middleware Test, the test system (Figure 2) will be configured so that the vendor provided PIV Middleware under test is also installed on the Test Computer and interacts with the FIPS 201 conformant test cards via the card reader(s).
After · SP 800-85A-4
The middleware test configuration is used to test a vendor’s middleware software application that implements the PIV client API and generates the appropriate commands in the PIV card command interface (refer to Table A-1 for mapping between the client API and card command interface). The middleware test configuration is depicted in Figure 3 .
Figure 3: Middleware Test Configuration Dual Interface Card Reader PIV Card Test
PIV Client Application Programming Interface
PIV Card Command Calls
Card Reader Driver
Card Reader
PIV Card Application
PIV Data Model PIV Card Command Interface PIV MIDDLEWARE – Implementation Under Test Host PC
Smart Card Reader
PIV CARD (SP 800-73-3800-73-4 Conformant) Test Toolkit Application
OR
DualInterface Card ReaderPIV Card Emulator (SP 800-73-3800-73-4 Conformant) PIV CardThe following list shows the test system components included in this configuration:
Host PC A+ testTest toolkit application software. + Vendor provided PIV Middleware, which is the subject of this test (also called asthe Implementationimplementation Underunder Testtest or IUT) and One of the following combinations: + Contact and contactless smart card readers or a dual interface reader together with + A PIN input mechanism together with + A dual interface FIPS 201 conformant PIV Card loaded with “ SP 800-73-3800-73-4 Part 2 conformant PIV Card Application” (for definition referRefer to sectionSection 7.2 for definition). or + A PIV card emulator that emulates the behavior of a PIV Card Application
OR.
A printer for reporting and documenting the testresultsThe test toolkit application software resides on the Testtest Computer,computer and facilitates the execution and management of both test suites explained in Section 3 . For the PIV Middleware Test, the test system ( Figure 2 ) will be configured so that the vendor provided PIV Middleware under test is also installed on the Testtest Computercomputer and interacts with the FIPSSP 201800-73-4 conformant test cards via the card reader(s).