microsoftgraph / microsoftgraph/msgraph-metadata
Missing OpenAPI authentication aka security scheme information
Nobody has claimed this yet.
- Dominant language
- XSLT
- Stars
- 166
- Forks
- 55
- Avg merge
- 16h 12m
- Merged PRs (30d)
- 14
Description
The OpenAPI yaml file is missing security scheme information, preventing us from generating fully working clients based on OpenAPI schema alone.
Given that certain SDKs are no longer maintained from Microsoft, would you be kind enough to add that so that we can use auto-generated clients?
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
The issue names the OpenAPI YAML file and the OpenAPI security-scheme specification. Start by locating how this schema is produced from the repository’s Microsoft Graph metadata, then compare its authentication requirements with the linked specification. Done means the YAML includes enough security-scheme information for clients to be generated from the schema alone.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api, authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100