Versions Compared

Old Version 17

changes.mady.by.user Fiona Sargeant

Saved on

compared with

New Version 18

changes.mady.by.user Fiona Sargeant

Saved on

Key

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

PhixFlow Ltd. is pleased to announce the release of PhixFlow 8.2.9. This page describes the improvements and fixes in this version. This minor release includes essential fixes.

Installing or Upgrading to PhixFlow Version 8.2.9

To install a new PhixFlow instance:

  1. Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies.   
  2. Follow the instructions in Installing PhixFlow.


Panel
borderColor#7da054
titleColorwhite
titleBGColor#7da054
borderStylesolid
titleSections on this page

Table of Contents
indent12px
stylenone


To upgrade an existing PhixFlow instance: 
  1. Check System Requirements and Compatibility for changes to the system requirements or supported database versions. For example, you may need to upgrade your database or Java version.
  2. Ensure you have a backup of the database before upgrading PhixFlow.

  3. Follow the Upgrading PhixFlow steps. It is important to complete Step 8, in which you apply any Special Upgrade Instructions for all the intermediate releases between your current version and the version to which you are upgrading.

  4. After upgrading, we recommend you republish the PhixFlow data as described in Step 10 of Upgrading PhixFlow.

Info
titleSpecial Instructions


Excerpt

Create new phixflow configuration files

You must create new version of $webapp/WEB-INF/classes/phixflow-login.xml 
To do this:

  1. Rename your existing configuration file, for example by adding a .bak suffix.
  2. Follow the Install the PhixFlow Webapp instructions for creating a new file from the.example file provided. 
  3. Copy the individual values from your existing configuration file and paste them into the new file.
    Avoid copying entire XML blocks into your new configuration files, as you may overwrite a section of the configuration file that PhixFlow needs.

SAML configuration 
Anchor
saml
saml

Note

The following changes are only required if you use SAML to authenticate users. If you do not, please ignore this section.

If Tomcat is not already configured to do so, set it to use HTTPS and the secure flag on session cookies; see Install Tomcat.

Configure phixflow-login.xml to uncomment <prop key="JSESSIONID">None</prop>

Expand
titleSee example


Code Block
<bean id="sameSiteCookieFilter"
  class="com.accipia.centerview.web.filter.SameSiteCookieFilter">
  <property name="cookies">
    <props>
      <!-- The following line must be uncommented to allow SAML login -->
      <prop key="JSESSIONID">None</prop>
    </props>
  </property>
</bean>




Improvements

DEV-7793  SAML authentication now requires HTTPS; see SAML Configuration upgrade instructions, above.
In addition, you can now configure SAML Single Logout, in which the SAML identity provider is notified of user logout.  To configure single logout, update the phixflow-login.xml attribute map to add <property name="authenticationOnly" value="true" />. 

Tip

Configure single logout to stop PhixFlow incorrectly showing users the message "You are not allowed to access...".

DEV-7823  You can now select and copy text from error and warning messages.

Bug Fixes

DEV-7937  For HTTP collectors and exporters, PhixFlow no longer reports warnings if the charset is not specified on the request or response.

DEV-7867   The options for background filters now correctly include the Ignore case tick box.

DEV-7947  PhixFlow will now only connect to an FTP Site when the Enabled property is ticked.