The constructor of the service.
This method executes a count query using the {@link model}
argument.
Caution: Count queries require a considerable amount of RAM
to execute. It is preferred to use pro-active statistics with
collections that contain one document with a counter.
The number of matching challenges.
This method updates exactly one document in a collection
and uses an upsert operation if it doesn't exist yet.
The query configuration with sort, order, pageNumber, pageSize.
The fields or data that has to be updated (will be added to $set: {}).
The operations that must be run additionally (e.g. $inc: {}) (optional).
The updated authChallenges document.
Method to query the existence of a document in the
authChallenges collection.
This executes a lean mongoose query such that the
properties of the returned document are reduced to
only the "_id" field.
The query configuration with sort, order, pageNumber, pageSize.
Whether a document exists which validates the passed query.
Method to query challenges based on query and returns as paginated result.
Find one AuthChallengeDocument instance in the database and use
a query based on the Queryable class.
The query configuration with sort, order, pageNumber, pageSize.
The resulting authChallenges document.
Method to update a batch of challenges.
This method generates a random authentication challenge.
The size of the generated authentication challenges can be changed
in the configuration file config/security.ts.
Note that by modifying the default challenge size, you may
affect the operations processor and thereby the data that is
returned by the backend.
(Optional) The size of the generated authentication challenge, defaults to 8.
An authentication challenge that can be attached on-chain.
Generated using TypeDoc
The main service to handle documents in the
authChallengescollection.v0.3.0