Re: [keycloak-user] Token generation: possibilities to improve performance

Regarding this, I wonder if we should add support for ECDSA based signatures as an alternative to RSA? Just went through some interesting blog [1] , which mentions that 256-bits ECDSA has around 9.5 times better performance of signature generation than 2048-bits RSA. The time of signature verification seems to be slightly worse for ECDSA (see second comment), however there is also increased security (256-ECDSA is equivalient of 3248 RSA according to blog). Maybe it's something we can look at? Also the optional flag to skip IDToken generation will be good too IMO. AFAIK the point of IDToken is the compliance with OIDC specification. However in case of Keycloak accessToken usually contains all the info like IDToken (+ some more) and it's the accessToken, which is used in REST endpoints. So with regards to that, most of the Keycloak-secured applications can live just with access+refresh token and don't need ID Token at all. So if just 2 tokens needs to be signed instead of 3, we have performance gain "for free" (no decrease of security, just one less useless token). [1] https://blog.cloudflare.com/ecdsa-the-digital-signature-algorithm-of-a-be... Marek On 24/05/16 15:43, Bill Burke wrote: