<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "type::bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary If a GitLab.com group has a dot or period in its name, API endpoint calls fail with an `Invalid JSON: Unexpected character` error. ### Steps to reproduce 1. Have a group with a `.` in the name. 2. Configure SAML auth with Okta 3. Configure SCIM with Okta's Marketplace GitLab app 4. When at the test phase, the app will fail with the attached message: [Okta-SCIM-Fail](/uploads/c0bde42b96a76367a4e747e85567b9c4/Okta-SCIM-Fail.png) ### Example Group https://gitlab.com/alvins-test.ai (admin access required to view) This shows the group name that I tested with. You will not be able to view the error as it appears in the SCIM app logs. ### What is the current *bug* behavior? Okta's auth test fails ### What is the expected *correct* behavior? Okta's auth test should pass ### Relevant logs and/or screenshots - Attached screenshot of failure message in Okta SCIM app  - [Kibana link to the endpoint call](https://log.gprd.gitlab.net/app/r/s/2N7Md) ### Possible workarounds Note: URL encoded the path to use `%2E` does not work. 1. Rename the group path ### Proposal See https://gitlab.com/gitlab-org/gitlab/-/issues/429500#note_1620852643 for suggested fix