Support for graph.microsoft.com
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.7k
- Forks
- 395
- PR merge metrics
- No merged PRs in 30d
Description
Yet another question (or maybe issue while running roadrecon) - sorry for being a bother! :)
Are there any plans for adding support for https://graph.microsoft.com based enumeration?
My use case is that I came in possession of access token scoped precisely for that client with User.Read User.ReadBasic.All scope and found that ROADtools are not able to help me pull data using this token.
Ultimately I guess I need to poke around manually?
(Invoke-RestMethod @{Uri="https://graph.microsoft.com";Headers=@{'Authorization'="Bearer $token"}; Method='GET'}).value
Regards,
Mariusz.
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
Start at the roadrecon enumeration entry point and inspect how requests are made for the existing Azure AD endpoints. Compare that flow with the supplied graph.microsoft.com URL and access-token scopes. Done means ROADtools can enumerate the requested data with that token, with relevant tests or documented verification added if the project has coverage for this path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100