Teams: Support certificate and federated credentials (workload identity) in Chat SDK auth #119
Description
Problem Statement
Current Chat SDK supports only client secret (password)–based authentication. This blocks secure production setups that prohibit long-lived secrets (e.g., GitHub Actions OIDC, Azure workload identity, managed identity). Many orgs require certificate-based or federated credentials for compliance and secretless CI/CD.
Proposed Solution
Add support for
- Client certificate authentication
- Federated credentials
Alternatives Considered
No response
Use Case
Priority
Critical
Contribution
- I am willing to help implement this feature
Additional Context
No response