How to validate securityScheme from openapi about openapi-httpfoundation-testing HOT 7 CLOSED

Hi,

I think that's down to how you build your request object? Can't you build it with the proper headers? I don't know in which context you're using the package (Laravel? Test suite?), so I don't know where you get that request object from, nor if you can update and how 🙂

from openapi-httpfoundation-testing.

Request object is constructed using slim. There is a proper header set in request but it gives error. I found that no security headers are set anywhere in OperationAddress.

from openapi-httpfoundation-testing.

Sorry mate, I don't really know. To be honest this looks like it has more to do with Slim and/or using OpenAPI definitions than it does with using this package per se. As you can see the original exception is thrown by the underlying package, so maybe you'd have more luck opening an issue there

from openapi-httpfoundation-testing.

@osteel I can post it there but is there any way to pass security headers when validating request to validator?

from openapi-httpfoundation-testing.

There is no feature to add these headers separately. Again, these headers should already be part of the request object, in my opinion

from openapi-httpfoundation-testing.

Yes, request object already has all the headers, but it's missing from OperationAddress object where we comparing the schemes which is set from the Validators but as you said there is no such feature

from openapi-httpfoundation-testing.

OperationAddress is a class from the package I've mentioned above. Like I said, it's probably an issue better suited for them. Closing this for now, as I believe I answered your question and cannot help you any further

from openapi-httpfoundation-testing.