mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-05-04 18:08:46 +03:00
Adding SAML support #236
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 @Xen3r0 on GitHub (Jan 17, 2017).
For Feature Requests
Desired Feature:
Adding SAML support for authentication method with
LightSAMLor another component.Link:
https://www.lightsaml.com/
@ssddanbrown commented on GitHub (Jan 30, 2017):
Hi @Xen3r0, I'd like to add SAML support but I'm not very familiar with the standard and maintaining another Auth method can be a lot of work.
I'd need to learn SAML and explore how it works. I'll leave this open and we'll see if it get's requested further otherwise I'll have to wait until I've got a large block of time to learn SAML and SSO standards.
@Ethanb00 commented on GitHub (Jan 31, 2017):
I'm curious what types of SAML provider folks are using. My org is using Okta. The implementation of an Okta integration is quite well documented and doesn't seem too intense:
http://developer.okta.com/standards/SAML/
@s0n- commented on GitHub (May 10, 2017):
I would be very interested in Okta integration as well since Bookstack is shaping up to be our corporate Wiki.
@jacksonp2008 commented on GitHub (Sep 18, 2017):
Based on your other auth methods here @ssddanbrown , I don't think OKTA integration would be very difficult for you.
We are very interested in seeing OKTA support, happy to test or help any way we can.
@poVoq commented on GitHub (Sep 23, 2017):
https://github.com/onelogin/php-saml
This seems to be the new go-to lib for open php source projects wishing to implement saml author.
@therealscottcarlow commented on GitHub (Nov 8, 2018):
Bump. My org is very big on SAML SSO and adding this feature to Bookstack would be a phenomenal addition. I would offer to help put it together, but I'm not a PHP developer. I do, however, know quite a bit about SAML if you get around to putting this together and want to bounce questions off of someone.
@cb3inco commented on GitHub (Nov 13, 2018):
+1 for this. Or a way to use headers to inject the users auth details as we are using a service to do this and that way the server can live behind a authentication mechanism.
@t-aus-m commented on GitHub (Nov 30, 2018):
+1, I would also appreciate SSO and SAML a lot, we're using Keycloak currently.
@Orchal commented on GitHub (Dec 12, 2018):
+1, I would appreciate a CAS apereo support too.
@ataraxus commented on GitHub (Jan 24, 2019):
Also looking for a way to use Keycloak with BookStack saml or openid connect would be very appreciated
@koenhendriks commented on GitHub (Feb 11, 2019):
Same here, Our organisation is using Okta and this application as internal Knowledge base. We would love to have SAML authentication for this.
@boblmartens commented on GitHub (Feb 11, 2019):
We would love CAS support as well.
@vsegdacocacola commented on GitHub (Jun 13, 2019):
+1 for SAML
@reavessm commented on GitHub (Jun 18, 2019):
+1 for Keycloak
@KroonCo commented on GitHub (Jul 22, 2019):
+1 for SAML functionality
@ghost commented on GitHub (Jul 22, 2019):
+1 for SAML
@Xiphoseer commented on GitHub (Aug 7, 2019):
I wrote a PR adding SAML support in #1576. It works mostly like a new SAML socialite plugin and uses laravel-saml2, but also mirrors the LDAP support for groups.
@amelie-excent commented on GitHub (Oct 22, 2019):
+1 for SAML
@ssddanbrown commented on GitHub (Nov 17, 2019):
As per #1576 and #1787, Initial SAML2 support has been merged into master and will be in the next feature release, v0.28, which is targeted for about mid/late December. Therefore I will now close this request.
@bendem commented on GitHub (Jan 8, 2020):
I see support was added, but the documentation mentioned here doesn't seem to be available. Is there any other place I can find it?
c055310507/.env.example.complete (L222)@ssddanbrown commented on GitHub (Jan 8, 2020):
Hi @bendem,
This has not yet made a release. The current release is taking a little while longer than expected. That documentation URL will exist after the next release is deployed.