Dimitrij Drus

FMPOV, the implementation should only care about the values it has stored and not about changes done outside of it. So, my vote goes to "update the eviction queues when...

@swithek, @davseby: Are there any chances to have this FR addressed in the near future?

If you don't mind, I would love to contribute the corresponding functionality (as I would like to have the corresponding feature in the upcoming version of my project). To be...

Thank you @martin31821 for your FR. I planned the corresponding functionality for the 0.13.0-alpha release. I personally don't see any dependency to #619. Actually, you could achieve your goal today...

BTW, I encourage you joining the community in [Discord](https://discord.gg/qQgg8xKuyb). That way you can directly participate in the ongoing discussions and influence the future of heimdall. I'll introduce this FR in...

@martin31821: Is there a reason, why you closed the FR? I personally think it is a pretty good enhancement of the available functionality

The idea with #619 was related to the actual discovery of the relevant endpoints. But you're right, the same information from the discovery endpoint can also be used to assert...

There is unfortunately no hook, which could be set to log a 431 error. And there are more like this. The responsible HTTP server implementation includes the following lines of...

There is a [corresponding FR](https://github.com/golang/go/issues/56028) to allow logging in such cases. As long as there is no solution for this, there is no way to resolve the corresponding issue with...

There is an [RFC draft](https://datatracker.ietf.org/doc/draft-ietf-oauth-transaction-tokens/) for so called transactional tokens which closes the first con written in the description as contextual information can be passed down to the new token.