[BUG][JAVA Native] No way to set bearer token

[inemtsev]

Description

We are providing the following in our spec:

components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT

# and for each endpoint
      security:
        - bearerAuth: [ ]

But, there generated java client provides no way to set the bearer token :(

I am using the latest generator version available with the following configuration:

openApiGenerate {
    generatorName.set("java")
    inputSpec.set(localSpecFile.path)
    outputDir.set("${buildDir}/generated")
    modelPackage.set("com.companyName.capi.generated.model")
    apiPackage.set("com.companyName.capi.generated.api")
    packageName.set("com.companyName.capi.generated")
    configOptions.set(
        mapOf(
            "library" to "native",
            "asyncNative" to "true",
            "dateLibrary" to "java8"
        )
    )
}

openapi-generator version

Using generator 7.14.0

Suggest a fix

I am either missing some approach, or this is a bug.

[verhasi]

@inemtsev I suppose you are using the gradle plugin to generate java sources. I have a similar experience using maven. Configuring the inputSpecRootDirectory to make the config smaller I got an ApiClient without any option to set the auth even though the spec file has details about it. By documentation the inputSpecRootDirectory is only the common starting point for the spec files but looking at the source of Generate.java

 @Override
    public void execute() {
        if (StringUtils.isNotBlank(inputSpecRootDirectory)) {
            spec = new MergedSpecBuilder(inputSpecRootDirectory, StringUtils.isBlank(mergedFileName) ? "_merged_spec" : mergedFileName)
                    .buildMergedSpec();
            System.out.println("Merge input spec would be used - " + spec);
        }

it is clear that it creates a merged spec file as soon as you define the directory. Looking at the merged spec file the full component tag is skipped and only the paths are referenced. Going back to full path giving the input spec it is working perfectly.
In case of the gradle there is an option

    /**
     * Skip bundling all spec files into a merged spec file, if true.
     *
     * Default false.
     */
    val inputSpecRootDirectorySkipMerge = project.objects.property<Boolean>()

that promises to skip merging. May be it could be a workaround for you until this side effect bug is fixed.

[verhasi]

relates to #21130