Use common user database shared with another Laravel project #816

New Issue

OVERLORD · 2026-02-04T22:22:36+03:00

OVERLORD commented

2026-02-04 22:22:36 +03:00

Originally created by @nekromoff on GitHub (Sep 17, 2018).

Describe the feature you'd like
Would it be possible to use social login/user accounts shared with another Laravel project that uses default user schema? This would specially be useful for social logins.

Currently my use case is this:
I have two Laravel installs (projects) running on the same domain. If user logs in using social OAuth2 access in another project, Bookstack token is overwritten and Bookstack requires log in again. Same goes once a user log is Bookstack, then another project requires relogging in.

Describe the benefits this feature would bring to BookStack users
Smoother streamlined login (remembered) process.

Additional context
n/a

Originally created by @nekromoff on GitHub (Sep 17, 2018). **Describe the feature you'd like** Would it be possible to use social login/user accounts shared with another Laravel project that uses default user schema? This would specially be useful for social logins. Currently my use case is this: I have two Laravel installs (projects) running on the same domain. If user logs in using social OAuth2 access in another project, Bookstack token is overwritten and Bookstack requires log in again. Same goes once a user log is Bookstack, then another project requires relogging in. **Describe the benefits this feature would bring to BookStack users** Smoother streamlined login (remembered) process. **Additional context** n/a

OVERLORD closed this issue

2026-02-04 22:22:37 +03:00

OVERLORD commented

2026-02-04 22:22:43 +03:00

@ssddanbrown commented on GitHub (Sep 20, 2018):

To be honest, Sharing the user database table directly with other projects is not really something I'd look to support due to the variation and uncontrollability that could occur.

I believe the core issue of this, in regards to being logged out of other systems, could be down to the cookies used. BookStack is using the default laravel_session cookie name and so may your other project. I've opened #1018 to be added in the next release to update BookStack to have a unique cookie name which should prevent being logged out of other systems.

@ssddanbrown commented on GitHub (Sep 20, 2018): To be honest, Sharing the user database table directly with other projects is not really something I'd look to support due to the variation and uncontrollability that could occur. I believe the core issue of this, in regards to being logged out of other systems, could be down to the cookies used. BookStack is using the default `laravel_session` cookie name and so may your other project. I've opened #1018 to be added in the next release to update BookStack to have a unique cookie name which should prevent being logged out of other systems.

OVERLORD commented

2026-02-04 22:22:49 +03:00

@nekromoff commented on GitHub (Sep 20, 2018):

Cool, this would definitely resolve it and I understand your argument.

On Thu, Sep 20, 2018 at 11:26 AM, Dan Brown notifications@github.com
wrote:

To be honest, Sharing the user database table directly with other projects
is not really something I'd look to support due to the variation and
uncontrollability that could occur.

I believe the core issue of this, in regards to being logged out of other
systems, could be down to the cookies used. BookStack is using the default
laravel_session cookie name and so may your other project. I've opened
#1018 https://github.com/BookStackApp/BookStack/issues/1018 to be added
in the next release to update BookStack to have a unique cookie name which
should prevent being logged out of other systems.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/BookStackApp/BookStack/issues/1010#issuecomment-423110033,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIJ3zS_dgvWRp1Twrxdpm6YQ5XRn9ewhks5uc18qgaJpZM4Wr8mS
.

@nekromoff commented on GitHub (Sep 20, 2018): Cool, this would definitely resolve it and I understand your argument. On Thu, Sep 20, 2018 at 11:26 AM, Dan Brown <notifications@github.com> wrote: > To be honest, Sharing the user database table directly with other projects > is not really something I'd look to support due to the variation and > uncontrollability that could occur. > > I believe the core issue of this, in regards to being logged out of other > systems, could be down to the cookies used. BookStack is using the default > laravel_session cookie name and so may your other project. I've opened > #1018 <https://github.com/BookStackApp/BookStack/issues/1018> to be added > in the next release to update BookStack to have a unique cookie name which > should prevent being logged out of other systems. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/BookStackApp/BookStack/issues/1010#issuecomment-423110033>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AIJ3zS_dgvWRp1Twrxdpm6YQ5XRn9ewhks5uc18qgaJpZM4Wr8mS> > . >

OVERLORD commented

2026-02-04 22:22:52 +03:00

@ssddanbrown commented on GitHub (Sep 20, 2018):

Okay, I that case I'll close this and we can await #1018 in the next release.

@ssddanbrown commented on GitHub (Sep 20, 2018): Okay, I that case I'll close this and we can await #1018 in the next release.

OVERLORD referenced this issue

2026-02-04 23:07:49 +03:00

The article does not display headlines in the preview (Cyrillic) #948

Sign in to join this conversation.