BearerAuth token not getting generated (1.3.11) about specmatic HOT 4 CLOSED

Bingo. I was missing the following from my API Spec:

security:
  - bearerAuth: []

After including it, Specmatic started to autogenerate an Authorization header. I was then able to use System.setProperty("bearerAuth", "abcdef"); to set my own token.

It may be worth updating https://specmatic.in/documentation/authentication.html to include some extra detail on setting the security as well as the security scheme.

Thanks!

from specmatic.

The API Spec is being generated using SpringDoc. I do have Stoplight installed and it didn't flag the unused security scheme 😞 Thanks again.

from specmatic.

Hi @noelmccrory, thanks for reaching out.

Looks like you are trying to run contract tests with a specification that has a security scheme defined.

Can you confirm if you are applying this security scheme to the APIs you are trying to test? Here's the documentation on how you can apply the defined security scheme to your APIs.

It would help us if you post a specification that would help us replicate the problem.

from specmatic.

@noelmccrory Glad you figured it out!
Just curious if you use any linters, if yes, it might have highlighted this issue in the spec in your IDE itself.
For example, in the following screenshot the Swagger Editor is telling me that I have not used the defined security scheme anywhere -

While technically Specmatic is operating correctly based on the OpenAPI spec, what we can do is, add the suggestion of using linters in our documentation to help users find out any spec level issues (e.g. unused security scheme) to get early feedback.

Closing this issue for now. Please feel free to reopen if necessary.

from specmatic.