This appears to be a bug that we've been able to duplicate in multiple environments, and it's a bug that specifically impacts that ability to use Windows Live Writer to connect various modules via Metapost. The creators of Metapost have been thoroughly engaged in tracking down the root cause of this to the AD Authentication Provider. Here is the setup... DNN 4.8.4, AD Provider 1.0.5, latest build of metapost. DNN portal is used as an intranet, so auto-login is being used and is primarily working correctly (aside from the bug, which I'll get to). Using auto-login, all AD groups are properly syncronized, and users with "edit" permissions can go in and edit any/all pages/modules that they're authorized for. The "bug" shows up when users try to connect Windows Live Writer (WLW) to some of these modules via Metapost (from IT Crossing). There's the scenario:
1. Log into DNN as Admin and DELETE the test user (so that he is deleted from the DNN database).
2. Test User opens their browser, and our DNN is set up to AUTO login using AD credentials. In other words, the test user never types in his/her credentials, even when accessing the portal for the first time. This process adds the user to the DNN database and automatically syncs the test users role membership against their AD memberships.
3. Test User can now access/edit all parts of DNN as expected, but can NOT connect to ANY module via Live Writer. It will always give a Server error 0 (cannot authenticate user).
4. Test user now hits the “Logout” button on the DNN portal, which takes them back to the DNN login screen. They click “Windows Login”, then enter their username as DOMAIN\testuser, along w/ their password.
5. Live Writer is now able to connect to all modules.
At this point, it seems logical that SOMETHING happens differently when a user is auto logged in versus manually logging in. However, we’ve gone into SQL server and grabbed a snapshot of the database when a NEW user auto-logs in for the first time (i.e. Live Writer won’t connect). We then “fix” this user’s profile by logging out and manually logging in. After doing this, we grabbed another snapshot of the SQL database and did a file compare. Aside from the “last login” date, the two snapshots are identical.
The FINAL scenario that we’ve tested is as follows:
1. We logged into DNN as Admin and deleted the test user.
2. Still logged in as Admin, we use the “Add User” function of DNN to add the user, as well as manually place that user in the proper DNN groups. (Essentially, this process manually creates a profile that is normally created via Active Directory).
3. Live Writer CAN connect at this point.
So in a nutshell, the two scenarios that allow WLW to connect are if the user manually logs into the portal, or if an Admin manually creates their account. WLW will fail to connect if their DNN account is created through Auto login. The creator of Metapost can create this same behavior on their environment as well, and has narrowed it down to the AD Authentication Module... just uncertain WHY the auto-login is different from the manual login.
I hope someone out there has some suggestions. I've tried to give enough detail to describe the problem, but hope I haven't been too detailed. If this problem should be submitted via a more "formal" process, please let me know and I'll do so. Thank you.