-
Notifications
You must be signed in to change notification settings - Fork 23
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
Comments
@jzbmw pbi implementing revoking of notification |
…pired policies
…pired policies
…pired policies
…pired policies
…pired policies
…pired policies
…pired policies
…iration feature: eclipse-tractusx/traceability-foss#639 rework handling of ex…
Reviewed the PR: #1041 (review) please see my comments. |
…olicies-after-crud bug: #639 update policies provider after crud operations on policies
The issue was fixed with the following PRs:
The issue was tested on dev as follows:
|
Tested on E2E: Policies don't match: Note: Also, following bug was found - unrelated to this ticket: #1188 |
…ired-error-message bug: eclipse-tractusx/traceability-foss#639 update policy expired err…
…pired-error-message bug: #639 fix policy expired message
…icy exceptions
…interface for policy exceptions
…expiration feature: eclipse-tractusx/traceability-foss#639 add catch clause
Created the following bug ticket: #1213 |
LGFM. Implementation according to concept. PO acceptance in behalf of @jzbmw |
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
The text was updated successfully, but these errors were encountered: