Debugging when Authenticating from Shiny
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- azure, r
- Domain
- authentication
Research direction
Compare the separate global.R, server.R, and UI.R setup with the “Authenticating from Shiny” vignette, including the clean_url_js snippet and the tenant, app, resource, and redirect values. Start by examining the reported error image and Shiny server logs; done would mean identifying a reproducible cause and documenting a concrete debugging or configuration fix.
Written by the indexing model from the issue text.
Description
I am building a Shiny app for my organization and plan to use AzureAuth to authenticate users. This is my first time using AzureAuth, and I have found little help with it elsewhere on the internet.
My app has separate global.R, server.R, and UI.R components. I tried to follow the "Authenticating from Shiny" vignette, however I am receiving an uninformative error and nothing more is produced in the error logs of the Shiny server.
I added components to the server and ui functions as outlined in the vignette and defined tenant, app, resource, and redirect in my global.R file. I also included the following at the top (from Authenticating from Shiny Vingette):
clean_url_js <- sprintf(
"
$(document).ready(function(event) {
const nextURL = '%s';
const nextTitle = 'My new page title';
const nextState = { additional information: 'Updated the URL with JS' };
// This will create a new entry in the browser's history, without reloading
window.history.pushState(nextState, nextTitle, nextURL);
});
", redirect
)
Do you have any tips for debugging?
Thank you in advance.
- Dominant language
- R
- Stars
- 48
- Forks
- 23
- Avg merge
- 4h 2m
- Merged PRs (30d)
- 3
Contributor 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 35/100
-
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
Similar issues
-
documentation pkg infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
epiverse-trace/epiparameter#511 ·
-
function:write_dwc
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
r-lib/pkgdepends#485 · 3 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
beginners blocker
Difficulty 2/5 1-3 hours Newbie friendliness 78/100