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.

Sign up for GitHub

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

Jump to bottom

Provide description of the security definition #6039

Open
zregvart opened this issue Jul 2, 2019 · 1 comment
Open

Provide description of the security definition #6039

zregvart opened this issue Jul 2, 2019 · 1 comment
Labels
cat/enhancement Enhancements to existing features and capabilities group/server REST backend for managing integrations notif/triage The issue needs triage. Applied automatically to all new issues. status/never-stale Marker that this issue should not be marked as stale

Comments

@zregvart
Copy link
Member

zregvart commented Jul 2, 2019

This is a...


[x] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Documentation issue or request

Description

The OpenAPI 2.0 (Swagger) specification allows for the description to be present in the security definitions. When we present the choice to the user to select one security definition based on which the authentication related properties will be configured for the new custom API connector we only display the kind (Basic Authentication, OAuth, API Key) we don't display that description, if present.

We should also display the description to make it easier for the user to pick the security definition/authentication method for the new custom API connector.
@zregvart zregvart added group/server REST backend for managing integrations cat/enhancement Enhancements to existing features and capabilities labels Jul 2, 2019
@pure-bot pure-bot bot added the notif/triage The issue needs triage. Applied automatically to all new issues. label Jul 2, 2019
@stale
Copy link

stale bot commented Sep 30, 2019

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

@stale stale bot added the status/stale Issue considered to be stale so that it can be closed soon label Sep 30, 2019
@zregvart zregvart added the status/never-stale Marker that this issue should not be marked as stale label Sep 30, 2019
@stale stale bot removed the status/stale Issue considered to be stale so that it can be closed soon label Sep 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cat/enhancement Enhancements to existing features and capabilities group/server REST backend for managing integrations notif/triage The issue needs triage. Applied automatically to all new issues. status/never-stale Marker that this issue should not be marked as stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@zregvart