Open mkanal opened 2 months ago
test https://jira.catena-x.net/projects/TRI/issues/TRI-1934 7: PASS / 8 FAILED => OK, because the 8 FAILS are the tests that need to be fixed in #503 (see TRI-1927 for comparison)
@dsmf why is the jwkSetUri not updated in vault?
Int was not updated
Please recheck int dev environments. Thank you very much
@mkanal ~INT was not updated since there was the reset of the entire environment which lead to no data being available anyway~ The jwkSetUri was not updated because it is no longer in use. As @dsmf mentioned, the tests were executed successfully, so everything is working as expected again.
@ds-jhartmann Please remove jwkSetUri as it is not in use. INT was mentioned inside the AC.
@ds-jhartmann Thank you very much accepted. Works as indended.
@jzbmw Ready for review.
As product I want to re-setup the int environment after reset of portal and bpdm so that we are able to join the e2e testing phase
Links
Acceptance Criteria
Out of Scope
Hints / Details
please note that we started to reset the Integration Env. to get ready for the 24.05. E2E tests. As a result, access to the portal and connected applications will be extremely limited until the E2E tests begin.
I understand that this may have a significant impact on many of you. To mitigate the inconvenience, we enabled a special support function. If you still need/want to perform actions such as EDC communications (version < 0.7 RC1), test runs, etc. using previously used users (both technical and functional), you can proceed by switching your connector and/or app instances to the following Keycloak token URL:
Token URL: https://centralidp-v2.int.demo.catena-x.net/auth/realms/CX-Central/protocol/openid-connect/token
Please note that this IDP instance is our previous INT Keycloak instance, which is now available under a new endpoint path. All user accounts and service accounts are still accessible with your existing credentials.