getUser function should fall back to search user api if the user email/login has a '/' character #430
Description
Describe the feature request?
Okta allows creating a user with '/' (forward slash) character in email or login attribute. But the GET /api/v1/user/{email} API returns 405 error when the same email. Looks like this a known limitation of the GET API and is documented here - https://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#get-user-with-login-shortname.
The get user API is used in a LOT of workflows in my organization and updating every place where the getUser function is called from the SDK to include an additional call to search user api is going to be time consuming and inefficient. The ask here is that the SDK's getUSer function should fall back to search user API is it see's a '/' character in the given email, so that the consumers do not need to add this additional logic.
New or Affected Resource(s)
UserApi.getUser() function
Provide a documentation link
Additional Information?
No response