Pulled in latest upstream changes for improved standards-compliance #12159
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The original version of the laravel-scim-server package that we use for our SCIM support has made a few updates that I wanted to take in. Furthermore, our SCIM support with the new
.env
var forSCIM_STANDARDS_COMPLIANCE
had a few bugs that dropped 500-series errors. So this change goes along with those updates to our fork of the library, so it uses the new config variable (upstream chose a different config variable name), and the new functionality (which is much less hacky than what I built before).