Release Management
Space shortcuts
Space Tools

Versions Compared

Key

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

html-text
<!DOCTYPE html>
<html>

<head>
    <title>i2b2 1.7.10 Release Notes</title>
    <meta charset="UTF-8">
    <meta name="description" content="The release notes for version 1.7.10 of the i2b2 Software" />
    <meta name="keywords" content="i2b2, release, 1.7, 1.7.03, 1.7.03a, 1.7.04. 1.7.05, 1.7.06, 1.7.07, 1.7.07b, 1.7.08, 1.7.08a, 1.7.09, 1.7.09a, 1.7.09b, 1.7.09c, 1.7.10" />
    <link rel="stylesheet" type="text/css" media="all" href="/stylesheets/i2b2-wiki.css" />
</head>

<body>
</body>

</html>

i2b2 Release 1.7.10
Anchor
releaseNote-1710
releaseNote-1710

Release Date: April 27, 2018

Release Summary
Anchor
releaseNoteSum-1710
releaseNoteSum-1710

Release 1.7.10 contains many new enhancements to the i2b2 kernel, many of which improve the security around signing into the i2b2 Web Client. We have included some Auditing features like logging all successful and attempted logins into the i2b2 Web Client or keeping a log of all the Admin functions performed with the Admin Module.

 

Installation Notes
Anchor
releaseNoteNewInstall-1710
releaseNoteNewInstall-1710

This release note applies to you if you are upgrading your i2b2 to 1.7.10 from and earlier 1.7.xx version of the i2b2 software. Please see the Upgrade Notes section for any information that is specific to the upgrade process.

If you are installing a new instance of the i2b2 we recommend you refer to the i2b2 Installation Guide found on the i2b2 Community Wiki. This documentation will guide you through the entire installation process. If you run into issues or have questions you can reach out to the community by joining and emailing the google group called i2b2 Install Help.

 

SHRINE Networks
Anchor
releaseNoteShrineApprvl-1710
releaseNoteShrineApprvl-1710

 

Warning
titleWarning

Release 1.7.10 has not been tested within a SHRINE network. Therefore, i2b2 Release 1.7.10 should not be installed within a SHRINE network. It can be installed independently of SHRINE. However because it has not been tested with SHRINE we can not guarantee all of the new enhancements will continue to work correctly when implemented within a SHRINE environment.

html-text
<html>
<body>
    <!-- Add the following section once SHRINE approves this release; may need to update the SHRINE version -->
    <!--
    <h2 id="rel1709cshrineApprvl">SHRINE Approval</h2>
    <p class="shrineApprvTxt">
        <img class="shrineApprvlImg" src="https://community.i2b2.org/wiki/download/attachments/15729710/shrineApprvl_v1-22-08.png" width="57" height="57" alt="Shrine Approval"><i>SHRINE Release 1.22.8</i> has been tested with <i>i2b2 1.7.09c Release</i> and has been <b>approved</b> by the SHRINE Team</p>
-->
</body>
</html>
 

 

Upgrade Notes
Anchor
releaseNoteUpgrade-1710
releaseNoteUpgrade-1710

The following i2b2 components contain changes in release 1.7.10.

    • i2b2 Database
    • i2b2 Server (kernel)
    • i2b2 Web Client

The list of changes made can be found in the change summary

Now provide an upgrade path for those sites that do not want to do a whole new install of the i2b2 server. provide just the JAR / war files

page that contains all the upgrade information is: Upgrade to latest version

 

 

Database Changes

 

 

 

Change Summary - i2b2 Kernel (Core Software) - Release 1.7.10
Anchor
releaseNoteChgSumCore-1710
releaseNoteChgSumCore-1710

Section

New Features and Improvements

Additional information about each of these features can be found in the Details about New Features in Release 1.7.10 section located after the Change Summary section for the Web Client.

 

 

 

New Features and Improvements

Additional information about each of these features can be found in the Details about New Features in Release 1.7.10 section located after the Change Summary section for the Web Client.

 

Jira
serveri2b2 JIRA
columnskey,type,summary
maximumIssues1000
jqlQueryproject = CORE AND issuetype in (Improvement, "New Feature", Story, Task, Sub-Task) AND fixVersion = 1.7.10 AND labels = wikirelease
serverId6e4599d0-bdbc-37f8-9067-5f0befc0ec6c

Bug Fixes

Jira
serveri2b2 JIRA
columnskey,type,summary
maximumIssues1000
jqlQueryproject = CORE AND issuetype = Bug AND fixVersion = 1.7.10 AND labels = wikirelease
serverId6e4599d0-bdbc-37f8-9067-5f0befc0ec6c

 

Change Summary - i2b2 Web Client Software - Release 1.7.10
Anchor
releaseNoteChgSumWeb-1710
releaseNoteChgSumWeb-1710

New Features and Improvements

Additional information about each of these features can be found in the Details about New Features in Release 1.7.10 section located after this section.

 

Jira
serveri2b2 JIRA
columnskey,type,summary
maximumIssues1000
jqlQueryproject = WEBCLIENT AND issuetype in (Improvement, "New Feature", Story, Task, Sub-Task) AND fixVersion = 1.7.10 AND labels = wikirelease
serverId6e4599d0-bdbc-37f8-9067-5f0befc0ec6c

Bug Fixes

Jira
serveri2b2 JIRA
columnskey,type,summary
maximumIssues1000
jqlQueryproject = WEBCLIENT AND issuetype = Bug AND fixVersion = 1.7.10 AND labels = wikirelease
serverId6e4599d0-bdbc-37f8-9067-5f0befc0ec6c

 

Details about New Features in Release 1.7.10
Anchor
releaseNoteFeatureDetails-1710
releaseNoteFeatureDetails-1710

Many improvements in 1.7.10; grouped into 4 categories

Miscellaneous improvements

 

Logging improvements

 

Password management improvements

 

Query improvements

 

Miscellaneous improvements
Anchor
releaseNoteFeatureDetailsMisc-1710
releaseNoteFeatureDetailsMisc-1710

Single sign-on

Separate Admin install no longer needed

i2b2 Administrators now login from the i2b2 Web Client

 

Improve datasource validations

•  Validate database connection
•   If connection in pool goes bad will not continue to use

 

Logging improvements
Anchor
releaseNoteFeatureDetailsLog-1710
releaseNoteFeatureDetailsLog-1710

 

•Logon Auditing
–Successful and failed login attempts will be logged in PM_USER_LOGIN table
•Log Admin functions
–Actions done within Admin will be logged in PM_USER_LOGIN table
–The service called & user_id that triggered it will be logged

Password management improvements
Anchor
releaseNoteFeatureDetailsPwdMgmt-1710
releaseNoteFeatureDetailsPwdMgmt-1710

Total of 4 new features

1.Account lockout
2.Mandatory password change
3.Prevent repeat password
4.Enforce complex passwords

 

Account Lockout

•Account lockout threshold and wait time is defined by the site Admin.
•Users are locked-out when the defined number of failed attempts has been reached.
•Once locked, the user must wait a preset period of time.
•User receives lockout message

The threshold & wait time are defined in 2 new global parameters.

Section
Column

PM_LOCKED_MAX_COUNT

•Threshold for failed sign-in  attempts
Column

PM_LOCKED_WAIT_TIME

•Number of minutes account is locked before user can sign in

 

 

 

Mandatory Password Change

•Require users to change passwords
•i2b2 Admins control how often (interval)
•Change password window will open when password expired
•1 new Global parameter
•1 new User parameter

Quick Summary of Password expiration process

1.New global parameter is set & feature turned on
2.ALL user passwords are expired
3.User attempts to sign in; prompted to change password
4.Enter new password & successfully sign into Web Client
5.Using value in global parameter, system calculates next expiration date for user & adds user parameter with that date to the correct table.

 

Section
Column

Global Parameter

PM_EXPIRED_PASSWORD

•Turns the feature on
•Define password change interval

Column

User Parameter

PM_EXPIRED_PASSWORD

•Added when pw changed 1st time
•Date password will expire for user

 

 

 

Warning

Feature is turned on for ALL users including service accounts.

To prevent service accounts from expiring you need to add the user parameter as soon as the feature is turned on or before it is turned on.

Set the expiration date for a date far in the future…

 

Prevent repeat password

•New password can’t be same as current password
•Warning message displayed
INSERT PASSWORD SAME IMAGE

Complex Passwords

Enforce complex passwords

•i2b2 Admins define requirements for complexity
•Enforced when users change passwords
•Warning message if don’t meet requirements
•New global parameter
INSERT REQUIREMENTS IMAGE

Global Parameter: PM_COMPLEX_PASSWORD

•Each requirement as an independent variable however they are concatenated and stored as a single “value” in the table.

 

 

Query improvements
Anchor
releaseNoteFeatureDetailsQryImprov-1710
releaseNoteFeatureDetailsQryImprov-1710

 

 

 


 

Include Page
1.7.09c Release Notes
1.7.09c Release Notes