Thanks for the link Brock. It says identityServer 3 won’t have the support :( Can you recommend a way it can be done outside identityServer3 then? I tried setting in web.config file but it didn’t work for cookies generated by identity server? Any guidance will be helpful.
]]>]]>IdentityServer3 and upcoming SameSite Cookie changes in Browsers
All the built-in APIs are done in Startup, so it’s static config. So all those steps I described would require a restart. As for something automatic, we will be releasing at the end of the month (Aug, 2019) a commercial component that provides automatic key management. See: https://www.identityserver.com/products for more info.
]]>1>As per above explanation do we have to create 2-3 keys in advance and put it in AddValidation keys call
.AddValidationKey(“CN=lastKeyName”).AddValidationKey(“CN=nextKeyName”) for key roatation or do we have to insert it at runtime?
2>In above blog you mentioned that “Then you can switch over and promote key2 to your active signing credential.” How this will happen as
AddSigningCredential and AddValidation Keys method gets called in ConfigureServices method which get executed at startup time only.
3>I got confused here as AddSigningCredential and AddValidation Keys method get called only one time. How this things will work automatically means after certain interval like 90 days?
Is there any option?
4>Does Identity server support automatic key rollover?
thanks. i think i finally fixed them all!
]]>yea, that’s because their windows authN isn’t quite following the same model as the rest of the authentication services and handlers in ASP.NET Core
]]>Very interesting for me because I am working on two different applications: one is AngularJS with Spring Boot (access token and refresh token) and the other is ClojureScript with Amazon Cognito (implicit flow, no refresh token).
Thanks for taking the time to write such a clear explanation.
]]> “;
await ctx.Response.WriteAsync(html);
return;
}
await next();
});