OpenAPI 3 feature: Support parameter location "in: cookie"

[jannyHou]

Description

Original discussion see: #916 (comment)

Cookie support is not so straightforward. It's a recommended practice to encrypt cookie values using a server-configured secret. We will need a way how to tell @loopback/rest what is this secret, otherwise it won't be able to decode cookie values.

Current workaround:

Throw a helpful error here, explain that cookie parameters are not supported yet and point people to the GH issue tracking this feature.

OpenAPI official reference: https://swagger.io/docs/specification/describing-parameters/#cookie-parameters

[stale]

This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository. This issue will be closed within 30 days of being stale.

[stale]

This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.

[achrinza]

It's been a while since this issue was visited;

@bajtos - is there any reason we need lb4 to transparently handle encrypting the cookies? IMO this reduces flexibility and interoperability. This should be handled by the controller and be up to the developer to encrypt.

[stale]

This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository. This issue will be closed within 30 days of being stale.