-
Notifications
You must be signed in to change notification settings - Fork 745
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OAuthV3 Support for authentication providers #2257
Comments
InnerMessage:Object reference not set to an instance of an object. InnerStackTrace: at DotNetNuke.Services.Authentication.OAuth.OAuthClientBase.ExecuteWebRequest(HttpMethod method, Uri uri, String parameters, String authHeader) at DotNetNuke.Services.Authentication.OAuth.OAuthClientBase.ExchangeCodeForToken() at DotNetNuke.Services.Authentication.OAuth.OAuthClientBase.AuthorizeV2() at DotNetNuke.Services.Authentication.OAuth.OAuthLoginBase.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) |
Not sure if this PR is related... Maybe something here: ` protected override void OnLoad(EventArgs e)
|
@valadas there is no support for OAuthV3 in the DNN Authentication Providers. While I haven't looked into the OAuth V3 specification we should add new V3 APIs to the provider to make it easier to integrate with. Any change that has been made to current providers is most likely a work-around to support the new specification. We should investigate and make some decisions on how we want to proceed. If OAuth 3.0 is starting to be adopted throughout the industry we should try and get this done by 10.0 if not sooner EditAfter doing some quick research it doesn't appear that there is an OAuth 3.0 spec. Is there any docs anyone can provide on this? |
Cool, I gonna make this an enhancement then |
This killed my web community when I made this report... so many users still cannot log I am sure gave up by now. I had to remove all authentication providers and I am pretty scared to add them again and embarrassed me trying to launch a community site that was taking off. I do look forward to the enhancement. thank you! |
OAuth 3 is in progress unless someone has other news, I am closing this issue for now, if news change, feel free to comment and I will re-open |
Description
OAuthV3 is now the latests version of OAuth supported by Authentication Providers such as Facebook, Twitters, ect.
DNN Platform/Library/Services/Authentication/OAuth/OAuthClientBase.cs
Supports up to OAuthV2 line 213
Current providers for Facebook, Twitter... fail to work as needed to allow login/registration.
Affected browser
The text was updated successfully, but these errors were encountered: