How to configure the client to use basic authentication if OpenAPI is behind basic auth?

[ddhanak]

How to configure the client to use basic authentication if OpenAPI is behind basic auth?
From my understanding this is currently not possible?

[mrlubos]

@ddhanak are you using the standalone client? (Fetch or Axios)

[ddhanak]

@mrlubos I am using the Axios client, here is my config:

import { defineConfig } from "@hey-api/openapi-ts";

const DEFAULT_URL = "https://my.api.com";

export default defineConfig({
  base: DEFAULT_URL,
  plugins: ["@tanstack/react-query"],
  client: {
    name: "@hey-api/client-axios"
  },
  input: `${DEFAULT_URL}/openapi.json`,
  output: {
    path: "./api/client",
    format: "prettier",
    lint: "eslint"
  },
  types: {
    enums: "typescript",
    name: "PascalCase"
  }
});

https://my.api.com/openapi.json is behind basic http auth.

[mrlubos]

And are you not able to accomplish the auth using interceptors?

I see Axios has a built-in support for it https://stackoverflow.com/a/44239543

[ddhanak]

I can successfully use interceptors but only after the client is generated. Right now I get a 401 when trying to generate the services. I am not sure how I can configure the client that is used to fetch the OpenAPI specification.

[mrlubos]

Oh wait, are you asking how to fetch the spec behind auth? You could use programmatic access to call the generator from TypeScript once you have the spec. How you get the spec is then up to you. There's no current support for different security schemes, think there's an issue related to this

[ddhanak]

@mrlubos it seems like the underlying library that is used to fetch the schema supports adding additional headers/options.

from my understanding, this is where we could potentially add some additional configuration.

Update: that's a valid solution. Thank you for your help (and this amazing library!).

[mrlubos]

Yep! I didn't decide yet what to do with that package, but that would be a potential route if we keep using it