Identityserver4: Login from RP spends much time at connect/authorize endpoint (submit this form)

Created on 11 May 2016  路  7Comments  路  Source: IdentityServer/IdentityServer4

If identityserver (read web app) is activated from idle state the first login request takes unreasonable amount of time at the connect/authorize endpoint.

Flow:

  • RP redirects to Identityserver
  • If you're not logged in, sign in (doesn't matter)
  • Get redirected to connect/authorize endpoint, you can see (submit this form title in browser tab)
  • After quite some time you get redirected back to the RP

Repeating the steps again after this is super fast.

question

Most helpful comment

so what? ;)

Tell MS to boot up faster or keep the app running..that has always been an issue in .net

All 7 comments

so what? ;)

Tell MS to boot up faster or keep the app running..that has always been an issue in .net

A bit quick to judge don't you think? The latency is definitely in the identityserver middlewear. You're referring to the long load time from cold start with the non core version but I'm running on core. Also as I described the app is already warm since I've loaded the login page and posted my credentials, it's not the first load, just the first redirect to connect/authorize.

Just now I had one tab that was waiting on connect/authorize with the title "submit this form", while that tab was busy I opened up a new tab and browsed to the identityserver where I was already logged in (due to the RP redirect->login), and I could perform several operations like updating my email adress and whatever until the first tab finally finished and redirected to RP.

Definitely not a MS problem.

You said "idle" state. Why would "core" change that?

Anyways - feel free to do some more investigation and profiling to find out where the time gets spend. Looking forward to the findings!

what did you profiling bring up?

I haven't had the time to come around and do it, been kind of swamped with work, also seems like it's faster, I've scaled the webapp to the premium tier. Closing this.

We have same problem.
After cold start client project, when first request to identity is not quick - client freeze and only press F5 helps us.

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Was this page helpful?
0 / 5 - 0 ratings