Collin Sauve

Hi Andrey. Thanks for the tip about the ignoring comment tag - I will use that as a work-around until I can find a way to simplify

I got this as well because response headers are not parsed properly. eg. I have something like this under an operation (several properties ommitted): ``` "responses": { "200": { "headers":...

So that is a bug, but I'd also like to bring up a feature request at the same time if possible: Allow dynamic token expirations. We've been considering implementing client-specific...

This may be a problem with other modules as well. We see some cases where we set `CookieAuthenticationOptions.ExpireTimeSpan` to 60 days but we see a 90 day expiry on the...

### Issue > could you expand your description of the issue? This concisely captures the issue: > OAuthAuthorizationServerOptions.AccessTokenExpireTimeSpan is used to set the expiry for the .AspNet.ApplicationCookie instead of CookieAuthenticationOptions.ExpireTimeSpan....

I still don't have a work-around for `UseTwoFactorSignInCookie`'s expiry replacing `UseCookieAuthentication`'s expiry on every request on the authorization server, but that's not as much of a problem for us since...

Thanks for that investigation @nickfloyd - makes sense now why we were having this issue. My 2 cents, though I'm just one of many users: We can probably work-around the...

:wave: Hello! Just a bump on this issue. I've experienced the same problem numerous times using Mocha. We're currently required to explicitly set the `.returns` on an expectation, and this...

I've put together an example that is much closer to where I have (most recently) encountered this issue: https://github.com/collinsauve/mocha-issue-493-example You can run `./example.rb` to see the system-under-test operating properly, and...

If you'd like I can also modify the system-under-test to be _misbehaving_ and yet the test still passes due to this bug. I'm thinking by now this point has been...