v4.0.0
[v4.0.0] - 2024-08-20
Overview
This release introduces support for UI branding configuration, adds improvements to the process of registering connectors for service providers and fixes several minor issues.
Check the deployment migration notes to ensure that you configured everything correctly.
Detailed Changes
Major
- The portal now supports multiple theme configurations
Minor
- Catalog
- Added copyable contact email and subject fields in the data offer detail dialog
- Organization filter is no longer split into ID and name
- Connector filter is no longer split into ID and endpoint
- Removed dataspace filter when only one dataspace is configured
- Service provider
- Service providers can now provide connectors using a Connector JWKS URL instead of a certificate (#272)
- The configuration summary after registering a connector now shows the value for
EDC_OAUTH_CLIENT_ID
- Added a message on the CaaS request page to inform the user in case the feature is not configured
Patch
- Fixed user not being redirected to the correct URL after login (#280)
- Fixed the close button on the self-hosted/CaaS connector choice page (#258)
- Fixed Dashboard showing uptimes of over 100% (#262)
- Organization list: Data offer and connector counts now show the correct numbers according to the active environment (#255)
- Fixed provider organization ID not showing up on CaaS connectors (#206)
- Keep in mind that sovity needs to be registered in the portal for the ID to show up.
- Already registered connectors will be updated automatically, this process can take up to 24 hours
- Fixed the close button on the self-hosted/CaaS connector choice page (#258)
- Adjusted connector status naming for more consistency (#270)
RUNNING (CaaS) -> ONLINE
STOPPED (CaaS) -> OFFLINE
DEAD -> OFFLINE
- Breadcrumbs now show "Catalogue" properly when using the MDS theme
- Removed requirement for an environment with ID
test
Deployment Migration Notes
Read the deployment migration notes carefully if you want to retain the portal's current behavior.
If you configure the optional variables incorrectly, you might end up with an inconsistent configuration.
Backend
Environment variable changes:
- Renamed variables:
authority-portal.caas.sovity.limit-per-mdsid
toauthority-portal.caas.sovity.limit-per-organization
- New optional configuration variables - the values assigned here are the ones you should use to retain the current behavior:
-
# Organization ID configuration (example: prefix: MDS & length: 4 would generate Ids in the format MDSL1234XX) # The 'L' stands for 'Legal' and is added automatically after the prefix - the last 2 characters are the checksum authority-portal.organization.id.prefix: "MDS" authority-portal.organization.id.length: "4"
-
- New mandatory configuration variables:
-
# Enables the client to connect to the CaaS service. If you weren't provided credentials for the feature by sovity, set this to false quarkus.oidc-client.sovity.client-enabled: true
-
Frontend
Environment variable changes:
- New mandantory configuration variables - the values assigned here are the ones you should use to retain the current behavior:
-
# UI Branding profile AUTHORITY_PORTAL_FRONTEND_ACTIVE_PROFILE: mds-open-source # Short Dataspace name, used in some explanatory texts AUTHORITY_PORTAL_FRONTEND_DATASPACE_SHORT_NAME: MDS # Portal name displayed in various texts AUTHORITY_PORTAL_FRONTEND_PORTAL_DISPLAY_NAME: "MDS Portal"
-
Compatible Versions
- Authority Portal Backend Docker Image:
ghcr.io/sovity/authority-portal-backend:4.0.0
- Authority Portal Frontend Docker Image:
ghcr.io/sovity/authority-portal-frontend:4.0.0
- Catalog Crawler CE:
ghcr.io/sovity/catalog-crawler-ce:10.2.0
- Sovity EDC CE:
10.2.0