You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am reaching out again regarding the OAuth 2.0 authentication error in the auth0 R package that occurs during page refresh , specifically the Error in httr::oauth2.0_access_token(api, app(redirect_uri), params$code). This issue has been previously commented on, but a definitive solution has not been found.
I am seeking any additional insights or alternative solutions. Is there a way to mitigate or circumvent this error, especially during the page refresh process?
The text was updated successfully, but these errors were encountered:
I'm having the same issue here. I built an application about a year ago and the JS script in the header actually did the trick. However, in this new app I'm building at the moment it just doesn't work. Refreshing the page sends me straight back to login again, even if I had logged in a seconds ago.
Any workarounds? @nionmaron, have you found a workaround yet?
Hi @nionmaron , any updates on this? have you been able to solve it? I'm still having this issue open for my app and given that other issues have come up with more priority I haven't tackled this one just yet, however, It's going to come up again soon I'm sure and I will have to have some options to try.
Just for the records, this time I have used bslib entirely for the app. I had built a previous app with auth0 with the bs4Dash package and that one's been running with no issues. The fix (javascript to clear url) worked like a charm.
I am reaching out again regarding the OAuth 2.0 authentication error in the auth0 R package that occurs during page refresh , specifically the Error in httr::oauth2.0_access_token(api, app(redirect_uri), params$code). This issue has been previously commented on, but a definitive solution has not been found.
I am seeking any additional insights or alternative solutions. Is there a way to mitigate or circumvent this error, especially during the page refresh process?
The text was updated successfully, but these errors were encountered: