Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Issue] azd pipeline config - auth type ignored #2883

Closed
jasontaylordev opened this issue Oct 18, 2023 · 0 comments · Fixed by #2905
Closed

[Issue] azd pipeline config - auth type ignored #2883

jasontaylordev opened this issue Oct 18, 2023 · 0 comments · Fixed by #2905
Assignees
Labels
authn customer-reported identify a customer issue needs-team-attention Issues out of a milestone pipelines question

Comments

@jasontaylordev
Copy link

Output from azd version
azd version 1.4.2 (commit 694107e)

Describe the bug
When I run the commands:

azd env new EnvName
azd pipeline config --provider github --auth-type federated  --principal-name sp-EnvName

The resulting service principal is created with both client and federated credentials.

To Reproduce
To reproduce the behavior, run the commands:

azd env new EnvName
azd pipeline config --provider github --auth-type federated  --principal-name sp-EnvName

Then navigate to Azure Portal > Microsoft Entra ID > App registrations > All applications > sp-EnvName > Certificates & secrets.

Note that both the Client secrets and Federated credentials have values.

Expected behavior
When specifying --auth-type federated, I expect that client credentials will not be created in Entra ID or configured in GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
authn customer-reported identify a customer issue needs-team-attention Issues out of a milestone pipelines question
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants