Polarity Server 5.4.0
Prior to updating to any version of Polarity Server 5.4 please ensure that all of your integrations are running the latest version. Integrations that have not been updated may not be compatible with Polarity Server 5.4+.
When updating integrations please keep in mind that any custom types that were manually added to the integration will be lost. Prior to updating, be sure to have a copy of any custom type regular expressions so they can be re-added after the update.
Polarity 5.4+ allows adding these custom types directly through the Data Types page on the integration settings page. Once on Polarity 5.4+, future integration updates will not reset your custom types.
About Latest Version
The latest 5.4.0 release adds in some great new features and functionality for users! We have added the ability to consolidate Errors into a single page for admins and users, as well as added the ability for admins to add in custom entity types from the UI versus having to update them on the backend. Enabling a much more seamless administrative experince for integrations. As always for more information on Errors and Custom Types, please see the Polarity Web release docs.
Single Pane for Error Management
The server added the ability for users to be able to see their errors as well as for there to be a single view for errors. Allowing admins to be able to quickly take action on errors and clear them out if needed. It also allows for users for the first time to see their errors.
Adding Custom Types through UI
Adding custom types to integrations is one of the biggest abilities our integration framework enables. It allows for any type of information to be looked up in different tools. However with the enablement of our integration store adding a custom type has become a little bit harder since the work takes place on the backend server, causing friction when Polarity publishes a new version of an integration which will lead to the over writing of an integration.
However we have now added the ability for admins to quickly add a custom type to integrations that support it right through the UI. Allowing for quick setup and time to value for different tools.
Server User Permissions Update
As a part of the new 5.4.0 release we have added in a new user that will own all of the polarity files on the server. This change was added in to address the issue of customers not being able to run docker as root. As a part of the upgrade the permissions will attempt to get set. If you run into issues during the upgrade please see the troubleshooting section below or reach out to us at [email protected].
Issues Addressed
Fixed issue when looking up more than 2 entities with spaces on web search
Addresses issue with web search parser when looking up defanged entities
Added ability to rate limit emails
Increased integration timeouts to 60 seconds versus 30 seconds
Added environment variable for admins to disable integration store
Added ability to change and edit email templates
Fixed issue with lookup pagination
Troubleshooting Upgrade to Latest 5.4 Version
Permission Issues
After upgrading to V5.4 and the server will not start you might see an error like the following :
:cacertfile either does not exist, or the application does not have permission to access itThis is due to a permission not getting set during the upgrade process. The fix is fairly straight forward as all you will need to do is run the following script to force set the permissions:
bin/polarity docker-set-permissionsImproperly Referenced `tls-ca-bundle.pem` file
If you notice the following error in your server logs then you may need to update your docker-compose.ymlfile to remove the POLARITY_TLS_CA_PATH environment variable:
Kernel pid terminated (application_controller)
({application_start_failure,polarity,{{shutdown,{failed_to_start_child,'Elixir.PolarityWeb.Endpoint',
{#{'__exception__' => true,'__struct__' => 'Elixir.ArgumentError',message =>
<<"could not start Cowboy2 adapter, the file /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem required by SSL's :cacertfile either does not exist,
or the application does not have permission to access it">>},If you see the above error, open your docker-compose.ymlfile located at /app/docker-compose.ymland look for the following line within the appservice:
environment:
- POLARITY_TLS_CA_PATH=/etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pemIf you see this line, you should delete the environment and POLARITY_TLS_CA_PATH line and then restart your containers.
cd /app && ./down.sh && ./up.shLast updated