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

Content-Type application/scim+json isn't creating a corresponding "consumes" section #72

Open
scarpent opened this issue Oct 10, 2023 · 2 comments

Comments

@scarpent
Copy link

I'm using v1.16.1, and have some apib like this:

### Create a user [POST /api/scim/v2/Users]

+ Request
    + Headers

            Content-Type: application/scim+json
            Authorization: Bearer token

    + Body

            {
                "schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"],
                "userName": "fredsmith",
                "name": {
                    "givenName": "Fred",
                    "familyName": "Smith"
                },
                "emails": [
                    {"primary": true, "value": "fred@example.com", "type": "work"}
                ],
                "displayName": "Fred Smith",
                "externalId": "fred-external-id",
                "active": true
            }

+ Response 201 (application/scim+json)

    + Attributes (ExistingUser)

When producing the swagger json, it creates a produces section, but not consumes, which then causes a UI viewer to default (I'm assuming) to application/json for "content type" and "request body schema". If I add the consumes section myself, it displays correctly.

"produces": [
    "application/scim+json"
],
"consumes": [
    "application/scim+json"
],

Thank you!

@kminami
Copy link
Owner

kminami commented Oct 21, 2023

I have released v1.17.0 to support consumes for swagger 2.0.
Please confirm it, thank you!

@scarpent
Copy link
Author

Works perfectly. 🚀 Thank you so much! 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants