Skip to content

Service principal authentication with client secret#597

Open
LapNik wants to merge 1 commit into
microsoft:masterfrom
LapNik:master
Open

Service principal authentication with client secret#597
LapNik wants to merge 1 commit into
microsoft:masterfrom
LapNik:master

Conversation

@LapNik

@LapNik LapNik commented Nov 7, 2025

Copy link
Copy Markdown

Adds the option to specify a client secret in the endpoint credential structures read from the ARTIFACTS_CREDENTIALPROVIDER_FEED_ENDPOINTS environment variable.

A client certificate may be difficult to use in some CICD scenarios, so this adds another option for service principal authentication. Users should still prefer certificates over secrets.

@LapNik

LapNik commented Nov 7, 2025

Copy link
Copy Markdown
Author

@microsoft-github-policy-service agree

@LapNik

LapNik commented Nov 7, 2025

Copy link
Copy Markdown
Author

For context, I wrote this PR because I had trouble configuring service principal authentication with client certificate in GitLab CI/CD.

In GitLab, I could configure a certificate file on Project level, but the file location would be random. The file path is saved to an environment variable, which I could expand into the ARTIFACTS_CREDENTIALPROVIDER_FEED_ENDPOINTS variable, but on Windows it would result in invalid JSON due to path separators.

Adds the option to specify a client secret in the endpoint credential
structures read from the ARTIFACTS_CREDENTIALPROVIDER_FEED_ENDPOINTS
environment variable.

A client certificate may be difficult to use in some CICD scenarios, so
this adds another option for service principal authentication. Users
should still prefer certificates over secrets.

Signed-off-by: Niko Lappalainen <niko.lappalainen@m-files.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant