Skip to content

Support for Client Secret #686

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

Closed
RobinDadswell opened this issue Jun 9, 2021 · 3 comments
Closed

Support for Client Secret #686

RobinDadswell opened this issue Jun 9, 2021 · 3 comments

Comments

@RobinDadswell
Copy link

RobinDadswell commented Jun 9, 2021

I can see that you have certificate based authentication allowed but is it possible to have the ability to use ClientSecret as part of the authentication methods - this is available when authenticating an app against Microsoft Graph normally so would be super handy for use in PowerShell
AB#9818

@ghost ghost added the ToTriage label Jun 9, 2021
@peombwa
Copy link
Member

peombwa commented Jun 15, 2021

We do not support client secrets due to security reasons such as; unintentionally adding a secret to a script and committing it to a public repo. This is also what MSAL recommends when it comes to production apps. I'd suggest you use a certificate instead.

We also have plans to support managed identities which will resolve the security concerns with secrets and credentials. See our authentication roadmap here #142 (comment).

@ghost
Copy link

ghost commented Jun 29, 2021

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@RobinDadswell
Copy link
Author

Agree that other methods should be used, I don't have an issue with that approach!

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

No branches or pull requests

2 participants