Add details for identifying consumers by their certificates.
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 17
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Section Number
"MDPWS Concurrent Consumer Connections" from PR #518
Priority
- Medium: Significant issue or clarification. Requires discussion, but should not lead to long debate.
Issue
Certificates provided by the consumer (may) provide a way to uniquely identify consumers for the purpose of limiting the number of concurrent connections, but we need to wait for details from the security working group.
Proposed Change
Specify how client credentials can be used to identify consumers when limiting concurrent consumer connections based on the findings from the security working group.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the “MDPWS Concurrent Consumer Connections” section from PR #518 and the security working group's certificate findings at wg-certificates. Determine how consumer-provided client credentials can identify consumers for concurrent-connection limits, then update the specification with that behavior and its limits.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100