DNN site uses LiveID as authentication mode. Authentication generated an error stating 'the http request has been forbidden for the client authentication scheme 'Anonymous'. DNN site & authentication has been up and running for the last four months.
How can this be resolved?

I'm getting the same error on one of our sites all of a sudden. Did you figure out what caused this problem?

Seems LiveID is broken now.

Did this just start happening without any updates or other changes to the site?

Which DNN version?

----------
I've seen other forum postings similar to this. It appears that the source of the problem is on the LiveID side of things. See: http://www.dnnsoftware.com/answers/...60209-site

No changes or updates to the site were done. LiveID stopped authenticating suddenly.
DNN version 7.2.2

Please look in the EventLog and see if there are any errors related to authentication.

There are no errors related to authentication in the event log.

This appears to be the latest.

http://www.dnnsoftware.com/forums/f...cope/posts

You can follow the link to the DNN Issue Tracker in Cathal Connolly's post. To summarize: the issue has been reported, but there's no timetable for a fix.

On the hopeful news side of the issue, the LiveId Authentication Provider is open source. So ... it's possible that someone will get interested in debugging the problem even if it is not a high priority item with the DNN team.

The issue is brought about by the authentication url currently being used by live id module (https://oauth.live.com). What works is pointing to http://login.live.com url instead. The challenge now is, how do I access the source code for the liveid module for version 7.2.2 so that those changes can be plugged in?

You can download the source for the LiveID authentication from https://dnnauthliveid.codeplex.com

I took a quick look at the source, and it appears that the login.live.com url is in the source. So ... where do you see the oauth.live.com URL being used?

Referred to the DNNAuthLiveID dll packaged with the DNN version Im using and noticed a method referencing the https://oauth.live.com url as the endpoint for both authorization and retrieving the token. The Source code you've referred is to does make a reference to login.live.com but on testing, generates the same authentication error.

Is there anything that gets added into web.config regarding the endpoint?

None in web.config. However, changed the url endpoint reference for authorization and the token to login.live.com from oath.login.live and the site is now up and running.

Cathy,

Could you document exactly what you change, and where? This might help others in the future.

In the absence of the source code for the liveID authentication module packaged with the DNN CMS, one will need to modify the dll file relating to the module by decompiling it, changing the endpoint urls, recompile the dll and plug it back in.

The source is available at https://dnnauthliveid.codeplex.com/SourceControl/latest

I took a look and find no reference to oauth.login.live.

The source code is marked as version 1.0.2 but the install module that you can download is 1.0.1. Someone was a little sloppy!

I just tried to send a message to the coordinators with a request to create a 1.0.2 install package. We'll see what happens

FYI, this issue is fixed and will be included in the 7.3.4 release of DNN.