CODEWITHSUNDEEP
asp.net-corejwtidentityserver4
ruipascoal
ruipascoal

Reputation: 47

Identity Server 4 Authentication Too Slow

I just tried out the samples for identity server 4 in here for .Net Core

https://github.com/IdentityServer/IdentityServer4.Samples

On the QuickStarts I tested the ImplicitFlowAuthentication.

The thing is, it takes very long just to reach the login page on the identity server app sometimes.

I'm testing this in the intranet of our company and I was looking for a solution to centralize authentication for all of our applications.

Out of the box I really like how flexible identity server 4 is but i don't understand why it takes more than 20 seconds to reach the identity server 4. Today It took less than a second to access it but yesterday it took almost a minute to login and logout using the sample solution.

On the other hand I already have working solution with Jwt authentication using a Web API but I have to deal with many customizations and handle how i store the token on the clients.

So there's 2 options for me.

Option 1: Go with identity server 4 and try to optimize it as much as possible.

Option 2: Stay with Jwt Web Api Authentication and try to secure it as much as possible.

If anyone can help me choose and why for my situation please do so. My aim is to allow users on our company intranet to access every single application without having to login every time and avoid duplicating data for each app. Also the users are validated against a LDAP and i saw IdentityServer4 also has an extension.

If there are more options please advice.

EDIT

For testing IS4, I ran it locally, as the only user and in debug mode. I'm actually trying to find out if IS4 has some configuration that might slow down performance

Upvotes: 0

Views: 2805

Answers (1)

smbanaei
smbanaei

Reputation: 1177

Just Install The Redis Server and Start it right before starting the main project https://github.com/abpframework/abp/issues/2764

Upvotes: 1

Related Questions