Last post Dec 10, 2019 06:08 AM by Yang Shen
Dec 09, 2019 09:37 AM|chandruasp|LINK
An ASP.NET web-forms based application, follows form authentication, maintains user session in DB for stateless model across the servers(F5 DR). Planning to replace the session management with JWT token based to avoid db hits and to meet future API development
but the UI (aspx) will be remain as it is.
Question: When it comes to ASP.NET webform which would execute all the requests at server side,posting a token between browser (client) and IIS (server) could be server-side processing (managed in ASP.NET context but not like a SPA), I assume it may behave
like an in-proc session, that means it would NOT meet stateless model requirement across the servers. Any suggestions? Does token-model not suit for asp.net web app?
Dec 10, 2019 06:08 AM|Yang Shen|LINK
I assume it may behave like an in-proc session, that means it would NOT meet stateless model requirement across the servers. Any suggestions? Does token-model not suit for asp.net web app?
Can't see anything stop you from using JWT token in asp.net web app.
As far as i know, this is totally based on how you will configure your authentication and authorization on your server.
Maybe you should check the IdentidyServer and https://stackoverflow.com/a/40284152/12473216 for more related information.