Publishing to Custom On-Premise Environment asks for Authcontext

[Mkublbock]

We have setup custom deployment to one of our customer's on-premise servers. The problem is that the deployment pipeline now asks for an AUTHCONTEXT Secret. We have the Authcontext when we deploy to cloud environments, but how do we create it for On-Premise Deployments?
logs_66073160067.zip

[frottke]

The answer I got two years ago might also work for you: #519 (comment)

[Mkublbock]

Tried it but doesn't seem to work. It just says that it cannot authenticate

Attempting authentication to any-scope using clientCredentials...
Response status code does not indicate success: 400 (Bad Request). invalid_scope
AADSTS1002012: The provided value for scope any-scope is not valid. Client credential flows must have a scope value with /.default suffixed to the resource identifier (application ID URI). Trace ID: 46b6df52-f41a-454a-95de-aae283f61300 Correlation ID: 69fb2b65-eff9-47ec-8a34-f43cea6c4b66 Timestamp: 2026-04-24 16:39:51Z
Response status code does not indicate success: 400 (Bad Request).

Authentication failed

[Mkublbock]

We had the custom deployment script in the .AL-Go Folder and not the .github folder. Moved it into the .github folder and now it doesn't ask for the authcontext again. Seems to work now.

[Mkublbock]

@frottke Maybe you can help with this. The Custom Script is now running, it is able to download the artifacts on the On-Premise agent runner, but the GetAppsAndDependenciesFromArtifacts doesn't return any apps. I know that there is an "apps" parameter we can use, but obviously we don't want to hardcode this. How can we reference the downloaded artifact folder in the custom deploy script?