Dev NOTES:
- Token Reference ID must be unique when set. Using semantic ID with atomic guards due to Prune problems and reference documents update: not atomic guards usage due to not being removed automatically by delete by query, optimistic concurrency, relying on library, loading before store, worst case scenario a new document with same reference if will overwrite the existing one
- Delete by query does not support map-reduce indexes. We need to output the authorizations index to a collection in order to run the query to prune tokens. see ravendb/ravendb#14496
Implementation of the OpenIdDict stores for the RavenDB database.
Unique values are stored as separate documents with atomic guards. In cases where unique values are handled the transaction mode will be set to cluster-wide as that is the requirement for atomic guards.
By default, set to null which implies HiLo identifier generation.
Refer to official RavenDB document about identifier generation strategies.
When token reference id is not null, that reference id becomes part of a semantic id.
Nikola Josipović
This project is licensed under the MIT License. See License.md for more information.
addr1q87dhpq4wkm5gucymxkwcatu2et5enl9z8dal4c0fj98fxznraxyxtx5lf597gunnxn3tewwr6x2y588ttdkdlgaz79spp3avz
0xae0B28c1fCb707e1908706aAd65156b61aC6Ff0A