c# - ASP.NET Identity 2.0, self hosted OWIN, NTLM and application roles persistance -


i'm trying hands on asp.net identity 2.0 , there aspects i'm not finding answers to:

here's setup:

  • webapi 2 self hosted nowin (i need full signalr server's not running 2012 r2)
  • a custom ntlm implementation
  • asp.net identity 2.0 own identitydbcontext<>

what's working far:

  • the webapi
  • the custom ntlm authenticationhandler<> (i can access user.identity in apicontrollers
  • adding claims

my actual question

the claims add identity aren't persisted database don't survive application restarts, nor correctly linked actual windows identity 2 "sessions" of same user can have different claims.

what expected asp.net identity 2.0 creates sort of "local (application) user" once i'm authenticated (from successful ntlm handshake) application claims stored.

i'm pretty sure there's plumbing code missing somewhere, can't find where.

after amount of fiddling around solutions following:

  1. create passive authentication middleware ntlm authentication when asked to
  2. create custom action on accounts controller transform ntlm/windows identity application identity , sign in one.

Comments

Popular posts from this blog

java - Plugin org.apache.maven.plugins:maven-install-plugin:2.4 or one of its dependencies could not be resolved -

Round ImageView Android -

How can I utilize Yahoo Weather API in android -