-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Request]: Update the API documentation #21
Comments
Hi @SyedAanif , can you please raise this request with our support team by contacting [email protected]? They will be able to help answer your request or guide you to someone that can. Thank you, |
Two-way TLS authentication (or "client-certificate authentication") is documented here: https://docs.solace.com/API/API-Developer-Guide-Go/Go-API-Messaging-Service.htm#Client There are examples of it in this codebase in the test code. Please see pubsubplus-go-client/test/messaging_service_test.go, and search for either |
I have submitted a request for the documentation to be augmented with extra info about cert/key file format, and what to do in case the key is in the same file as the certificate, and what to do if there is no password for the private key. I have also raised Issue SolaceSamples/solace-samples-go#14 |
The request for samples is being handled in the SolaceSamples repository. |
Thanks for the reply, but we chose to use traditional JMS to connect to
Solace broker, because none of the pub-sub clients(in any languages) was
working inside AWS Lambda.
…On Fri, Dec 20, 2024 at 11:35 PM Ragnar ***@***.***> wrote:
The request for samples is being handled in the SolaceSamples repository.
—
Reply to this email directly, view it on GitHub
<#21 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AP5NPO2FVL5EACLG45U6MQL2GRL7LAVCNFSM6AAAAABMHVYGR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJXGQ4DCNZSGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Feature Description
Thanks for building this API, but as a request can you please update the docs with examples specifically catering to the mTLS needs.
Use Case
This request is required to have a clear understanding of the certificate based broker connection. Few pointers:
key-store-password
?./trust_store
folder with.pem
files inside and not mention any file name intrust-path
?Proposed Solution
No response
The text was updated successfully, but these errors were encountered: