Failure publishing app to Foundry

Scenario:

HCL Volt MX 9.5.3 - Helm based deployment.

Deplyoing to foundry an app that only includes a Microsoft Active Directory services fails with the following error shown in the console's "publish" log.

Failed to associate Identity Services Failed to publish identity providers snapshot to Auth Service [ Tracking id - f888c079-d34c-46bc-8721-a855409cb5b1 ]

Can you suggest what is the right troubleshooting approach here ?

Hi @Daniele Vistalli,

Can you please provide the logs of workspace, identity and middleware components? To capture logs of both components use the below command.
kubectl logs -f <console-container-id>
kubectl logs -f <identity-container-id>
kubectl logs -f <middleware-container-id>

I found this in the console of Iris while building the app:

INFO
---⚙ Publish Services ---
Status - Error
Application published
Publish snapshot created successfully
[Clean up] No clean up of unused App Services is required
[Clean up] Skipping removal of Mobile Web Client as it is being updated
[Clean up] No clean up of unused Sync Services is required
Skipping publish of App Services as they are not configured
Published Mobile Web Client
Skipping publish of Sync Services as they are not configured
Failed to associate Identity Services. Details: Failed to publish identity providers snapshot to Auth Service [ Tracking id - a4e8a479-eb28-48b0-a63b-09359bade53a ]
10:52:12.538 [main] ERROR com.kony.console.tools.api.MobileFabricException - Failed to publish
10:52:12.539 [main] ERROR com.kony.console.tools.api.MobileFabricException - Publish failed for App 1 with app id "51d940d8-5519-44e9-99d9-7f6a71191d8b". Failed to publish
ERROR mf publish error: ERROR: Publish failed for App 1 with app id "51d940d8-5519-44e9-99d9-7f6a71191d8b". Failed to publish
INFO ⇏ Services for this application will not work since they are not published to Foundry.
ERROR CustomError: Error while publishing Foundry application. ERROR: Publish failed for App 1 with app id "51d940d8-5519-44e9-99d9-7f6a71191d8b". Failed to publish
at C:\Program Files\Volt MX Iris\kbuild\serviceconfig\PublishTask.js:1:2297
at new Promise ()
at PublishTask.execute (C:\Program Files\Volt MX Iris\kbuild\serviceconfig\PublishTask.js:1:712)
at C:\Program Files\Volt MX Iris\kbuild\serviceconfig\servicePackager.js:1:1496
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
INFO Creation of C:\Users\Service\Iris\workspace\konyfabriccli.properties file is successful.
INFO ⚙ Fetching service doc...
ERROR mf appinfo publish error: ERROR: HTTP GET on https://mxapps.voessing.de/authService/100000002/appconfig?compositeSvcDoc=true failed for [Fetch service document of app] with status 401. Details - {"details":{"message":"Invalid App Credentials found in Request","errcode":0,"errmsg":"Invalid App Credentials found in Request"},"httpstatus":"Unauthorized","requestid":"c4e67b50-4146-4fd8-becb-73b618c80741","domain":"AUTH","code":-9,"mfcode":"Auth-9","message":"Invalid App Credentials"}
WARN ⇏ Services for this application will not work since they are not published to Foundry.
ERROR Error get service doc for mf app:ERROR: HTTP GET on https://mxapps.voessing.de/authService/100000002/appconfig?compositeSvcDoc=true failed for [Fetch service document of app] with status 401. Details - {"details":{"message":"Invalid App Credentials found in Request","errcode":0,"errmsg":"Invalid App Credentials found in Request"},"httpstatus":"Unauthorized","requestid":"c4e67b50-4146-4fd8-becb-73b618c80741","domain":"AUTH","code":-9,"mfcode":"Auth-9","message":"Invalid App Credentials"}
INFO Done!
INFO

BUILD SUMMARY

desktopweb … COMPLETED [12.59 s]
Upload Web Archive … App ‘App 1’ uploaded successfully!
Fabric App … ERROR
Total time … 00:01:45.296
Finished at … “2023-05-24T08:52:14.289Z”

Build and Publish Web Failed

At the same time when this happens, I am successfully authenticated to our foundry instance.

@Daniele Vistalli or @Daniele Vistalli can you have a look?

Browser get request to the same address fails the same way although the necessary cookies are existing:

Whenever I re-upload the metadata.xml from AAD to my identity service, the publishing works well

why did this solve the problem?

the authentication does not work in the app. There must be something broken - but what?