identityserver4 - Hosting IS4 and AspNet Core Identity's user management functions in the same web application? -
i've read in is4 issues recently, e.g. here, hosting is4 , client in same web application not tested or recommended scenario. apply when integrating aspnet identity's logged-in workflows is4?
for example, it's understood aspnet identity's account feature's controller, models , views aspnet identity required identityserver4.aspnetidentity code can initiate relevant ui, okay leave manage controller in same web application provide self-service feature, or should functionality moved separate web application?
for is3 created separate web app contained user profile functions (manage controller), plus admin is3 configuration , user management. app configured client , is3 web app had no client config or logged-in workflows. preferred architecture re-using manage controller functionality?
ideally, i'd keep aspnet identity functionality is4 in 1 web app , have separate web app admin of config , users. want i'm not opening security vulnerability doing so.
Comments
Post a Comment