Relative URL for openIdConnectUrl fails validation about oas-kit HOT 6 CLOSED

OAI/OpenAPI-Specification#1270

from oas-kit.

Yes, with the PR still being a work-in-progress, not all of the comments have been incorporated yet. In addition, the schema here has a bunch of descriptions ported over from OAI/OpenAPI-Specification#1236

from oas-kit.

The fix to the schema has been included in swagger2openapi v3.0.x. Thanks for your patience.

from oas-kit.

Thanks for raising the issue and including an example.

The problem was actually in the OAS draft schema (which the validator uses as a fallback).

The openIdConnectUrl was defined as:

                 },
                 "openIdConnectUrl": {
                    "type": "string",
                    "format": "url"
                 },

When it should have been format: uriref.

This explains the similar behaviour of swagger-editor / swagger-ui - they are presumably using the same schema to drive validation, though I believe they are not using this project's (hand written) validator.

We are waiting on a dependency to come out of beta before cutting a new release, but if your requirement is urgent I can go back to the 2.11.x branch and make a patch. Please let me know.

from oas-kit.

This is not urgent for me, I can possibly use an absolute URL for now, or just wait until it is fixed to switch from my current security scheme to openIdConnect.

You mentioned the 'OAS draft schema', where is that located?

from oas-kit.

I looked at that PR, and it looks like this comment also called out the format mismatch, but must have been missed.

OAI/OpenAPI-Specification#1270 (comment)

from oas-kit.