Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pulled in latest upstream changes for improved standards-compliance #12159

Merged
merged 1 commit into from
Nov 28, 2022

Conversation

uberbrady
Copy link
Collaborator

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 for SCIM_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).

@what-the-diff
Copy link

what-the-diff bot commented Nov 22, 2022

  • The key "standards_compliance" was changed to "omit_main_schema_in_return".
  • The default value of the new key is set by env('SCIM-STANDARDS-COMPLIANCE', false).

@snipe snipe merged commit 9aa0356 into snipe:develop Nov 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants