refactor: expose swagger UI to enable OAuth2 try-it-out in upstream applications

[andrewwylde]

Summary

This is a Proof-of-Concept to attempt a fix to some issues in an upstream repository (konnect-portal). The issue is that for client-side-only OIDC "Try It Out" authorization, one needs to be able to initialize oauth with certain values available.

More info!

For SPA-based requests to the /authorize endpoint, one needs to invoke the following (where swaggerUI is an instance that has already been initialized.

swaggerUI.initOAuth({
          usePkceWithAuthorizationCodeGrant: true,
          additionalQueryStringParams: {
            nonce: Math.random().toString(36).substring(7)
          }
        })

Rather than initializing that within spec-renderer (really within swagger-ui-web-component), I think the better move is to allow more flexibility and to expose #instance so that folks can call it from the consuming application.

Open to differing opinions, this is just how we got things working for our use case: https://gist.github.com/andrewwylde/d47c94c7629a81a0232ac80ef862e788

[Mierenga]

👍

[adamdehaven]

@andrewwylde can you add your team to the CODEOWNERS for this package?

public-ui-components/CODEOWNERS

Line 40 in 57142b2

/packages/portal/swagger-ui-web-component/ @adamdehaven @davidma415 @kaiarrowood @mptap

[nateslo]

@andrewwylde can you add your team to the CODEOWNERS for this package?

public-ui-components/CODEOWNERS

Line 40 in 57142b2

/packages/portal/swagger-ui-web-component/ @adamdehaven @davidma415 @kaiarrowood @mptap

Added Devx as codeowners here #1266