Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

SSP v2.6.0 General Release Announcement

 

To be released at the end of October

Release Highlights

  • Add the Watch Student feature
  • Add bulk actions for Caseload and Search Results (IE: email, export, change program status)
  • New Early Alert Reports
  • Significant Report fixes

 

There are no external database schema changes in this release

Fresh Installation Instructions

See SSP v2.6.0 Installation Instructions

Upgrade Instructions

Upgrading Source Code Forks

See SSP Source Code Upgrade Process

Additional Upgrade Steps

 

It is important to first follow the steps in the Release Notes for v2.5.1 and v2.5.2.

The SSP development team is not aware of any SSP deployments integrated with CAS, but this release includes two security-related patch sets specifically targeted at CAS integrations:

  • SSP-2721 - Scrubs certain CAS-specific request parameters. The changes and effects are detailed in the uPortal project.  No work should be required to enable the patch, but you may want to review that document to better understand the CAS-related configuration changes included in this release.
  • SSP-2724 - Works around what amounts to a CAS-specific session hijacking vulnerability. The changes and effects are detailed in the uPortal project and the <platform-src>/uportal-war/src/main/resources/properties/security.properties file includes greatly expanded comments describing recommended configuration changes. You will likely want to review the email thread and changes to that file whether or not you use CAS. The new defaults may interfere with your existing authentication provider integrations, especially AD/LDAP. SSP-specific details below.

 

1 - Cleanup-up potentially corrupt Maven repo dependencies

SSP-2817 made additional changes to the SSP-Platform ant build script to try to work around continued problems with corrupt Maven dependency downloads. Deployers clean out possibly corrupt dependency downloads before updating SSP and/or Platform build to v2.6.0.  The Maven repo base is where the .M2 directory exists (IE env variable = MAVEN_HOME)

  • Unix/Linux
    • rm -rf <repo-base>/net/sf/ehcache
rm -rf <repo-base>/org/jasig/cas/client
  • Windows
    • delete folder <repo-base>/net/sf/ehcache
    • delete folder <repo-base>/org/jasig/cas/client

 

2 -Update to java 1.7

Java 1.7 is now required and the only version of java that SSP will use.  Once the code branch has been pulled into the local repository, the Platform API must be built prior to deploying SSP Platform as shown below:

cd <SSP-Platform source>/uportal-java-api
mvn clean install

 

3 - 

 

4 - 

5 - 

v2.6.0 JIRA Issues

Bugs

Improvements and New Features

 

 

 

 

  • No labels