Licensing details implementation missing
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- networking
Research direction
Start by reviewing the custom session provider implementation and the RequestLicensingCapabilities or RequestClientLicense entry points mentioned in the issue. Investigate the SetErrorInfo values 12 and 15 and verify the required configuration and connection steps; done means the licensing exchange completes without closing the connection.
Written by the indexing model from the issue text.
Description
What are the configuration and steps involved in enabling the custom session provider ?
I have implemented the custom session provider based on the above implementation but I am always getting error in the step of RequestLicensingCapabilities Or RequestClientLicense and after that the SetErrorinfo 12 or 15 is received connection is closed.
- Dominant language
- No language data
- Stars
- 8
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from Azure/Remote-Desktop-Services-Protocol-Sample
-
Difficulty 4/5 3-5 days Newbie friendliness 15/100
Azure/Remote-Desktop-Services-Protocol-Sample#3 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
Azure/Remote-Desktop-Services-Protocol-Sample#1 · 1 comment ·
All issues in Azure/Remote-Desktop-Services-Protocol-Sample
Similar issues
-
bug status/needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
prowler-cloud/prowler#12885 · 1 comment ·
Maintainers usually reply within 1 day
-
area/proxy kind/bug priority/backlog triage/accepted
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
lexfrei/cloudflare-tunnel-gateway-controller#840 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
callstackincubator/appduct#129 ·
Maintainers usually reply within 1 day
-
area/auth area/install-update comp/cli P2 sweeper:risk-compatibility type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#124654 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day