Open sats268842 opened 7 months ago
Please take a look at #3341
@torbenraab We can also configure Microsoft Auth with
MICROSOFT_CLIENT_ID= MICROSOFT_CLIENT_SECRET= MICROSOFT_CALLBACK_URL=http://localhost:3170/v1/auth/microsoft/callback MICROSOFT_SCOPE=user.read MICROSOFT_TENANT=common
Since it will take time for OpenID Connect to merge. So we can go with this approach
Is there an existing issue for this?
Summary
Integrating Microsoft Authentication will enhance accessibility and user experience, especially for corporate users entrenched in the Microsoft ecosystem.
Why should this be worked on?
Integrating Microsoft Authentication as a Single Sign-On (SSO) option is essential for enhancing user convenience, expanding the user base, and ensuring robust security. Many users and organizations heavily rely on Microsoft services, making this integration crucial for accessibility and compliance with corporate standards. Additionally, it aligns with industry trends towards secure and efficient authentication methods, potentially increasing the tool's adoption and competitiveness.