[PR #5461] [CLOSED] Enable Social Login with Planning Center Online #6500

New Issue

OVERLORD · 2026-02-05T10:33:55+03:00

OVERLORD commented

2026-02-05 10:33:55 +03:00

📋 Pull Request Information

Original PR: https://github.com/BookStackApp/BookStack/pull/5461
Author: @monoxane
Created: 1/31/2025
Status: ❌ Closed

Base: development ← Head: feat/planningcenter-auth

📝 Commits (2)

897c3dc feat: enable social login with planning center online
cc7c10d fix: update planningcenter display name to follow branding guidelines

📊 Changes

8 files changed (+76 additions, -2 deletions)

View changed files

📝 .env.example.complete (+5 -0)
📝 app/Access/SocialDriverManager.php (+1 -0)
📝 app/App/Providers/EventServiceProvider.php (+2 -0)
📝 app/Config/services.php (+9 -0)
📝 composer.json (+1 -0)
📝 composer.lock (+51 -1)
➕ resources/icons/auth/planningcenter.svg (+6 -0)
📝 version (+1 -1)

📄 Description

Hey, I'm probably being a bit of a pest opening a PR without an associated issue so sorry for that.

This PR adds support for Social auth with Planning Center, a scheduling and management app typically used with Churches, but also somewhat popular with some types of non-profits.

The rationale behind enabling social auth using the existing Socialite dependency is that PCO has their own OAuth2.0 implementation that does not conform 100% to the OIDC spec, and therefore cannot be used with the generic OIDC provider in BookStack (See planningcenter/developers #1271 for me complaining about it)

I don't really have a full PHP environment set up as I usually do golang/react but I've tested this locally using the docker-compose stack as well as building the LinuxServer.io image using it, and deploying that to my prod env. Changes behave as expected and I am able to log in using a PCO account via Oauth, and the account is successfully registered and marked as being from PCO. I've ran static check and the linter and they both passed.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/BookStackApp/BookStack/pull/5461 **Author:** [@monoxane](https://github.com/monoxane) **Created:** 1/31/2025 **Status:** ❌ Closed **Base:** `development` ← **Head:** `feat/planningcenter-auth` --- ### 📝 Commits (2) - [`897c3dc`](https://github.com/BookStackApp/BookStack/commit/897c3dcc19d84e57fdc1df921b3da7c2e3fab01a) feat: enable social login with planning center online - [`cc7c10d`](https://github.com/BookStackApp/BookStack/commit/cc7c10d97f0b3cdae2839cb38ba125902db5132e) fix: update planningcenter display name to follow branding guidelines ### 📊 Changes **8 files changed** (+76 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `.env.example.complete` (+5 -0) 📝 `app/Access/SocialDriverManager.php` (+1 -0) 📝 `app/App/Providers/EventServiceProvider.php` (+2 -0) 📝 `app/Config/services.php` (+9 -0) 📝 `composer.json` (+1 -0) 📝 `composer.lock` (+51 -1) ➕ `resources/icons/auth/planningcenter.svg` (+6 -0) 📝 `version` (+1 -1) </details> ### 📄 Description Hey, I'm probably being a bit of a pest opening a PR without an associated issue so sorry for that. This PR adds support for Social auth with [Planning Center](https://www.planningcenter.com), a scheduling and management app typically used with Churches, but also somewhat popular with some types of non-profits. The rationale behind enabling social auth using the existing Socialite dependency is that PCO has their own OAuth2.0 implementation that does not conform 100% to the OIDC spec, and therefore cannot be used with the generic OIDC provider in BookStack (See [planningcenter/developers #1271](https://github.com/planningcenter/developers/issues/1271) for me complaining about it) I don't really have a full PHP environment set up as I usually do golang/react but I've tested this locally using the docker-compose stack as well as building the LinuxServer.io image using it, and deploying that to my prod env. Changes behave as expected and I am able to log in using a PCO account via Oauth, and the account is successfully registered and marked as being from PCO. I've ran static check and the linter and they both passed. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

OVERLORD added the pull-request label 2026-02-05 10:33:55 +03:00

OVERLORD closed this issue

2026-02-05 10:34:00 +03:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/BookStack#6500