Hi everyone,

We have been working on the Authorization providers to correct some of the existing issues and to support some other specific providers

On the "standard" Authorization providers, we find out that LinkedIN uses a different access_token than the OAuth2.0 standard (it uses "oauth2_access_token" instead of the standard "access_token")

Also, some other Authorization Providers (a proprietary system we are working with) needs Authentication headers to be able to make the authorization.

We will like to suggest couple of changes in the OAuthClientBase for the 7.4.2 version, so DNN will work seamless with more Authentication providers, for that matter we raise two issues on the DNN tracker platform

https://dnntracker.atlassian.net/browse/DNN-7116 

https://dnntracker.atlassian.net/browse/DNN-7058

we would like to ask to be this development included in the next release, as we provide basically the full code to be added, this shouldn't be very time-consuming

by the way, when is planned the 7.4.2 coming into release ?

DNN 7.4.2 is just a bug Fixing release and should be available within a couple of weeks (according to http://www.dnnsoftware.com/community/..., release date would be today, but AFAIK it has been pushed back a Little, to include more fixes)

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

Hi everyone, i'm Carlos Miranda, part of the development group with Pedro Grande.

I did the next pull request:
https://github.com/carlinesrallysport...

There, we made a little change at oauthclientbase.cs as it's explained in the description of the commit.
__doPostBack('dnn$ctr1565$Forum_Container$DNNForum$cmdSubmit','')
Anyway, my workmate Pedro, says it's kind of confusing because many lines were added to the code (around 1700)

That is due to the addition of 2 whole folders:
DotNetNuke.Authentication.LinkedIn and DotNetNuke.Authentication.Fiware

Anyway, if you are not interested on their addition there, it would be great to have the oauthclientbase.cs modified.

This will allow people to add their own auth. providers in the future with an extra couple of features in case they are needed.

The example is our Fiware provider and LinkedIn needing a custom access_token path name.

Thanks in advance.