SAML integration with JumpCloud #2314

New Issue

OVERLORD · 2026-02-05T03:38:10+03:00

OVERLORD commented

2026-02-05 03:38:10 +03:00

Originally created by @galeido on GitHub (Jul 7, 2021).

Describe the bug
We have tried to do SAML integration against JumpCloud. Unfortunately, based on the configuration example in the documentation and GitHub. We have not made this integration work.

The app debug log gives the following error message

Exception
Error on parseRemoteXML. Error parsing metadata. DOMDocument::loadXML(): Opening and ending tag mismatch: link line 1 and head in Entity, line: 1

Steps To Reproduce
Steps to reproduce the behavior:

Create a JumpCloud user account
Create a new Custom SAML application in JumpCloud
Add the required information to the Custom SAML application based on the instructions in the BookStack wiki
Add the following lines to the BookStack configuration

SAML2_NAME = "JumpCloud SSO"
SAML2_ENABLED = true
SAML2_AUTO_REGISTER = true
SAML2_EMAIL_ATTRIBUTE = email
SAML2_DISPLAY_NAME_ATTRIBUTES = displayName
SAML2_EXTERNAL_ID_ATTRIBUTE = uid
SAML2_IDP_ENTITYID = https: //sso.jumpcloud.com/saml2/$example
SAML2_AUTOLOAD_METADATA = true

Enable app debug log
APP_DEBUG=true

Expected behavior
The purpose is to be directed to the login of the JumpCloud service

Screenshots
N/A

Your Configuration (please complete the following information):

Exact BookStack Version (Found in settings): v21.05.3
PHP Version: 7.3.27
Hosting Method (Nginx/Apache/Docker): Caddy reverse proxy + Docker (linuxserver.io)

Additional context
N/A

Originally created by @galeido on GitHub (Jul 7, 2021). **Describe the bug** We have tried to do SAML integration against JumpCloud. Unfortunately, based on the configuration example in the documentation and GitHub. We have not made this integration work. The app debug log gives the following error message Exception Error on parseRemoteXML. Error parsing metadata. DOMDocument::loadXML(): Opening and ending tag mismatch: link line 1 and head in Entity, line: 1 **Steps To Reproduce** Steps to reproduce the behavior: 1) Create a JumpCloud user account 2) Create a new Custom SAML application in JumpCloud 3) Add the required information to the Custom SAML application based on the instructions in the BookStack wiki 4) Add the following lines to the BookStack configuration ``` SAML2_NAME = "JumpCloud SSO" SAML2_ENABLED = true SAML2_AUTO_REGISTER = true SAML2_EMAIL_ATTRIBUTE = email SAML2_DISPLAY_NAME_ATTRIBUTES = displayName SAML2_EXTERNAL_ID_ATTRIBUTE = uid SAML2_IDP_ENTITYID = https: //sso.jumpcloud.com/saml2/$example SAML2_AUTOLOAD_METADATA = true ``` 5) Enable app debug log APP_DEBUG=true **Expected behavior** The purpose is to be directed to the login of the JumpCloud service **Screenshots** N/A **Your Configuration (please complete the following information):** - Exact BookStack Version (Found in settings): v21.05.3 - PHP Version: 7.3.27 - Hosting Method (Nginx/Apache/Docker): Caddy reverse proxy + Docker (linuxserver.io) **Additional context** N/A

OVERLORD added the 🐕 Support 🚪 Authentication labels 2026-02-05 03:38:10 +03:00

OVERLORD closed this issue

2026-02-05 03:38:14 +03:00

OVERLORD commented

2026-02-05 03:38:18 +03:00

@ssddanbrown commented on GitHub (Jul 12, 2021):

Hi @galeido,
Just had a play using a trial JumpCloud account. I was able to get things working as expected without too much of an issue.

One thing I noticed, You can directly access the metadata at the IDP URL which BookStack expects when autoloading metadata which may be what's producing that error. Instead I set SAML2_AUTOLOAD_METADATA to false and exported my metadata from within JumpCloud and then used the values in that file to set my SAML2_IDP_x509 and SAML2_IDP_SSO values directly.

So in the end my .env file looked something like this:

SAML2_NAME="JumpCloud"
SAML2_EMAIL_ATTRIBUTE="email"
SAML2_EXTERNAL_ID_ATTRIBUTE="email"
SAML2_DISPLAY_NAME_ATTRIBUTES="firstname|lastname"
SAML2_IDP_ENTITYID=https://sso.jumpcloud.com/saml2/bookstack
SAML2_IDP_SSO=https://sso.jumpcloud.com/saml2/bookstack
SAML2_AUTOLOAD_METADATA=false
SAML2_IDP_x509="<big long cert string here>"

@ssddanbrown commented on GitHub (Jul 12, 2021): Hi @galeido, Just had a play using a trial JumpCloud account. I was able to get things working as expected without too much of an issue. One thing I noticed, You can directly access the metadata at the IDP URL which BookStack expects when autoloading metadata which may be what's producing that error. Instead I set `SAML2_AUTOLOAD_METADATA` to false and exported my metadata from within JumpCloud and then used the values in that file to set my `SAML2_IDP_x509` and `SAML2_IDP_SSO` values directly. So in the end my `.env` file looked something like this: ```bash SAML2_NAME="JumpCloud" SAML2_EMAIL_ATTRIBUTE="email" SAML2_EXTERNAL_ID_ATTRIBUTE="email" SAML2_DISPLAY_NAME_ATTRIBUTES="firstname|lastname" SAML2_IDP_ENTITYID=https://sso.jumpcloud.com/saml2/bookstack SAML2_IDP_SSO=https://sso.jumpcloud.com/saml2/bookstack SAML2_AUTOLOAD_METADATA=false SAML2_IDP_x509="<big long cert string here>" ```

OVERLORD commented

2026-02-05 03:38:21 +03:00

@galeido commented on GitHub (Jul 12, 2021):

@ssddanbrown

Thank you, great work! How about the settings for the custom SAML application on JumpCloud?

@galeido commented on GitHub (Jul 12, 2021): @ssddanbrown Thank you, great work! How about the settings for the custom SAML application on JumpCloud?

OVERLORD commented

2026-02-05 03:38:28 +03:00

@ssddanbrown commented on GitHub (Jul 12, 2021):

@galeido Details below, I didn't play around with the settings too much to be honest, Might be some improvements to be made.

@ssddanbrown commented on GitHub (Jul 12, 2021): @galeido Details below, I didn't play around with the settings too much to be honest, Might be some improvements to be made. ![Screen Shot 2021-07-12 at 21 45 47](https://user-images.githubusercontent.com/8343178/125353517-9289d380-e35a-11eb-8a93-651f220234b1.png)

OVERLORD commented

2026-02-05 03:38:31 +03:00

@galeido commented on GitHub (Jul 13, 2021):

I can confirm configuration works in our test environment in production mode.

The ticket can be closed as a completed.

Thank you very much for your help.

@galeido commented on GitHub (Jul 13, 2021): I can confirm configuration works in our test environment in production mode. The ticket can be closed as a completed. Thank you very much for your help.

OVERLORD commented

2026-02-05 03:38:33 +03:00

@ssddanbrown commented on GitHub (Jul 13, 2021):

@galeido Happy to have helped, And thank you very much for the sponsorship.

@ssddanbrown commented on GitHub (Jul 13, 2021): @galeido Happy to have helped, And thank you very much for the sponsorship.

OVERLORD referenced this issue

2026-02-05 04:09:44 +03:00

[CSS] More declarations in dark-mode #2442

OVERLORD referenced this issue

2026-02-05 04:36:36 +03:00

Reduce sidebar fade when in dark mode for better legibility #2606

OVERLORD referenced this issue