Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.106/11/2019Eric McDonaldInitial Draft



Table of Contents


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.


Info
titleCONNECT 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

Info
titleImport 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. 

...

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 
Enterprise

(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


BA, IO

BA, IO

BSA, IO, R, P

B, A, IO

...

  • 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/ImprovementSummary
Security Enhancements

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-341

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-1722

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2346

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2365

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2379

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2399

Performance Enhancements

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-1776

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2089

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2355

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2370

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2422

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2434

Multi Certificates Support

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2017

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2375

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2378

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2381

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2383

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2384

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2385

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2386

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2387

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2390

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2393

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2398

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2400

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2404

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2418

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2419

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2423

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2424

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2425

Wiki Consolidation

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2366

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2388

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2394

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2456

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2467

Admin GUI analysis and cleanup

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-1805

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-1808

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-1885

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2219

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2238

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2347

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2361

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2367

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2368

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2372

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2373

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2374

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2376

Certificate Manager upgrades

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-1917

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2282

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2364

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2437

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2440

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2442

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2446

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2463

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2471

Non-labelled Tasks

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-1578

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-1761

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-1779

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-1807

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-1811

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2328

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2369

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2377

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2396

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2397

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2405

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2409

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2415

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2426

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2432

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2435

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2436

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2438

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2439

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2450

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2457

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2460

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2461

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2475

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2476

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2477

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2478

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2479

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2480

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2481

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2482

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2483

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2486

Other

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-1853

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-1941

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2176

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2208

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2362

Jira Legacy
serverSystem JIRA
serverId6628e6d3-9f37-37e9-8471-2574f58dea1e
keyCONN-2462


Known Issues


Issue
Garbage Collection (GC) exceptions may occur if CONNECT is undeployed and re-deployed without a server restart in between


...