OpenAPITools / OpenAPITools/openapi-generator

[BUG] [Rust Server] Rust Server generated code HTTPS/SSL not work.

Open
#6,040 1 comment 0 reactions 1 assignee View on GitHub

@richardwhiuk is already working on this.

Since Aug 9, 2024.

Issue: Bug
Dominant language
Java
Stars
26.8k
Forks
7.7k
PR merge metrics
PR metrics pending

Description

Bug Report Checklist
  • Have you provided a full/minimal spec to reproduce the issue?
  • Have you validated the input using an OpenAPI validator (example)?
  • What's the version of OpenAPI Generator used?
  • Have you search for related issues/PRs?
  • What's the actual output vs expected output?
  • [Optional] Bounty to sponsor the fix (example)
Description

On the example project openapi-v3,

  1. One Shell run "cargo run --example server -- --https "
  2. Another Shell run "cargo run --example client -- --https UuidGet"
    Fail with the following error:
    Err(ApiError("No response received: The OpenSSL library reported an error: error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:s3_clnt.c:1264:")) (X-Span-ID: XSpanIdString("4f9b1d61-d15e-453c-a7f3-7e4679213549"))
openapi-generator version

5.0.x and master both fail

OpenAPI declaration file content or url

example openapi-v3.yaml

Command line used for generation

One Shell run "cargo run --example server -- --https "
Another Shell run "cargo run --example client -- --https UuidGet"

Steps to reproduce

On the example project openapi-v3,
1.One Shell run "cargo run --example server -- --https "
2. Another Shell run "cargo run --example client -- --https UuidGet"
Fail with the following error:
Err(ApiError("No response received: The OpenSSL library reported an error: error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:s3_clnt.c:1264:")) (X-Span-ID: XSpanIdString("4f9b1d61-d15e-453c-a7f3-7e4679213549"))

Related issues/PRs
Suggest a fix

After replace the ca.pem/server-chain.pem/server-key.pem to new self signed CA, it works.
Can someone update the pem in the code.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.