Interest in upsteaming a ClientCredentialContext not directly tied to Azure?

Open
#115 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
ruby
Domain
authentication

Research direction

Start with lib/microsoft_kiota_authentication_oauth/contexts/client_credential_context.rb, especially the provider-specific code referenced in the issue. Compare the current context with the proposed generic implementation and check how other language packages structure it. Done means a ClientCredentialContext can be used with a provider that is not tied to Microsoft or Azure.

Written by the indexing model from the issue text.

Description

Hey! I wanted to ask if you would be interested in including a ClientCredentialContext that is not tied to Microsoft. The current version cannot be used with a generic provider. I've done the work to have a generic version of the context that I could upstream to this repo if that's something you consider in scope.

I ask because it seems some effort was made in the past to remove reference to the GraphSDK, but the contexts remain tied to Microsoft/Azure. At the same time, looking at implementations in other language, the package seems to be called something Azure related.
image

Dominant language
Ruby
Stars
5
Forks
8
Avg merge
11h 9m
Merged PRs (30d)
24

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/kiota-ruby

All issues in microsoft/kiota-ruby

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.