Disclaimer
All capabilities designed, developed, and tested during the CONNECT 5.3 project time frame are described below. Known defects in the product are listed below as well as in the CONNECT Issue Tracker tool. Defects which may occur within the product may not be limited to these issues. This product and the accompanying written materials are provided "as is" without warranty or guarantee of any kind. Furthermore, no representations made regarding the use, or the results of use, of the product in terms of correctness, accuracy, reliability, currency, or otherwise is warranted or guaranteed. The Federal Health Architecture (FHA) shall not be held liable for any direct, indirect, consequential, or incidental damages arising out of the use of or the inability to use this product.
Version History
Version# | Date | Modified By | Description of Modification |
|---|---|---|---|
| 0.1 | 06/11/2019 | Eric McDonald | Initial Draft |
Summary
Release 5.3 continues to build on the functionality and architecture introduced in Release 4.0 through additional features, selected improvements, and bug fixes.
We encourage the CONNECT community to upgrade to Release 5.3 to take advantage of these updates. Details can be found in the following subsections:
Enhancements and Announcements
Configurable Secure Hash Algorithm (SHA) 256
CONNECT provides a basic feature to more easily select SHA versions to use for initiating and accepting requests. Available SHA versions are based on the versions supported by CXF and OpenSAML.
CONNECT is not yet intended for multi-exchange support
The ability to download, store and process data from multiple healthcare provider directories and the proof of concept to authenticate with multiple certificates on one CONNECT instance have been completed with the release of CONNECT 5.3. However, the messaging and SAML services are still strictly intended for NwHIN exchange. Additional code enhancements are required for complete multi-exchange implementation.
Multi certificates support that includes Server Name Indication (SNI)
An assumption is made that CONNECT implementers participating in multiple exchanges will obtain separate SSL certificates for each exchange, thereby requiring the management of multiple certificates.
Import Wizard in Admin GUI
Import Wizard
While replacing the self-sign certificates with the CA certificates imported using Import Wizard, user must exercise caution and verify, before replacing, if they have imported the root, intermediate(s) and leaf certificates.
Import Wizard interface partly automates the process of creating new certificate and importing CA certs into CONNECT configuration.
The Import Wizard can:
- Create a new certificate or
- Generate Certificate Signing Request (CSR) for an existing certificate or
- Import SSL Certificate
EventLogging updates for Admin GUI
User can search Audit and Failure events through Logging GUI without having to log into the database to track events.
Certificate Manager Updates
- simplify the import or remove the certificate in the TrustStore.
Common types and Webservices cleanup for improved performance
Common types and Webservices have been cleaned up to minimize resource requirements for CONNECT.
All properties related to SAML have been moved to saml.properties
All SAML properties have been centralized to the saml.properties file.
Release Testing
Release testing for 5.3 consisted of installation testing, interoperability testing, regression testing, and new feature testing.
A full cycle of release testing is performed on each release candidate prior to making it generally available.
When a release candidate passed all testing phases it is designated as ready for release and made generally available to the community.
The table below describes the environments that will be utilized for testing.
Testing summary by Operating system and application server for 5.3
App Server | WebSphere (Version 8.5.5.3) | WebLogic12c (Version 12.2.1) | WildFly (Version 8.2.1) | JBoss (Version EAP 7) | |
|---|---|---|---|---|---|
OS | |||||
Windows 64 | B,S,A | ||||
Linux 64 | B, A, IO | B, A, IO | B, S, A, IO, R, P | B, A, IO |
Legend:
- S – Source Code Installation and Validation
- B – Binary Installation and Validation
- R – Regression
- IO – Interoperability
- A – Admin GUI (IE v11, Chrome)
- P – Performance Test
JIRA Trackers for Work Accomplished for Release 5.3
The following tables display issues resolved or tasks addressed during the release of CONNECT 5.3. The details of these issues can be found in the CONNECT Issue Tracker, linked to in the tables below.
Features and improvements
| Feature/Improvement | Summary |
|---|---|
| Security Enhancements | |
| Performance Enhancements | |
| Multi Certificates Support | CONN-2017 - Getting issue details... STATUS CONN-2375 - Getting issue details... STATUS CONN-2378 - Getting issue details... STATUS CONN-2381 - Getting issue details... STATUS CONN-2383 - Getting issue details... STATUS CONN-2384 - Getting issue details... STATUS CONN-2385 - Getting issue details... STATUS CONN-2386 - Getting issue details... STATUS CONN-2387 - Getting issue details... STATUS CONN-2390 - Getting issue details... STATUS CONN-2393 - Getting issue details... STATUS CONN-2398 - Getting issue details... STATUS CONN-2400 - Getting issue details... STATUS CONN-2404 - Getting issue details... STATUS CONN-2418 - Getting issue details... STATUS CONN-2419 - Getting issue details... STATUS CONN-2423 - Getting issue details... STATUS CONN-2424 - Getting issue details... STATUS CONN-2425 - Getting issue details... STATUS |
| Wiki Consolidation | |
| Admin GUI analysis and cleanup | CONN-1805 - Getting issue details... STATUS CONN-1808 - Getting issue details... STATUS CONN-1885 - Getting issue details... STATUS CONN-2219 - Getting issue details... STATUS CONN-2238 - Getting issue details... STATUS CONN-2347 - Getting issue details... STATUS CONN-2361 - Getting issue details... STATUS CONN-2367 - Getting issue details... STATUS CONN-2368 - Getting issue details... STATUS CONN-2372 - Getting issue details... STATUS CONN-2373 - Getting issue details... STATUS CONN-2374 - Getting issue details... STATUS CONN-2376 - Getting issue details... STATUS |
| Certificate Manager upgrades | CONN-1917 - Getting issue details... STATUS CONN-2282 - Getting issue details... STATUS CONN-2364 - Getting issue details... STATUS CONN-2437 - Getting issue details... STATUS CONN-2440 - Getting issue details... STATUS CONN-2442 - Getting issue details... STATUS CONN-2446 - Getting issue details... STATUS CONN-2463 - Getting issue details... STATUS CONN-2471 - Getting issue details... STATUS |
| Non-labelled Tasks | CONN-1578 - Getting issue details... STATUS CONN-1761 - Getting issue details... STATUS CONN-1779 - Getting issue details... STATUS CONN-1807 - Getting issue details... STATUS CONN-1811 - Getting issue details... STATUS CONN-2328 - Getting issue details... STATUS CONN-2369 - Getting issue details... STATUS CONN-2377 - Getting issue details... STATUS CONN-2396 - Getting issue details... STATUS CONN-2397 - Getting issue details... STATUS CONN-2405 - Getting issue details... STATUS CONN-2409 - Getting issue details... STATUS CONN-2415 - Getting issue details... STATUS CONN-2426 - Getting issue details... STATUS CONN-2432 - Getting issue details... STATUS CONN-2435 - Getting issue details... STATUS CONN-2436 - Getting issue details... STATUS CONN-2438 - Getting issue details... STATUS CONN-2439 - Getting issue details... STATUS CONN-2450 - Getting issue details... STATUS CONN-2457 - Getting issue details... STATUS CONN-2460 - Getting issue details... STATUS CONN-2461 - Getting issue details... STATUS CONN-2475 - Getting issue details... STATUS CONN-2476 - Getting issue details... STATUS CONN-2477 - Getting issue details... STATUS CONN-2478 - Getting issue details... STATUS CONN-2479 - Getting issue details... STATUS CONN-2480 - Getting issue details... STATUS CONN-2481 - Getting issue details... STATUS CONN-2482 - Getting issue details... STATUS CONN-2483 - Getting issue details... STATUS CONN-2486 - Getting issue details... STATUS |
| Other | CONN-1853 - Getting issue details... STATUS CONN-1941 - Getting issue details... STATUS CONN-2176 - Getting issue details... STATUS CONN-2208 - Getting issue details... STATUS CONN-2362 - Getting issue details... STATUS CONN-2462 - Getting issue details... STATUS |
Known Issues
Issue |
|---|
| Garbage Collection (GC) exceptions may occur if CONNECT is undeployed and re-deployed without a server restart in between |