Rust sdk: Basic/oauth/bearer/api_key auth unused

[Dig-Doug]

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• This issue affects my Ory Cloud project.
• I have joined the Ory Community Slack.
• I am signed up to the Ory Security Patch Newsletter.

Describe the bug

It seems like the auth related fields are completely unused. Is that expected?

Reproducing the bug

sdk/clients/keto/rust/src/apis/configuration.rs

Line 19 in 96841c7

pub basic_auth: Option<BasicAuth>,

Relevant log output

No response

Relevant configuration

No response

Version

HEAD

On which operating system are you observing this issue?

No response

In which environment are you deploying?

No response

Additional Context

A workaround is to specify the auth tokens as default headers while initialing the reqwest client.

[aeneasr]

It appears that those are indeed not used. Keto does not have HTTP Authorization built in - if you deploy it yourself and introduce some type of HTTP Authorization it might be required to generate the client yourself and adjust it to your security mechanisms. Unfortunately the SDK can't cover all of the different ways authorization can be done :/

Or did I misread your issue?

[Dig-Doug]

The main thing I want to flag is that these options are confusing because they don't work.

Looking at the generated code, it seems like the client could use the authorization config values when building the request here via the reqwest option. Alternatively, removing those fields would eliminate the confusion too.

[aeneasr]

That makes sense - the problem here is the openapi-generator which is apparently introducing these structs even if they're not used. The repository is: https://github.com/OpenAPITools/openapi-generator

So unfortunately we can't manually remove these definitions as they will be overwritten immediately once the automation runs. If you want, you can open an issue upstream at https://github.com/OpenAPITools/openapi-generator or see if there's any options in there that would help improve the generated code here :)