Skip to content

ASP.NET Core templates that include both Open API and Authentication should include scaffolding for Swagger to authenticate users. #36185

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
Closed
drchilds opened this issue Sep 4, 2021 · 2 comments
Closed

ASP.NET Core templates that include both Open API and Authentication should include scaffolding for Swagger to authenticate users. #36185

drchilds opened this issue Sep 4, 2021 · 2 comments
Assignees
@captainsafia
Labels
enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-openapi feature-templates old-area-web-frameworks-do-not-use *DEPRECATED* This label is deprecated in favor of the area-mvc and area-minimal labels Priority:1 Work that is critical for the release, but we could probably ship without
Milestone
7.0-preview6

Comments

@drchilds
Copy link

drchilds commented Sep 4, 2021

As of .NET 6 Preview 7, no Swagger authentication scaffolding is included in projects generated from templates that offer both Authentication and Open API. At the very least, a comment should be included that points to docs on how to configure.
@Pilchie Pilchie added feature-openapi area-mvc Includes: MVC, Actions and Controllers, Localization, CORS, most templates feature-templates labels Sep 7, 2021
@mkArtakMSFT mkArtakMSFT added enhancement This issue represents an ask for new feature or an enhancement to an existing one old-area-web-frameworks-do-not-use *DEPRECATED* This label is deprecated in favor of the area-mvc and area-minimal labels and removed area-mvc Includes: MVC, Actions and Controllers, Localization, CORS, most templates labels Sep 7, 2021
@BrennanConroy BrennanConroy added this to the .NET 7 Planning milestone Sep 14, 2021
@captainsafia captainsafia mentioned this issue Oct 1, 2021
Closed
@rafikiassumani-msft rafikiassumani-msft added Cost:S Priority:1 Work that is critical for the release, but we could probably ship without labels Jan 25, 2022
@ghost
Copy link

ghost commented Mar 14, 2022

Thanks for contacting us.

We're moving this issue to the .NET 7 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@rafikiassumani-msft
Copy link
Contributor

dupe #39761

@ghost ghost locked as resolved and limited conversation to collaborators Jul 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@captainsafia captainsafia

Labels
enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-openapi feature-templates old-area-web-frameworks-do-not-use *DEPRECATED* This label is deprecated in favor of the area-mvc and area-minimal labels Priority:1 Work that is critical for the release, but we could probably ship without
Projects
None yet
Milestone
7.0-preview6
Development

No branches or pull requests
6 participants
@Pilchie @captainsafia @drchilds @BrennanConroy @mkArtakMSFT @rafikiassumani-msft