Automattic / Automattic/jetpack

SSO: Disable SSO if other Single Sign-On plugins are detected.

Open
#8,404 2 comments 0 reactions 0 assignees View on GitHub
[Feature] SSO [Pri] Low Customer Report [LEGACY] Enhancement Good For Community
Dominant language
PHP
Stars
1.8k
Forks
898
Avg merge
1d 18h
Merged PRs (30d)
774

Description

When using other services for SSO Login Jetpack should detect and disable the WP.com SSO module. This conflict was reported with this plugin:

https://wordpress.org/plugins/google-apps-login/ (https://wp-glogin.com/glogin/)

For most JP features, if we notice something else duplicating that functionality we'll bow out, this feels like it should be no exception.

Steps to reproduce:

1. Install and activate https://wordpress.org/plugins/google-apps-login/
2. Check that the login page has the correct login options:
![image](https://user-images.githubusercontent.com/16127063/34272776-3c1ec446-e657-11e7-9318-61d8f7073507.png)
3. Activate SSO in Jetpack
4. Go back to login page, and note that Google Login is no longer an option.

First reported in 861063-zen

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the conflict with the Google Apps Login plugin and Jetpack SSO enabled, then trace the Jetpack SSO activation and login integration points. Done means Jetpack detects the other SSO plugin and leaves its login option available instead of overriding it.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, wordpress
Domain
authentication
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.