mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-11 03:13:15 +03:00
freee access for lan and not for others #5092
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @boscorelly on GitHub (Dec 30, 2024).
Attempted Debugging
Searched GitHub Issues
Describe the Scenario
hi,
i haven't found the answer : is it possible to create a scenario where a specific ip range can access publicly the documentation, while others must login ?
Exact BookStack Version
last
Log Content
No response
Hosting Environment
docker
@ssddanbrown commented on GitHub (Dec 31, 2024):
Hi @boscorelly,
No, that's not something which is supported at all.
It could be possible to hack on an instance in various ways using the logical theme system, but I'm hesitant to provide further guidance on that as it's easy to result in an insecure setup when it comes to customizations around authentication.
@boscorelly commented on GitHub (Jan 1, 2025):
De : Dan Brown @.>Envoyé : mardi, décembre 31, 2024 4:47 PMÀ : BookStackApp/BookStack @.>Cc : Camille Ollié @.>; Mention @.>Objet : Re: [BookStackApp/BookStack] freee access for lan and not for others (Issue #5377)
Hi @boscorelly,
No, that's not something which is supported at all.
It could be possible to hack on an instance in various ways using the logical theme system, but I'm hesitant to provide further guidance on that as it's easy to result in an insecure setup when it comes to customizations around authentication.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
Envoyé à partir de Outlook pour iOS
@ssddanbrown commented on GitHub (Jan 1, 2025):
Sure, I understand the aim.
Would users not already be generally logged into Office365 while in the office though? If so, just using Azure/MS based OIDC for SSO may provide a low-friction route for use.
@boscorelly commented on GitHub (Jan 2, 2025):
De : Dan Brown @.>Envoyé : mercredi, janvier 1, 2025 4:22 PMÀ : BookStackApp/BookStack @.>Cc : Camille Ollié @.>; Mention @.>Objet : Re: [BookStackApp/BookStack] freee access for lan and not for others (Issue #5377)
Sure, I understand the aim.
Would users not already be generally logged into Office365 while in the office though? If so, just using Azure/MS based OIDC for SSO may provide a low-friction route for use.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
Envoyé à partir de Outlook pour iOS
@ssddanbrown commented on GitHub (Jan 4, 2025):
Our OIDC/SAML options do provide the option to auto-start the auth process, which results in automatic login assuming they're already logged into the upstream auth system in that browser.
Otherwise, I'll close this off since the original question has been answered.
@boscorelly commented on GitHub (Jan 4, 2025):
De : Dan Brown @.>Envoyé : vendredi, janvier 3, 2025 10:01 PMÀ : BookStackApp/BookStack @.>Cc : Camille Ollié @.>; Mention @.>Objet : Re: [BookStackApp/BookStack] freee access for lan and not for others (Issue #5377)
but they will not be auto logged in.
Our OIDC/SAML options do provide the option to auto-start the auth process, which results in automatic login assuming they're already logged into the upstream auth system in that browser.
Otherwise, I'll close this off since the original question has been answered.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
Envoyé à partir de Outlook pour iOS
@boscorelly commented on GitHub (Jan 21, 2025):
hi,
i tried and it works like i want.