Support in Investigation regarding EDC Keycloack auth overflow

[jzbmw]

As DEV,
I want to know if the current Trace-X / IRS behaviour is expected or some unexpected behaviour,
so that we know what is happening.

Hints / Details

• child of Resiliency Measurements sig-release#218
• see https://jira.catena-x.net/browse/TRACEFOSS-3027 for Trace-X support
• check token ttl / refresh token

Outcome / Acceptance Criteria

Acceptance Criteria

• testing conducted in Week 51
• new User for EDC MIW communication been implemented on INT env's
• IRS and Trace-X Team work together for identification of issues
• Automated Tests are being used as reference usage of tools
• LogLevel has been increased to get more details.

[ds-jhartmann]

Planning 2

• update EDC helm config to get more detailed logs from EDC Controlplane (both consumer and provider) and share with TraceX team
• assist in analysing IRS logs to get a rough estimate on the amount of contract negotiations and calls to EDC in general
• Testing is done on TraceX INT environment, we do not need to run tests on IRS INT

[ds-jhartmann]

• Changed MIW Users to have a distinct user for each EDC for a easier debugging in the future
• log config is already set to DEBUG. MIW requests are not logged on EDC side
• supported Trace-X Team with their investigation

[jzbmw]

Mail for results have been sent. Results to be expected