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

Hot to limit Public Access to a list of ip-adresses #5422

Open
2 tasks done
Skittel opened this issue Jan 18, 2025 · 1 comment
Open
2 tasks done

Hot to limit Public Access to a list of ip-adresses #5422

Skittel opened this issue Jan 18, 2025 · 1 comment

Comments

@Skittel
Copy link

Skittel commented Jan 18, 2025

Attempted Debugging

  • I have read the debugging page

Searched GitHub Issues

  • I have searched GitHub for the issue.

Describe the Scenario

Hello,
I would like to create a wiki for a customer.
There request is the open the wiki inside the company without login to see all informations (Public Access).
From the outside (road warrior) only with login.

Is there a known way to limit public access to a list of ip-adresses?
Or is there a way to autologin from these ips?

Thanks

Stefan

Exact BookStack Version

v24.12.1

Log Content

No response

Hosting Environment

PHP 8.4 on Ubuntu 24

@ssddanbrown
Copy link
Member

There request is the open the wiki inside the company without login to see all informations (Public Access).

Generally that may be better achieved by hosting the wiki inside their firewall (within their own private company network) so it can be under their own managed network controls.

Is there a known way to limit public access to a list of ip-adresses?

BookStack does not specifically provide that, but you could instead set IP-based access restrictions at the web-server or host firewall level to completely prevent access outside those IPs.

Or is there a way to autologin from these ips?

Not built-in at all. You could maybe hack something in using our logical theme system if confident with PHP, but it's not something I can officially advice since it will require maintainence and could be easy to get wrong.

Generally, if the company uses a central login/authentication system, then connecting that to BookStack (via SAML2/OIDC if possible) so employees can use single-sign-on options is the general best approach to low-friction company access, since that will result in actual unique logged in users.

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