Oversight/incorrect documentation? Config file suggests a custom key provider can be used but there is nothing in the docs nor does the code indicate this is possible.

[stevenmaguire]

Is this an oversight? Is it possible to build your own key provider or not?

[freekmurze]

@riasvdv could you take a look at this one?

[riasvdv]

@stevenmaguire This was indeed missing. I've now added it to the package: https://github.com/spatie/laravel-ciphersweet#implementing-a-custom-key-provider

[stevenmaguire]

Thank you for the confirmation and prompt response!

[stevenmaguire]

As a follow-up - and I am happy to open a new discussion if that is preferred - do you think similar support for custom backends is reasonable?

I'm specifically thinking about the MultiTenant support from the underlying package. It requires a KeyProvider and a Backend that implement specific MultiTenant interfaces. The current stock options do not appear to satisfy that. If I can provide a custom KeyProvider and custom Backend it seems that functionality will be accessible.

[riasvdv]

We don’t need this functionality ourselves, but I’d gladly merge a PR with tests that adds this