Closed mkanal closed 2 months ago
Asked portal team for futher assistance since the app creation process does not work.
Hi @mkanal / @jzbmw please assist me with the following topics:
The app release process is now working.
Following new topics came up.
1) Where can I find the initial created technical user which has all of the app roles I have selected on creation of the company? -> When I open https://portal.int.demo.catena-x.net/technicaluser on company BMW there is no technical user available. I am also not able to create a technical user via self service because only one role can be selected.
-> Will those be created after app creation?
-> Semantic Data Model, BPDM, Dataspace Discovery
2) We need an approval of the app request for BMW: "Trace-X" which is in status "In Review"
3) For the technical user which is used by the edc: Is it enough to have the "Identity Wallet Management" Role or do we also need the "Dataspace Discovery"?
Currently waiting for: #778 to be able to test successfully.
E2E environments are up and running. EDC connection is established and working. Tested the regular notification flow, which works without issues. Ready for review.
PO acceptance in behalf of @jzbmw. Works as intended.
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
Blocked by: https://github.com/eclipse-tractusx/portal-frontend/issues/736, https://github.com/eclipse-tractusx/portal-frontend/issues/704
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:
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.