Hi, @Oleksandr Hrusha, @Roman Barannyk, and @Denis . Great news, and thank you! Can this issue be Closed as Not reproduceable?

I can confirm that issue is not longer reproducible on https://tls-eureka-bugfest-ramsons-consortium.int.aws.folio.org/

Open

Tested, and it appears that this issue is no longer reproducible. The ILR ECS request was successfully created: https://tls-eureka-bugfest-ramsons-consortium.int.aws.folio.org/requests/view/fde9e10f-8995-4291-8d6e-dbfeabd50458

Error messages related to system user login appear in the mod-tlr logs; however, as discussed with the Eureka team, these should not impact the business logic

2025-03-25 15:19:10,681 WARN [org.fol.sid.ser.tok.SystemUserTokenProvider] (ForkJoinPool.commonPool-worker-12) Failed to obtain system user token: message = io.quarkus.security.UnauthorizedException: Authentication error: {"error":"invalid_grant","error_description":"Invalid user credentials"}: java.util.concurrent.ExecutionException: io.quarkus.security.UnauthorizedException: Authentication error: {"error":"invalid_grant","error_description":"Invalid user credentials"}

Hello @Anne Ekblad , I increased the priority to P1 since that is a blocker for FSE team to switch to TLS version of R Bugfest; because that is a key workflow that we must have on the cluster to test different scenarios.

cc @Alexander Kurash @Yogesh Kumar @Artem Akimov @Oleksandr Hrusha @Oleg Kurdyayev

Hello @Anne Ekblad ]. I don`t think https://folio-org.atlassian.net/browse/MODTLR-161 is related to this issue, at least because this ticket is about TLS