Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatic email confirmation for OIDC #5516

Open
2 tasks done
miko007 opened this issue Mar 4, 2025 · 2 comments
Open
2 tasks done

Automatic email confirmation for OIDC #5516

miko007 opened this issue Mar 4, 2025 · 2 comments

Comments

@miko007
Copy link

miko007 commented Mar 4, 2025

Attempted Debugging

  • I have read the debugging page

Searched GitHub Issues

  • I have searched GitHub for the issue.

Describe the Scenario

From a page within the documentation, i gathered this hint: {SERVICE}_AUTO_CONFIRM_EMAIL=true, which lead me to believe, that OIDC_AUTO_CONFIRM_EMAIL=true should also work.

Setting this in my .env file however, has no effect. BookStack still complains about a non-verified email address for the new user.

Am i missing something, or is this actually not implemented?

I do not really want users to be bothered clicking a link in an email when they log in the first time, as i already know that the email is correct. If this would work, i could skip setting up SMTP alltogether, i think.

Exact BookStack Version

v25.02

Log Content

No response

Hosting Environment

I run BookStack dockerized.

@ssddanbrown
Copy link
Member

Hi @miko007,

Do you need email confirmation/domain restrictions active if you're using OIDC?
Email confirmation is only needed if using those registration options.

@miko007
Copy link
Author

miko007 commented Mar 6, 2025

oh, hey, thank you very much, that hint actually solved all problems at once. this did not even come to mind.

it somehow did not occur to me, that settings in the gui would have an effect on something i configured in the environment variables. there also is this hint in the settings, that the "enable registration" option is ignored, when using something like ldap, i extrapolated that to all the options, i guess.

but that most likely is just me being totally ignorant. maybe we should put something into the docs nevertheless?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants