You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For generated collection from definition, some of Auth values are placeholder values which doesn't help much. These values should be environment variables for easier usage.
For example with below schema, generated collection will have auth value as <Bearer Token>. This can be {{bearer_token}} so users can consume them directly as variables instead of doing manual changes. This applies to all kind of authorization types.
openapi: "3.0.0"
info:
version: 1.0.0
title: Swagger Petstore
license:
name: MIT
servers:
- url: https://postman-echo.com/get
security:
- bear: []
paths:
/pets/{petId}:
get:
summary: Info for a specific pet
operationId: showPetById
tags:
- pets
parameters:
- name: petId
in: path
required: true
description: The id of the pet to retrieve
schema:
type: string
responses:
default:
description: unexpected error
content:
application/json:
schema:
$ref: "#/components/schemas/Error"
components:
schemas:
Error:
type: object
required:
- code
- message
properties:
code:
type: integer
format: int32
message:
type: string
securitySchemes:
bear:
type: http
scheme: bearer
bearerFormat: JWT
The text was updated successfully, but these errors were encountered:
For generated collection from definition, some of Auth values are placeholder values which doesn't help much. These values should be environment variables for easier usage.
For example with below schema, generated collection will have auth value as
<Bearer Token>
. This can be{{bearer_token}}
so users can consume them directly as variables instead of doing manual changes. This applies to all kind of authorization types.The text was updated successfully, but these errors were encountered: