SAML2_AUTO_REGISTER + SAML2_AUTO_CONFIRM_EMAIL variables to be added? #1777

New Issue

OVERLORD · 2026-02-05T01:50:54+03:00

OVERLORD commented

2026-02-05 01:50:54 +03:00

Originally created by @tiredofit on GitHub (Jul 7, 2020).

Describe the feature you'd like
Add the following variables to align with other external services

Describe the benefits this feature would bring to BookStack users

If AUTO_REGISTER was disabled, it would limit the auto user creation and only rely on users in the User Table
If AUTO_CONFIRM_EMAIL was enabled - it would eliminate users having to verify their email, as they are already authorized via an external service provider which assumingly knows the right email address. This In a system where email is not being used at all, this limits the ability for users to automatically connect into the system.

Originally created by @tiredofit on GitHub (Jul 7, 2020). **Describe the feature you'd like** Add the following variables to align with other external services **Describe the benefits this feature would bring to BookStack users** - If AUTO_REGISTER was disabled, it would limit the auto user creation and only rely on users in the User Table - If AUTO_CONFIRM_EMAIL was enabled - it would eliminate users having to verify their email, as they are already authorized via an external service provider which assumingly knows the right email address. This In a system where email is not being used at all, this limits the ability for users to automatically connect into the system.

OVERLORD added the 🔨 Feature Request 🚪 Authentication labels 2026-02-05 01:50:54 +03:00

OVERLORD closed this issue

2026-02-05 01:50:57 +03:00

OVERLORD commented

2026-02-05 01:51:01 +03:00

@ssddanbrown commented on GitHub (Sep 27, 2025):

Since there's been no further desire reflected I'm going to close off this issue.

If still needed, it should be possible to emulate that additional AUTO_REGISTER behaviour with a simple logical theme system function to reject, or throw an error, on relevant events.

Email confirmation would only be required if using email domain filtering, or email confirmation, registration settings.
Again, if really needed, there are probably options via the logical theme system for alternative behaviour here too.

Thanks for the original request though @tiredofit.

@ssddanbrown commented on GitHub (Sep 27, 2025): Since there's been no further desire reflected I'm going to close off this issue. If still needed, it should be possible to emulate that additional `AUTO_REGISTER` behaviour with a simple logical theme system function to reject, or throw an error, on relevant events. Email confirmation would only be required if using email domain filtering, or email confirmation, registration settings. Again, if really needed, there are probably options via the logical theme system for alternative behaviour here too. Thanks for the original request though @tiredofit.

OVERLORD referenced this issue

2026-02-05 03:35:52 +03:00

Sorting a book changes the update time on pages. #2297

OVERLORD referenced this issue

2026-02-05 04:51:06 +03:00

Update updated_at field when tags are changed #2698

OVERLORD referenced this issue

2026-02-05 08:52:15 +03:00

Wrong revision information #4425

OVERLORD referenced this issue

2026-02-05 08:57:48 +03:00

Possible Bug / Possibly Intended #4473