Provide Cookie implementation of AuthorizationRequestRepository

We should consider providing a Cookie based implementation of AuthorizationRequestRepository.

[afrancoc2000]

Sure the reason is microservices applications, today the best way of handling this type of apps is making them stateless so any app can respond to any request.

The authorization can be easily saved and restored from a jwt cookie thats better than having a session because for sessions I need an extra component like a redis cache, that means more infrastructure, more points of failure and the posiblility of conflicts between sessions, problems that could be easily solved by replacing a couple lines of code.

Also that allows me to link an external frontend more easily just by passing the jwt cookie that is a standard in the industry.

I would love to help I was looking at the example of @naturalprogrammer in this links: link 1, link 2 but found out that storing the OAuth2AuthorizationRequest is not enough and I would prefer to do the implementation with a jwt cookie saving and restoring the security context, haven’t got till there yet.

[jgrandja]

This feature will not be implemented for the reasons mentioned in this comment. If an application requires this, it would be fairly trivial to implement a custom AuthorizationRequestRepository, please see gh-8621.