Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Display securityDefinitions/security #7

Closed
2 of 3 tasks
RomanHotsiy opened this issue Jan 22, 2016 · 10 comments
Closed
2 of 3 tasks

Display securityDefinitions/security #7

RomanHotsiy opened this issue Jan 22, 2016 · 10 comments

Comments

@RomanHotsiy
Copy link
Member

RomanHotsiy commented Jan 22, 2016

  • securityDefinitions
  • add security definitions to the side menu
  • security
@RomanHotsiy RomanHotsiy self-assigned this Jan 22, 2016
@RomanHotsiy RomanHotsiy modified the milestones: Rebilly release, v1.0 Jan 22, 2016
@adamaltman
Copy link
Member

👍

@cayter
Copy link

cayter commented Aug 30, 2016

+1

1 similar comment
@rbaumi
Copy link

rbaumi commented Sep 12, 2016

+1

@RomanHotsiy
Copy link
Member Author

RomanHotsiy commented Nov 1, 2016

securityDefinitions are now rendered in the docs
Also the placement of securityDefinitions can be configured.
Check out details in the docs or check example in the demo spec

@SebastianStehle
Copy link

There are also security information per operation, e.g. you can specify the roles or claims. Would be awesome to support this:

 "security": [
      {
        "roles": []
      }
    ]

@mooop12
Copy link

mooop12 commented May 15, 2017

Any news on this? This is kind of a big deal, most APIs use some kind of authorization. I know this will be important during API console implementation, but maybe until then we could get a placeholder link pointing to the appropriate securityDefinition section?

@robdefeo
Copy link

robdefeo commented Jan 9, 2018

Missing this feature is significant because it does not allow the user to understand what security scopes are required for each operation. With complex API's this is a significant ask. What is the status with this feature?

@RomanHotsiy
Copy link
Member Author

It is being worked on in version 2 (track here: #357)
image

Here is the screenshot of the current implementation. If anyone has a better idea of how to visualize this, please share!

@RomanHotsiy
Copy link
Member Author

Implemented in 2.0-alpha.x

@tPl0ch
Copy link

tPl0ch commented May 23, 2019

@RomanGotsiy is there an npm package for the 2.0-rc* version? We'd like to use this feature but would need to completely change our redoc deployment (which is based on npm install currently).

Regards and many thanks for your work on redoc,
Thomas

RomanHotsiy pushed a commit that referenced this issue Mar 30, 2021
dvkuznietsov added a commit to dvkuznietsov/redoc that referenced this issue Jan 9, 2023
rjaramillo21 added a commit to KUBBESA/redoc that referenced this issue Aug 12, 2024
Adding eCommerce cancel and create documentation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants