Invalid SSL certificates. What is Kiota trying to access? #7084
Unanswered
rudfoss-rr
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm evaluating whether to use Kiota for client generation from our OpenAPI files at the moment and I'm struggling with understanding exactly what is happening behind the scenes. I'm using the containerized CLI.
We are using a self-signed certificate in our environment and from the docs I can see that the
generatecommand has a parameter for ignoring SSL validation. This seems to work, but I don't fully understand why it needs any network access at all. This is the full command I'm running which generates clients just fine as long as the--disable-ssl-validationparameter is set:Since the openapi spec file is mounted directly why is there any need for network access? And is there a way for me to cache whatever it needs so that it doesn't have to request anything?
I'm also getting the same SSL error when using the
infocommand and it doesn't seem to have any way to disable ssl validation at all. Adding--disable-ssl-validationsimply returnsUnrecognized command or argument '--disable-ssl-validation'..What I was hoping was to be able to run all the necessary commands locally without any need for direct internet access. Either just downloading a Kiota container image with everything I need or caching whatever it needs and mounting it as a volume or something similar.
I'm also wondering how I'm supposed to use
infocorrectly when it keeps throwing SSL exceptions.Beta Was this translation helpful? Give feedback.
All reactions