Skip to content

Support Azure DevOps STACKIT Service Connection #1668

Closed

Description

@JorTurFer

Problem description

Some months ago, we shipped https://marketplace.visualstudio.com/items?itemName=SchwarzDigits.stackit-service-connection.

That connection can be used for easily configure service account connections (keys or WIF) by customers.
The current cli version doesn't read the env "STACKIT_SERVICE_CONNECTION_ID" and this leads with different assertions in different contexts.

For example, if terraform and cli run on the same flow, they will get a different OIDC token with a different "sub".

Proposed solution

As terraform does, the cli should check the presence of the env "STACKIT_SERVICE_CONNECTION_ID" and pass it to the oidcadapters package in order to use the same credential configuretion in all the surfaces.

This can be done here:

if adoURL := os.Getenv(EnvAzureOIDCRequestURI); adoURL != "" {
if adoToken := os.Getenv(EnvAzureAccessToken); adoToken != "" {
return oidcadapters.RequestAzureDevOpsOIDCToken(adoURL, adoToken, ""), nil
}
}

terraform example:

https://github.com/stackitcloud/terraform-provider-stackit/blob/e3484e4d1a947ceda0d0908233dda74e16cd24fc/stackit/provider.go#L710-L716

Activity

  1. Fyusel commented on Oct 16, 2026

    @Fyusel
    Contributor

    Hi @JorTurFer,
    thank you for reporting this issue. We will have a look at it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions