Access swagger-ui after setup to initialize oauth2

Is there an existing issue that is already proposing this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe it

It is not possible to initialize ouath2 parameters.

Looking at the doc https://swagger.io/docs/open-source-tools/swagger-ui/usage/oauth2/

ui.initOAuth({
    clientId: "your-client-id",
    clientSecret: "your-client-secret-if-required",
    realm: "your-realms",
    appName: "your-app-name",
    scopeSeparator: " ",
    scopes: "openid profile",
    additionalQueryStringParams: {test: "hello"},
    usePkceWithAuthorizationCodeGrant: true
  })

Describe the solution you’d like

Either SwaggerModule.setup() should return an instantiated swagger-ui or we should add configuration option that could trigger the setup of ui.initOauth().

Teachability, documentation, adoption, migration strategy

No response

What is the motivation / use case for changing the behavior?

Cannot pre configure oauth2 configuration such as clientId.

[julianklumpers]

You can achieve this with swaggerOptions

SwaggerModule.setup('api', app, document, {
  customSiteTitle: 'Your API',
  swaggerOptions: {
    oauth: {
      clientId: "your-client-id",
      clientSecret: "your-client-secret-if-required",
      realm: "your-realms",
      appName: "your-app-name",
      scopeSeparator: " ",
      scopes: ["openid", "profile"],
      additionalQueryStringParams: {test: "hello"},
      usePkceWithAuthorizationCodeGrant: true
    },
    persistAuthorization: true,
  },
});

[dan-cooke]

Does anybody else find swagger to be just incredibly messy and have a terrible DX.

I almost always advocate for GraphQL purely because of how annoying Swagger is to configure.

Prime example…

Why is there a function initOauth()

But for some reason, you don’t pass theredirectUrl in this part… instead you configure it in the parent swagger options config? as oauth2RedirectUrl

Like come on.