monicahq/monica

Support logging in with an OAuth2 provider

Open

#1,154 创建于 2018年4月12日

在 GitHub 查看
 (14 评论) (27 反应) (0 负责人)PHP (24,641 star) (2,464 fork)batch import
feature requesthelp wantedsecurity

描述

A rephrasing of the now-closed #558. And a reincarnation of #39.

As a user, I would like to be able to log in with a 3rd-party identity provider and not have to maintain yet another username and password credential pair.

This is probably only going to be useful for self-hosted installations -- they can decide who they trust. For the publicly hosted version, I don't know of many OAuth2 providers that has broad community trust. (Mozilla's Firefox Accounts maybe? I don't even know if 3rd parties can use it. Gitlab and/or Github as well?)

If support is implemented in a generic fashion, then users can spin up their own OAuth2 providers (RedHat's KeyCloak, a self-hosted Gitlab instance, there are many other projects.) and trust those.

贡献者指南

技术栈
phplaravel
领域
authenticationbackend
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
over 1 week
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Basic understanding of OAuth2Familiarity with Laravel authenticationKnowledge of PHP and LaravelExperience with socialite packages
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
30
研究方向
Investigate previous discussions in linked issues #558 and #39. Review the Laravel authentication system, particularly the use of Laravel Socialite for OAuth2. Look at the current login flow in routes and controllers. Consider which providers to support initially (e.g., GitHub, GitLab). Create a proposal outlining the architecture and required changes.