Update to newest version of Swagger UI to support Password Flow

[pdusen]

Since #202 is closed and is not receiving any responses from @domaindrivendev, I'm trying to draw attention to this by opening a new issue.

Password Flow support has landed in swagger-ui Master: swagger-api/swagger-ui#2397

Please update Swashbuckle to make use of the newest version of swagger-ui.

[UnrealKazu]

Pull request #974 could be of interest for this issue. This essentially updates Swagger UI to 2.2.10, which has the new password flow functionality. I too am eager for this to be supported in Swashbuckle.

Though, I am not sure to what extend Swashbuckle itself would need some tinkering in order for password flow to function properly. This, as Swashbuckle provides config settings for the grant type which should be used in Swagger UI.

[aposashenko-distillery]

We're also interested in the password flow.

P.S. thank you guys for your work implementing so cool tool!

[VenomAV]

I have just compiled the latest commit of master and I verified that OAuth2 password flow works correctly. Does anyone know when the new version of the NuGet package will be released?
The parameters of EnableOAuth2Support method are useless since the new version of Swagger UI does not use those configurations any more (at least for the password flow).

[heldersepu]

It seem that the owner is busy with other projects...
But there is a call out for maintainers, see: #1053

[VenomAV]

@heldersepu I saw the call for maintainers and I would like to be helpful. However, at the moment, I do not have enough insights on the inner workings of the library and the overall design to be of any real help.

[clabnet]

I am very interested to this update.

[Astimus]

I am very interested too. Authorization works great. But after there is no authorization header in requests to api. Is this will be solved after upgrade?

[heldersepu]

All we need is a new version of the NuGet package...
Anyone in a rush I will recommend the solution from VenomAV: #986 (comment)

[heldersepu]

I've been working on my fork, I updated to the latest Swagger-UI (3.x), here is how it looks on one of my projects:
http://turoapi.azurewebsites.net/swagger/ui/index

If you have time I could use your help testing it, you can get my version from MyGet:
https://www.myget.org/gallery/swashbuckle

[domaindrivendev]

SB v5.6.0 ships with swagger-ui 2.2.10 and is now available on Nuget. I believe this resolves the original issue. @pdusen - please let me know if this isn't the case. Thanks

[UnrealKazu]

@domaindrivendev It seems like the way authorization settings are configured in Swagger UI have been changed. This means that the corresponding EnableOAuth2Support method is no longer working, like @VenomAV already mentioned.

So this isn't a clear-cut 'upgrade Swagger-UI and everything is fixed'-solution, unfortunately. It does seem that there isn't too much needed to make Swashbuckle work with those new settings, though.

[ai-fwd]

@UnrealKazu if possible can you elaborate on the changes required to make Swashbuckle work with the new settings so it's a little more turnkey for the rest of us? Using the V5.6 which ships with swagger-ui 2.2.10