Discussions

During PATCH, “login-disabled” is not getting updated to Boolean true As per API reference document <https://developer.degreed.com/reference/patch_api-v2-users-id> "Ability for the user to login."

During PATCH, “bio” field is accepting more than 2000 characters As per API reference document : <https://developer.degreed.com/reference/patch_api-v2-users-id> "Short biography of the user. The maximum length is 2000 characters." PATCH is not validating with more than 2000 characters. During POST is it throwing error: "source": "field bio has the following problem: The length of 'Bio' must be 2000 characters or fewer. You entered 2958 characters." And During patch it is accepting more then 2000 characters.

During PATCH, password field is accepting less then 8 characters. "password" : "123" Note: During POST it is working fine.

We are not able to update "personal-email" using PATCH Method if it is not NULL, Using rest API. "source": "field personal-email has the following problem: The attribute 'personal-email' can only be updated when the existing value is null" Updating the personal-email from [[email protected]](mailto:[email protected]) to [[email protected]](mailto:[email protected])

"Organization Email" in PATCH Request is accepting invalid email id's. During POST it is throws "can't be null", instead of invalid organization email. During POST got below error for incorrect Organization email. "organization-email": "byreyesallegisgroupcom", "source": "field organization-email has the following problem: can't be empty" <br /> During PATCH its accepts the incorrect Organization email. "organization-email": "byreyesallegisgroupcom"

We are not able to view “privacyLevel” in GET user responses using REST API.

Using rest API once we delete a user, We are getting error: “Unable to create user: User already exists in database.” and unable to create again same user. We are not able to get the deleted user using GET method.

When i pass 'next' query parameter it still returns first set.

I saw in the docs access token endpoint returns expires_in. Is the number in seconds or milliseconds

Can we have a `/.well-known/openid-configuration` as described in [RFC8414](https://datatracker.ietf.org/doc/html/rfc8414) ?