Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Use cipherSpec property from MQ binding #75

Closed
dan-r opened this issue Nov 2, 2022 · 2 comments
Closed

Use cipherSpec property from MQ binding #75

dan-r opened this issue Nov 2, 2022 · 2 comments
Assignees
@dan-r
Labels
enhancement New feature or request

Comments

@dan-r
Copy link
Member

dan-r commented Nov 2, 2022

For completeness, it would be good to parse the cipherSpec property from the spec and map this to the Java cipher suite as per https://www.ibm.com/docs/en/ibm-mq/9.3?topic=jms-tls-cipherspecs-ciphersuites-in-mq-classes

I'll give this a go for MQ, @dalelane I'm not sure if this is applicable/relevant to Kafka?
@dan-r dan-r added the enhancement New feature or request label Nov 2, 2022
@dan-r dan-r self-assigned this Nov 2, 2022
@github-actions
Copy link

github-actions bot commented Nov 2, 2022

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

@dan-r dan-r mentioned this issue Nov 3, 2022
Merged
@dalelane
Copy link
Collaborator

dalelane commented Nov 3, 2022

I'll give this a go for MQ, @dalelane I'm not sure if this is applicable/relevant to Kafka?

nope - Kafka uses a different approach

@dan-r dan-r closed this as completed Feb 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dan-r dan-r

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dan-r @dalelane