- PoolParty Semantic Suite Documentation
- Introduction to PoolParty UnifiedViews
- UnifiedViews 10.1.0 Release Notes
UnifiedViews 10.1.0 Release Notes
08/07/2025
PoolParty UnifiedViews (UV) is a data integration platform designed to manage and automate data processing workflows, particularly for linked data and semantic web applications. It enables users to extract, transform, and load data from various sources into structured formats, making it useful for data publishers and organizations working with complex data pipelines to manage their data in PoolParty.
New Feature: Single Sign-On (SSO) Integration
PoolParty UnifiedViews now supports Single Sign-On (SSO) authentication through OpenID Connect (OIDC) providers. This new feature enables customers to authenticate using their own OIDC provider, which simplifies the user experience by allowing them to seamlessly access UnifiedViews with their existing credentials, eliminating the need for multiple logins. This enhancement streamlines user access while maintaining the robust data integration capabilities that the platform is known for.
Key Benefits
Enhanced security: By leveraging the customer's existing OIDC provider, the security of the UnifiedViews environment is improved. This is achieved through standardized authentication protocols.
Simplified user experience: Users can seamlessly access UnifiedViews using their existing OIDC credentials, eliminating the need for multiple logins.
Increased flexibility: The feature provides the ability to integrate with a wide range of OIDC providers, giving customers the freedom to choose the solution that best meets their needs.
Backwards compatibility: Customers are not forced to switch to the new authentication method. The local (RDF) authentication mode can still be used as before.
Supported OIDC Providers
Keycloak
other OIDC-compliant providers (compatibility may vary)
Configuration and Migration
Any UV instance running version 10.1.0 or later can be seamlessly switched to OIDC mode by updating its configuration settings. This typically involves setting the authentication mode to OIDC and providing the necessary OIDC parameters, such as the issuer URL, client ID, client secret, and scopes. After configuration, the instance will use OpenID Connect for user authentication.
When changing to OIDC mode for the first time, if you want to keep your pipelines, schedules, and custom DPUs, you will need to migrate the ownership for these resources. This migration is not necessary if the usernames in your OIDC provider match the usernames in your UV instance. The UnifiedViews Migration API provides endpoints to migrate pipelines, schedules, and DPUs. These endpoints are available at the /migrate
base path and require ADMIN_ROLE
authorization.
API Usage
The API endpoints remain unchanged. However, you will now authenticate using OAuth tokens retrieved from your identity provider. For endpoints that require administrative privileges, ensure you obtain a token for a user account that holds an admin role within your provider. This approach maintains security while providing the necessary permissions for administrative operations.
Bug Fixes
New UnifiedViews deployments now automatically configure all Data Processing Units (DPUs) with public visibility settings. This enhancement ensures that all team members can access and utilize DPUs immediately upon deployment, eliminating the previous configuration barrier that required manual permission adjustments for non-administrative users during the initial setup process.
Component Versions
Tomcat 9.0.104
RDF4J 4.3.6
Spring Core 5.3.30
Spring Security 5.8.16
System Requirements
Java 17