Steve Van Treeck

My feedback

  1. 163 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Steve Van Treeck commented  · 

    Is there a working example of this in action? I tried to implement this using 4.0.23, and received a bunch of 401s using IIS Express after following the registration code that was included in the release notes. I was trying to go to http://<websiteUrl>/auth/windowsauth, and then I could see that I was authorized at http://<websiteUrl>/auth; however, when I attempted to access one of my services that was tagged with [Authenticate], I'd get a popup in my browser asking for username/pass (and my windows credentials would not work here). Any ideas on what might be missing or going on?

    This is the code I was using to enable the feature:
    Plugins.Add(new AuthFeature(
    () => new AuthUserSession(),
    new IAuthProvider[] {
    new AspNetWindowsAuthProvider(this) { AllowAllWindowsAuthUsers = true },
    }
    ));

Feedback and Knowledge Base