Closed jzbmw closed 9 months ago
Hi @ds-ext-kmassalski & @ds-alexander-bulgakov
what is missing is the outcome. Was this tested. How could this be tested? Is there some evidence to check? Need some assistance here. Thank you very much,
Hi @ds-ext-kmassalski, as discussed please make sure the changes are deployt on DEV so i can test. Please give me a hint once the deployment is done. Thank you!
Updated documentation without any 'Keycloak' mentions can be found here: https://catenax-ng.github.io/tx-item-relationship-service/docs/arc42/full.html OAuth2 protocol is used as substitute.
App deployed on DEV and INT with newest version (without keycloak configuration names).
Some more evidences that its was modified:
No issues could be found during final QA-review. For testing tavern and cucumber tests were run in gitlab and locally and IRS-jobs were requested on DEV. Docu was checked as well. See outcome:
Ticket is ready for PO-review. FYI @jzbmw
As we are using OAuth2 Standard to authorize IRS and the API we have actually a product-lock in the configuration, documentation and in helm charts configuration. This might be removed to have a more generic approach.
Hints / Details
Current
Expected
Tasks
Outcome / Acceptance Criteria
Outcome
Acceptance Criteria
Out of Scope
Sprint Planning 2
Currently
Expected