Release 2.4.0

[ds-jhartmann]

Added

• IRS is now able to cache the EDC catalog. Caching can be disabled via application config. Maximum amount of cached items and item time-to-live can be configured as well.

Changed

• API endpoints have now additional layer of security and require BPN claim in token. Allowed BPN that can access API can be configured with (env:API_ALLOWED_BPN) variable.
• Updated Spring Boot dependency to 3.0.5

Fixed

• Fixed issue in paging when calling SemanticsHub with some page size configurations

[gitguardian]

⚠️ GitGuardian has uncovered 12 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	Secret	Commit	Filename
5896348	Generic High Entropy Secret	493cf4a	charts/full-irs/test/vault.rest	View secret
5896348	Generic High Entropy Secret	493cf4a	charts/full-irs/test/vault.rest	View secret
5896349	Generic Private Key	493cf4a	charts/full-irs/daps/keys/edc.key	View secret
5896349	Generic Private Key	493cf4a	charts/full-irs/values.yaml	View secret
5896349	Generic Private Key	493cf4a	charts/full-irs/daps/keys/edc.key	View secret
5896349	Generic Private Key	493cf4a	charts/full-irs/values.yaml	View secret
5896350	RSA Private Key	493cf4a	charts/full-irs/subcharts/omejdn-service/templates/configmap.yaml	View secret
5896350	RSA Private Key	493cf4a	charts/full-irs/subcharts/omejdn-service/templates/configmap.yaml	View secret
5896351	Generic High Entropy Secret	493cf4a	charts/full-irs/test/irs-backend-service.rest	View secret
5896351	Generic High Entropy Secret	493cf4a	charts/full-irs/test/irs-backend-service.rest	View secret
5896352	Generic High Entropy Secret	493cf4a	charts/full-irs/test/omejdn-service.rest	View secret
5896352	Generic High Entropy Secret	493cf4a	charts/full-irs/test/omejdn-service.rest	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>