karlk
January 8, 2026, 9:23pm
#1
We have been running a couple installations of Corteza for quite some time, with single-sign on via Azure (aka Active Directory) - and suddenly this morning the single-sign on stopped working for both of them. Has anyone else noticed similar problems?
My guess is that microsoft rolled out some change to Azure that we don’t know about (and perhaps was not well tested?) but that’s just a theory.
For anyone who may have encountered something similar lately, we were able to resolve this issue.
We created a PR for this for those interested:
cortezaproject:2024.9.x ← manuelnelson:2024.9.x-fix-oauth-handler
opened 02:39PM - 15 Jan 26 UTC
Our Azure OAuth recently broke. It turns out, the token being returned was larg… er than 1024 characters, and the validFormPost was failing and not allowing users to login. With 200+ users, this was a pretty big issue for us, since this is our primary/secure way of logging in.
# The following changes are implemented
Form size validation is now only applied to POST, PUT, and PATCH requests. This allows GET requests with long query parameters, such as OIDC callbacks, to bypass the form size check.
# Changes in the user interface:
None
# Checklist when submitting a final (!draft) PR
- [x] Commits are tidied up, squashed if needed and follow guidelines in CONTRIBUTING.md
- [x] Code builds
- [x] All existing tests pass
- [ ] All new critical code is covered by tests
- [ ] PR is linked to the relevant issue(s)
- [ ] Rebased with the target branch
There previously wasn't an issue for this so I didn't link to it. Also, since it's a one-liner, I didn't add any new tests for this. I'm not really a Go developer, so let me know if this is all good. Also open to other ways of fixing this issue, but this is what I thought was the most innocuous.
1 Like