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

[POLICY] Implement handling of notification which are revoked from receiver side because of policy expiration #639

Closed
3 tasks done
mkanal opened this issue Feb 6, 2024 · 8 comments · Fixed by #1192
Closed
3 tasks done
Assignees
Labels
4 - Policy Management backend Backend related issues hardening measurements to increase resiliency policy policy management access and usage spillover temporary label for spill over

Comments

@mkanal
Copy link
Contributor

mkanal commented Feb 6, 2024

As user
I want comprehensible message in case policy of expiration
so that I know exactly why policy was revoked

Blocked by

#787

Link

Hints / Details

  • ...

Acceptance Criteria

Out of Scope

  • ...
@mkanal mkanal changed the title Realize handling of notification which are revoked from receiver side because of policy exiration Implement handling of notification which are revoked from receiver side because of policy expiration Feb 6, 2024
@mkanal
Copy link
Contributor Author

mkanal commented Feb 6, 2024

@jzbmw pbi implementing revoking of notification

@jzbmw jzbmw added the hardening measurements to increase resiliency label Feb 15, 2024
@ds-lcapellino ds-lcapellino added the backend Backend related issues label Mar 12, 2024
@ds-mwesener ds-mwesener added the BLOCKED Issues are blocked by other issues label Apr 16, 2024
@mkanal mkanal added the policy policy management access and usage label Apr 25, 2024
@mkanal mkanal changed the title Implement handling of notification which are revoked from receiver side because of policy expiration [POLICY] Implement handling of notification which are revoked from receiver side because of policy expiration Apr 25, 2024
@ds-mmaul ds-mmaul removed the BLOCKED Issues are blocked by other issues label Apr 30, 2024
@RazvanZmau RazvanZmau added the spillover temporary label for spill over label May 28, 2024
@ds-lcapellino ds-lcapellino self-assigned this Jun 10, 2024
ds-lcapellino added a commit to catenax-ng/tx-item-relationship-service that referenced this issue Jun 10, 2024
ds-lcapellino added a commit to catenax-ng/tx-item-relationship-service that referenced this issue Jun 10, 2024
ds-lcapellino added a commit to catenax-ng/tx-item-relationship-service that referenced this issue Jun 10, 2024
ds-lcapellino added a commit to catenax-ng/tx-item-relationship-service that referenced this issue Jun 11, 2024
ds-lcapellino added a commit to catenax-ng/tx-item-relationship-service that referenced this issue Jun 11, 2024
ds-lcapellino added a commit to catenax-ng/tx-item-relationship-service that referenced this issue Jun 11, 2024
ds-lcapellino added a commit to catenax-ng/tx-item-relationship-service that referenced this issue Jun 11, 2024
mkanal added a commit to eclipse-tractusx/item-relationship-service that referenced this issue Jun 11, 2024
ds-lcapellino added a commit to ds-lcapellino/traceability-foss that referenced this issue Jun 17, 2024
ds-lcapellino added a commit to ds-lcapellino/traceability-foss that referenced this issue Jun 17, 2024
ds-lcapellino added a commit to ds-lcapellino/item-relationship-service that referenced this issue Jun 17, 2024
ds-lcapellino added a commit to ds-lcapellino/item-relationship-service that referenced this issue Jun 17, 2024
ds-lcapellino added a commit to ds-lcapellino/traceability-foss that referenced this issue Jun 17, 2024
ds-lcapellino added a commit to ds-lcapellino/item-relationship-service that referenced this issue Jun 17, 2024
ds-lcapellino added a commit to ds-lcapellino/traceability-foss that referenced this issue Jun 18, 2024
ds-lcapellino added a commit to ds-lcapellino/traceability-foss that referenced this issue Jun 18, 2024
@ds-mwesener
Copy link
Contributor

Reviewed the PR: #1041 (review) please see my comments.

@ds-lcapellino
Copy link
Contributor

ds-lcapellino commented Jul 8, 2024

The issue was fixed with the following PRs:

The issue was tested on dev as follows:

  1. With the policy API, create a new policy that is either expired or has wrong permissions
  2. create a new notification
  3. approve notification
  4. check the error message of the notification - the corresponding error of step 1. should be displayed

@ds-crehm
Copy link
Contributor

ds-crehm commented Jul 8, 2024

Tested on E2E:

Policies don't match:
grafik
Policy of sender is expired:
grafik
This error should instead be like the first one "Failed to negotiate contract agreement: Policy [EXPIRED_POLICY_TEST] has expired."

Note:
The valid until date from the receiver is not verified. So I can send a notification to a BPN with an expired policy as long as the constraints match and my own policy is within the validUntil deadline.

Also, following bug was found - unrelated to this ticket: #1188

ds-lcapellino added a commit to eclipse-tractusx/item-relationship-service that referenced this issue Jul 9, 2024
ds-lcapellino added a commit to eclipse-tractusx/item-relationship-service that referenced this issue Jul 9, 2024
ds-lcapellino added a commit that referenced this issue Jul 9, 2024
ds-mwesener added a commit that referenced this issue Jul 10, 2024
…pired-error-message

bug: #639 fix policy expired message
@mkanal mkanal reopened this Jul 10, 2024
@ds-mwesener
Copy link
Contributor

Summary of parking lot: Ticket will be moved to the review column. @ds-crehm and @mkanal will have a seperate meeting where @ds-crehm presents the use case to @mkanal

ds-lcapellino added a commit to ds-lcapellino/item-relationship-service that referenced this issue Jul 10, 2024
ds-lcapellino added a commit to ds-lcapellino/item-relationship-service that referenced this issue Jul 10, 2024
@mkanal
Copy link
Contributor Author

mkanal commented Jul 10, 2024

Image
Wrong status "ZUGESTELLT" should be "ERSTELLT" as there was an error during send process.

@ds-crehm
Copy link
Contributor

Created the following bug ticket: #1213
As discussed, this ticket is now ready for review.

@ds-crehm ds-crehm assigned mkanal and unassigned ds-crehm Jul 15, 2024
@mkanal
Copy link
Contributor Author

mkanal commented Jul 15, 2024

LGFM. Implementation according to concept. PO acceptance in behalf of @jzbmw

@mkanal mkanal closed this as completed Jul 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4 - Policy Management backend Backend related issues hardening measurements to increase resiliency policy policy management access and usage spillover temporary label for spill over
Projects
Status: done
Development

Successfully merging a pull request may close this issue.

7 participants