Mar 10 - Mar 24, 2014
Executive Summary
Overall Status
Sprint status is excellent. The Product team prioritized the following themes and tasks for Sprint 126 comprising 37 points. These themes included - Release testing and documentation and community support. During the course of the sprint some additional tickets were pulled in totalling 48 points. The team completed all 48 points and released 4.3 on time. Additional tickets included testing on Liberty Profile/Windows, updating regression scripts and additional testing related to concurrent requests from 3.3 to 4.3 gateway.
Burndown
Sprint Themes and related tickets for Sprint 127:
- Community Implementation support
- Worked with the VA team on their 4.2.1 deployment in their development environment
- Supported several meetings including an in-person meeting and email exchanges
- Conducted research on a deployment issue with WebLogic 12c and Windows. The team was able to successfully install on WebLogic 12c (12.1.1) but found an issue with deployment of Connect 4.2.1 on Weblogic 12c (12.1.2) that would need further research(CONN-877)
- Researched and tested a persistent eHealth Exchange certificate issue affecting multiple organizations
- Conducted industry and exchange related research to isolate the issue
- Tested with the VA, Conemaugh and MiHIN
- Discussed and presented findings to Healtheway/Spec Factory
- Documented additional detail about PKI to help the community understand certificate setup and provided troubleshooting guidance.(CONN-884)
- The certificate issue was discovered in the staging environment as a result of some adopters having connectivity issues with their trading partners on the Exchange. Analysis and research conducted by the CONNECT team led to the conclusion that there were two certificates with different roots in use on the Exchange on the staging environments causing trust issues between the partners.
- HealtheWay was able to clarify that the Root CA downloaded from Entrust (SKI: DED9) is being phased out and replaced with the other one (SKI: FF25); members of the eHealth Exchange will eventually have to replace any certificates that were signed before the new Root CA was introduced.
- This issue was documented as a case study that can be used for reference - /wiki/spaces/CONNECTWIKI/pages/11174264
- Troubleshooting information can be found here - eHealth Exchange Certificate chain overview and troubleshooting (CONN-885, CONN-886)
- Support and testing efforts continued with NIST, discussed several topics and compared interpretations of specifications
- Completed testing NIST test cases for SOAP transport/Document Submission (CONN-882)
- Tested DIL test for RDR test case(CONN-876)
- Document Database configuration (CONN-849/CONN-888)
- Worked with the VA team on their 4.2.1 deployment in their development environment
- 4.3 Release
- Bug fixes affecting release
- Fix secured entity interfaces for Query for Documents and Retrieve Documents services.(CONN-908,CONN-909,CONN-892)
- Fix QD and RD adapters for On Demand and Stable retrieval (CONN-896)
- Research issue when there was a replay attack fault returned when concurrent requests are sent from a 3.x gateway to a 4.x gateway(CONN-859)
- Documented analysis and possible options
- Disabled CXF replay detection as the CXF algorithm is not mature enough (CONN-903)
- Remove all HIEM tables and related database scripts(CONN-887)
- Began install testing on Release 4.3
- Created 4.3 RC1 tag (CONN-883)
- Binary Install testing on GlassFish(Windows) (CONN-780)
- Source Install testing on GlassFish(Windows) (CONN-781)
- Binary Install testing on WebLogic12c(Linux) (CONN-785)
- Binary Install testing on JBoss(Linux) (CONN-790)
- Source Install testing on JBoss(Linux) (CONN-791)
- Source Install testing on WebSphere 8.5(Liberty Profile)(Linux) (CONN-789) – Work started but not completed this sprint. Moved to next sprint.
- Release Documentation
- Review and update System Architecture Documentation (CONN-873)
- Document Release test plan for 4.3 (CONN-815) – Draft ready for review but not completed this sprint. Move to next sprint.
- Bug fixes affecting release
- Security scan analysis and resolution (CONN-911, CONN-
- Fixed issue - Privilege Management: Default Function or Procedure Rights(CONN-936)
- Re-ran Fortify scan on GA to ensure that there were no new issues because of replay attack fix, or XML Entity Injection fixes.
- Reviewed the response from DoD and ensured all items mentioned have been addressed in code or documentation.
- Sent DoD newly created artifacts for the last scan run on GA - FPR file and Fortify scan report.
- Created a ticket for next sprint to follow-up with DoD after they have reviewed the artifacts.
- Ongoing Custodial Agent Duties
- CONNECT 4 Blogs and Forum posts
JIRA Planning Board of Committed User Stories for Sprint 127
Completed Tickets
Related Files
- Release 4.3 artrifacts -