Relative path in OAuth 2.0 authorizationUrl is allowed in OAS 3?

78 views
Skip to first unread message

Yuto SASAKI

unread,
Dec 5, 2017, 2:12:47 AM12/5/17
to Swagger
Hi,

I've found that the doc says 

The authorization URL to use for this flow. Can be relative to the API server URL.

and Swagger Editor does not complaint about the following definition:

  securitySchemes:
    petstore_auth:
      type: oauth2
      flows:
        implicit:
          authorizationUrl: oauth/dialog
          scopes:
            write:pets: modify pets in your account
            read:pets: read your pets

However, it seems that Swagger UI goes to own server not the API server.

Is this a UI bug, or a documentation bug?

Ron Ratovsky

unread,
Dec 5, 2017, 12:40:38 PM12/5/17
to swagger-sw...@googlegroups.com

Looks like a UI bug. Can you file a ticket with the project?

--
You received this message because you are subscribed to the Google Groups "Swagger" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
swagger-swaggers...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.

Yuto SASAKI

unread,
Dec 6, 2017, 1:32:58 AM12/6/17
to Swagger
Thanks for the reply!
I filed an issue https://github.com/swagger-api/swagger-ui/issues/3992

2017年12月6日水曜日 2時40分38秒 UTC+9 Ron:

To unsubscribe from this group and stop receiving emails from it, send an email to swagger-swaggersocket+unsub...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages