Secure Web Fingerprint Transaction (SWFT) 7.2.4 and 7.2.4.1 Release Webinar

1. Secure Web Fingerprint Transaction (SWFT) 7.2.4 and 7.2.4.1 Release Webinar Presented to: SWFT User Community Presented by: SWFT Application and Program Support Team Date: July 2017 • Please mute your phones unless you are asking a question. Please do not use the hold feature.

2. SWFT New Release Webinar Agenda AGENDA: Review SWFT 7.2.4.1 Release notes Review SWFT 7.2.4 Release notes ‹#›

3. SWFT New Release Webinar 7.2.4.1 The following is a list of application changes for all users: • The Account Activity page in Account Management is now displaying the correct paging and total results. • Users will be able to include colons, and semicolons in the filename when uploading an eFP file on the Biometric Upload screen in SWFT without receiving an error. • When uploading eFPs, updating scanner records, running reports in SWFT, or accessing BioSP, the users will be able to include dmdc.mil and osd.mil in their Compatibility View settings and have the ‘Display intranet sites in Compatibility View’ check box checked. • On the Biometric Upload screen, if the user enters the incorrect Org/CAGE Code, an error message ‘Unregistered or Invalid Org/CAGE Code’ will be displayed ‹#›

4. On the Biometric Upload screen, if the user enters the incorrect Org/CAGE Code, an error message ‘Unregistered or Invalid Org/CAGE Code’ will be displayed ‹#›

5. SWFT New Release 7.2.4 Webinar Topics The following is a list of application changes for all users: • On the eFP Preview screen, the Image Capture Equipment (IMA) and CRI fields have been modified. • A Test eFP will be rejected, if the serial number on the eFP does not match a serial number on a scanner registration record within SWFT. • When running the Auto Upload Error Log by Date report, the user will be able to view eFP records based on their permissions. • The Release Notes will be accessible from the Help screen within the SWFT application. • When a user’s account is deactivated, if the user is currently accessing SWFT, the user account will be logged out from the SWFT application at that time. • Adobe Flash Player is no longer needed to upload multiple eFP records into SWFT. The following is a list of application changes for administrative and privileged users: • On the Add Scanner, Edit Scanner and Scanner Detail screens, the device fields have been grouped together. • Device Make and Device Model have been added as search criteria to the Scanner Registration list screen. • The administrative and privileged users will have the ability to modify the scanner serial number, make and model on a scanner record in any status. ‹#›

6. When running the Auto Upload Error Log by Date report, Organization Administrators will only be able to see eFPs within their organization, Site Administrators will only be able to see eFPs within their site and standard users with the Web Enroller permission will only be able to see eFPs they uploaded. Privileged users will be able to view all eFPs on the Auto Upload Error Log by Date report. 6

7. The report screens have been updated with a new look. The Org/CAGE Code dropdown has now been changed from a dropdown to a group box for easier selection. See the Transaction by Status report below for an example of the new Org/CAGE Code selection field. 7

8. On the Biometric Upload screen, the Org/CAGE Code field validation has been modified. If the user enters an incorrect Org/CAGE Code and clicks Browse, the user will receive an ‘Unregistered or Invalid Cage Code’ upload error message. The user will need to enter a valid Org/CAGE Code to complete the eFP upload process. 8

9. On the eFP Preview screen, the Image Capture Equipment (IMA) field has been modified to parse the Make, Model and Serial Number (S/N) and the CRI field was modified to add the SON, SOI and IPAC titles. 9

10. The Release Notes will be accessible from the Help screen within the SWFT application. The Release Notes will no longer be available on the SWFT PSA Website. 10

11. The device fields on the Add Scanner, Edit Scanner and Scanner Detail screens have been moved to group the Device Make, Model and Serial Number together and the Software Vendor, Operating System and TCN together. Administrative and privileged users can also view the last status date change in Scanner Registration for each individual registration record. 11

12. Device Make and Device Model have been added as search criteria to the Scanner Registration search screen. 12

13. Additional Release Features: When the user uploads a Test eFP, if the serial number on the eFP does not match a serial number on a scanner registration record within SWFT, the Test eFP will be rejected. The user will need to correct or add a new scanner registration record in SWFT. Refer to the SWFT Scanner Registration and Configuration guide for additional instructions. If the scanner serial number needs to be corrected on the scanner record in SWFT, the user should contact their Site or Organization Administrator. If the serial number displayed in the IMA field on the eFP Preview screen is non-compliant; all zero’s, unknown, or an invalid serial number, the user will need to contact their device vendor. The administrative and privileged users will have the ability to modify the scanner serial number, make and model on a scanner record in any status. If the scanner needs to be reapproved, the system will move the registration record to the Pending Re-Approval by Registration Authority. When a user’s account is deactivated, if the user is currently accessing SWFT, the user account will be logged out from the SWFT application at that time. Adobe Flash Player will no longer be required when uploading multiple eFPs in the SWFT application from the Biometric Upload screen. 13

14. Additional Release Features: • Each Organization that has a registered scanner approved for production must have at least 1 Organization or Site Administrator assigned to their Organization or Site. If there is an Organization or Site Administrator assigned to the Organization or Site, but the administrative account is inactive, a new administrative account will need to be added. The SWFT team is running compliance reports and if any Organizations are found that do not meet the requirement, the SWFT Coordinators will contact members in the Organization to update this information. • SWFT eFP submissions should match the device Make, Model and serial number be in the registration record within SWFT.  Any device submitting eFPs though SWFT that is not compliant with the requirement could be suspended from operation. 14

15. Q&A Serving Those Who Serve Our Country

16. Resources and Communication Visit the PSA Website to Find Additional Resources: Technical Assistance/PSSAR Submissions/Account Information: dmdc.contactcenter@mail.mil SWFT Coordinator/SWFT Program Manager: dmdc.swft@mail.mil SWFT PSA Information Website: https://dmdc.mil/swftinfo Newsletter PKI Frequently Asked Questions Release Notes Access, Registration, and Test Guide PSSAR, Sample, Instructions, and Checklist The below links are located within the PKI FAQ DoD approved PKI Vendors DoD ECA approved vendors can be found at http://iase.disa.mil/pki/eca/Pages/index.aspx and approved Non-Federal Issuers including all of the Category II listed providers at http://iase.disa.mil/pki-pke/interoperability/Pages/index.aspx. Serving Those Who Serve Our Country