mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-07-16 05:33:49 +03:00
GuzzleHttp\Exception\ClientException Client error: POST https://login.microsoftonline.com/common/oauth2/token resulted in a 401 Unauthorized response
#1712
Closed
opened 2026-02-05 01:41:26 +03:00 by OVERLORD
·
10 comments
No Branch/Tag Specified
development
l10n_development
release
snyk-action
ci_and_static
mfa_key
phpstan_june26
MilnerMart/development
GamerClassN7/impersonations-for-admin
Zhey-on/feature/csp-image-css-controls-6033
tortillas5/development
llm_only
vectors
McTom234/oidc-key-algorithms
captcha_example
v26.05.2
v26.05.1
v26.05
v26.03.5
v26.03.4
v26.03.3
v26.03.2
v26.03.1
v26.03
v25.12.9
v25.12.8
v25.12.7
v25.12.6
v25.12.5
v25.12.4
v25.12.3
v25.12.2
v25.12.1
v25.12
v25.11.6
v25.11.5
v25.11.4
v24.11.4
v25.11.3
v25.11.2
v25.11.1
v25.11
v25.07.3
v25.07.2
v25.07.1
v25.07
v25.05.2
v25.05.1
v25.05
v25.02.5
v25.02.4
v25.02.3
v25.02.2
v25.02.1
v25.02
v24.12.1
v24.12
v24.10.3
v24.10.2
v24.10.1
v24.10
v24.05.4
v24.05.3
v24.05.2
v24.05.1
v24.05
v24.02.3
v24.02.2
v24.02.1
v24.02
v23.12.3
v23.12.2
v23.12.1
v23.12
v23.10.4
v23.10.3
v23.10.2
v23.10.1
v23.10
v23.08.3
v23.08.2
v23.08.1
v23.08
v23.06.2
v23.06.1
v23.06
v23.05.2
v23.05.1
v23.05
v23.02.3
v23.02.2
v23.02.1
v23.02
v23.01.1
v23.01
v22.11.1
v22.11
v22.10.2
v22.10.1
v22.10
v22.09.1
v22.09
v22.07.3
v22.07.2
v22.07.1
v22.07
v22.06.2
v22.06.1
v22.06
v22.04.2
v22.04.1
v22.04
v22.03.1
v22.03
v22.02.3
v22.02.2
v22.02.1
v22.02
v21.12.5
v21.12.4
v21.12.3
v21.12.2
v21.12.1
v21.12
v21.11.3
v21.11.2
v21.11.1
v21.11
v21.10.3
v21.10.2
v21.10.1
v21.10
v21.08.6
v21.08.5
v21.08.4
v21.08.3
v21.08.2
v21.08.1
v21.08
v21.05.4
v21.05.3
v21.05.2
v21.05.1
v21.05
v21.04.6
v21.04.5
v21.04.4
v21.04.3
v21.04.2
v21.04.1
v21.04
v0.31.8
v0.31.7
v0.31.6
v0.31.5
v0.31.4
v0.31.3
v0.31.2
v0.31.1
v0.31.0
v0.30.7
v0.30.6
v0.30.5
v0.30.4
v0.30.3
v0.30.2
v0.30.1
v0.30.0
v0.29.3
v0.29.2
v0.29.1
v0.29.0
v0.28.3
v0.28.2
v0.28.1
v0.28.0
v0.27.5
v0.27.4
v0.27.3
v0.27.2
v0.27.1
v0.27
v0.26.4
v0.26.3
v0.26.2
v0.26.1
v0.26.0
v0.25.5
v0.25.4
v0.25.3
v0.25.2
v0.25.1
v0.25.0
v0.24.3
v0.24.2
v0.24.1
v0.24.0
v0.23.2
v0.23.1
v0.23.0
v0.22.0
v0.21.0
v0.20.3
v0.20.2
v0.20.1
v0.20.0
v0.19.0
v0.18.5
v0.18.4
v0.18.3
v0.18.2
v0.18.1
v0.18.0
v0.17.4
v0.17.3
v0.17.2
v0.17.1
v0.17.0
v0.16.3
v0.16.2
v0.16.1
v0.16.0
v0.15.3
v0.15.2
v0.15.1
v0.15.0
v0.14.3
v0.14.2
v0.14.1
v0.14.0
v0.13.1
v0.13.0
v0.12.2
v0.12.1
v0.12.0
v0.11.2
v0.11.1
v0.11.0
v0.10.0
v0.9.3
v0.9.2
v0.9.1
v0.9.0
v0.8.2
v0.8.1
v0.8.0
v0.7.6
v0.7.5
v0.7.4
v0.7.3
0.7.2
v.0.7.1
v0.7.0
v0.6.3
v0.6.2
v0.6.1
v0.6.0
v0.5.0
Labels
Clear labels
🎨 Design
📖 Docs Update
🐛 Bug
🐛 Bug
:cat2:🐈 Possible duplicate
💿 Database
☕ Open to discussion
💻 Front-End
🐕 Support
🚪 Authentication
🌍 Translations
🔌 API Task
🏭 Back-End
⛲ Upstream
🔨 Feature Request
🛠️ Enhancement
🛠️ Enhancement
🛠️ Enhancement
❤️ Happy feedback
🔒 Security
🔍 Pending Validation
💆 UX
📝 WYSIWYG Editor
🌔 Out of scope
🔩 API Request
:octocat: Admin/Meta
🖌️ View Customization
❓ Question
🚀 Priority
🛡️ Blocked
🚚 Export System
♿ A11y
🔧 Maintenance
> Markdown Editor
pull-request
Mirrored from GitHub Pull Request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/BookStack#1712
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking 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 @amahmou on GitHub (May 5, 2020).
Hi,
i can t login with Microsoft AZURE ( qith MFA activated ) on my Bookstack
Steps To Reproduce
Steps to reproduce the behavior:
LOG :
https://flareapp.io/share/47qVaa5W#F57
@ssddanbrown commented on GitHub (Jun 30, 2020):
Hi @amahmou,
Sorry for my late reply.
In the error message, it looks like microsoft is providing the message "Invalid client secret".
Can you double check the value of the secret that you have configured in your BookStack
.envfile?Does it contain any special characters or spaces?
@danielslyman commented on GitHub (Jul 24, 2020):
I have the same issue unfortunately, and yes, my secret do have special characters. Any way to fix this?
Thank,
Daniel
@danielslyman commented on GitHub (Jul 24, 2020):
uzzleHttp\Exception\ClientException
Client error:
POST https://login.microsoftonline.com/common/oauth2/tokenresulted in a401 Unauthorizedresponse: {"error":"invalid_client","error_description":"AADSTS7000215: Invalid client secret is provided.\r\nTrace ID: 2e46836e-e (truncated...)@danielslyman commented on GitHub (Jul 24, 2020):
This may help:
https://stackoverflow.com/questions/41133573/microsoft-graph-rest-api-invalid-client-secret
@danielslyman commented on GitHub (Jul 27, 2020):
@ssddanbrown - could you please please help? This would be perfect for our organisation but we need this integration to make it workable for us.
@ssddanbrown commented on GitHub (Jul 28, 2020):
@danielslyman Can you try wrapping the secret in quotes within the
.envfile? So like:Otherwise, can you rengerate the key in azure?
Otherwise, please can you confirm your BookStack version & confirm if you have MFA active in azure.
@danielslyman commented on GitHub (Jul 28, 2020):
I can confirm that wrapping the secret in quotes rather than brackets does the trick! Thanks so much for helping :)
It may be useful to change the hint in the .env file:
"# Replace the below (including '{}' braces) with your azure APP_ID and APP_SECRET and TENANT"
@danielslyman commented on GitHub (Jul 28, 2020):
Follow-up:
What would be the easiest way to hide the regular login form? Are those css classes/ids used elsewhere or can I simply do a display: none; ?
Thanks,
Daniel
@ssddanbrown commented on GitHub (Jul 28, 2020):
@danielslyman Awesome, Glad that worked. Will therefore close this off.
For the login form, you could use the action of the form itself, like so:
@danielslyman commented on GitHub (Aug 1, 2020):
I can confirm this works perfectly, should remove the confusion for staff. I also opted for the snippet below, removing the + hr to retain the line separator - looks more pleasing to me.
Thank you so much!