get_azure_token for non azure site using active directory
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- azure, r
- Domain
- api, authentication
Research direction
Start with the get_azure_token entry point and the package's authentication documentation, then reproduce the popup error against https://mdr-api.cefas.co.uk/index.html using the tenant, resource, app ID, and redirect URI described. Done means establishing whether non-Azure APIs using Active Directory are supported and documenting or correcting the relevant behavior.
Written by the indexing model from the issue text.
Description
I am trying to use the azure auth package to get an access token for an api that requires active directory authentication. I have all the necessary details including the tenant, resource, app id and redirect uri, but I am still getting errors about the resource not being found in the client on the popup, so I cannot login. I have checked in the azure portal and the resource id is definitely in the tenant. The site is https://mdr-api.cefas.co.uk/index.html (parts are accessible without login, but I need to access the parts that are restricted)
Does get_azure_token work if you are accessing an api that is not an azure site but does use active directory? I am starting to suspect the reason I am failing is because of that, but I have not found any other R packages for getting tokens using active directory login.
- Dominant language
- R
- Stars
- 48
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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/AzureAuth
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 20/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 3 days
-
Elevation orderOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
inbo/erl-butterflies-2025#19 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Component: R good-first-issue Type: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
The-Strategy-Unit/nhp_output_reports#116 · 1 comment ·