Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build: update changelog for v1.8.0-RC4 #472

Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
68 changes: 54 additions & 14 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,29 +2,69 @@

New features, fixed bugs, known defects and other noteworthy changes to each release of the Catena-X Portal Backend.

## 1.8.0-RC4

### Change
* updated response body of the GET: /api/administration/user/owncompany/users endpoint by changing the "role" section to an array to include role client information ![Tag](https://img.shields.io/static/v1?label=&message=BreakingChange&color=yellow&style=flat)
* pattern harmonization of 'company name' insert endpoints
* POST: api/administration/invitation
* POST: api/administration/registration/network/partnerRegistration
* POST: api/registration/application/{applicationId}/companyDetailsWithAddress
* PUT: /api/apps/appreleaseprocess/{appID}
* POST: /api/apps/appreleaseprocess/createapp
* pattern harmonization of 'company name' search endpoints
* GET: api/administration/registration/applicationsWithStatus
* GET: api/administration/registration/applications
* adjusted business logic of post/put BPN endpoints to allow the post/put of lowercase BPNs and ensure the transition to all uppercase by the backend logic (connector controller, registration controller, user controller)

### Feature
* Administration Service
* API endpoints for user account creation backend logic updated to set the providerID (unique username on the IdP which holds the user identity) is getting stored inside the portal db
* POST: /api/administration/identityprovider/owncompany/usersfile
* POST: /api/administration/registration/network/{externalId}/partnerRegistration
* POST: /api/administration/invitation
* POST: /api/administration/user/owncompany/users
* POST: /api/administration/user/owncompany/identityprovider/{identityProviderId}/users
* POST: /api/administration/user/owncompany/identityprovider/{identityProviderId}/usersfile
* POST: /api/administration/user/owncompany/usersfile
* POST: /api/registration/application/{applicationId}/inviteNewUser
* added additional user identity provider attributes (such as idpDisplayName and providerID) for all GET user account data
* GET: /api/administration/user/owncompany/users?page=0&size=5
* GET: /api/administration/user/owncompany/users/{userId}
* GET: /api/administration/user/ownUser

### Technical Support
* fixed sonar cloud finding to use correct pagination params

### Bugfix
* changed claimTypes static class of clientId claim to client_id

### Known Knowns
n/a

## 1.8.0-RC3

### Change
- External Interface Details
- BPDM interface refactored - bpdm push process was updated to support the new interface spec of the bpdm gate service
- Clearinghouse interface updated - possible generated clearinghouse service error content is getting saved inside the application comment level
- Email Template "cx_admin_invitation" enhanced by adding the section and link of the decline url (portal-frontend implementation)
* External Interface Details
* BPDM interface refactored - bpdm push process was updated to support the new interface spec of the bpdm gate service
* Clearinghouse interface updated - possible generated clearinghouse service error content is getting saved inside the application comment level
* Email Template "cx_admin_invitation" enhanced by adding the section and link of the decline url (portal-frontend implementation)

### Feature
- Onboarding Service Provider Function
- enabled deactivation of managed idps (administration service) via the existing idp status update endpoint
- enabled deletion of managed idps (administration service) via the existing idp delete endpoint
- added new endpoint to enable customer to decline their own company application which was created by an osp
* Onboarding Service Provider Function
* enabled deactivation of managed idps (administration service) via the existing idp status update endpoint
* enabled deletion of managed idps (administration service) via the existing idp delete endpoint
* added new endpoint to enable customer to decline their own company application which was created by an osp

### Technical Support
- Release workflow updated by adding additional image tag of type semver
- Upgraded external packages with security vulnerabilities
* Release workflow updated by adding additional image tag of type semver
* Upgraded external packages with security vulnerabilities

### Bugfix
- Endpoint authorization on valid companyId added for
- POST: /api/apps/appreleaseprocess/consent/{appId}/agreementConsents
- POST: /api/services/servicerelease/consent/{serviceId}/agreementConsents
- Adjusted endpoint GET: api/administration/serviceaccount/owncompany/serviceaccounts to filter for active service accounts by default if no parameter is submitted
* Endpoint authorization on valid companyId added for
* POST: /api/apps/appreleaseprocess/consent/{appId}/agreementConsents
* POST: /api/services/servicerelease/consent/{serviceId}/agreementConsents
* Adjusted endpoint GET: api/administration/serviceaccount/owncompany/serviceaccounts to filter for active service accounts by default if no parameter is submitted

## 1.8.0-RC2

Expand Down
2 changes: 1 addition & 1 deletion src/Directory.Build.props
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,6 @@
<Project>
<PropertyGroup>
<VersionPrefix>1.8.0</VersionPrefix>
<VersionSuffix>RC3</VersionSuffix>
<VersionSuffix>RC4</VersionSuffix>
</PropertyGroup>
</Project>
Loading