Custom store implementation
See original GitHub issueDescribe the problem you’d like to have solved
A cookie implementation isn’t sufficient when the amount of claims starts to rise and the browser will emit a 431 Request Header Fields Too Large
.
For those who’ll need a different store strategy allowing for a custom store implementation will unblock without putting the work and maintenance on Auth0, as each user can bring their own store, a bit like express-session
.
Describe the ideal solution
Allow to pass an instance of a Store in the params to overwrite the CookieStore.
Alternatives and current work-arounds
No current workaround. Currently patching the library to allow this.
Additional information, if any
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:15 (6 by maintainers)
Top Results From Across the Web
How to implement a custom Store - DevExpress Support
It is not that difficult to create a custom Store, but one should take care of implementing allBasic Operations and make sure that...
Read more >Custom-Backing-Store - TIBCO Software
The BaseStoreProvider class acts as an entry point for the custom store implementation. Specify the fully qualified name of this class into the...
Read more >Implementing a Store - Unity - Manual
Implementing a Store. Your store must implement the IStore interface, the methods of which are detailed in following sections. using UnityEngine.Purchasing.
Read more >Implementing Custom Cache Store | Ignite Documentation
You can implement your own custom CacheStore and use it as an underlying data storage for the cache. The methods of IgniteCache that...
Read more >21.3 Creating a Custom Store Provider - Oracle Help Center
However, the implementation shows the path towards a robust, production-quality custom SPI that can plug into the DBFS, and expose existing relational data...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@johansundwall @PSoltes @ShawnFumo @jhaji2911 @matiascarranza @alechartung
I’ve released an experimental version of the SDK with support for custom session stores.
To install:
See this example for how to implement https://github.com/auth0/nextjs-auth0/blob/session-stores/EXAMPLES.md#use-a-custom-session-store
I’ve also set up an example app using the SDK with a redis session store (using upstash) here https://github.com/adamjmcgrath/nextjs-auth0-redis-session (The interesting file is /lib/auth0-config.ts)
Please try it out and add any feedback or issues in this thread 👇
Hi @jhaji2911 - thanks for your interest
Currently we’re not working on this feature, but it’s something we’re considering for a future iteration