x-csrf-token header, otherwise you'll receive a `403 - ForbiddenError: invalid csrf token`. If your cookie is not being included in your requests be sure to check your withCredentials and CORS configuration.
+If you plan on using express-session then please ensure your cookie-parser middleware is registered after express-session, as express session parses it's own cookies and may cionflict.
csrf-csrf itself will not support promises or async, however there is a way around this. If your csrf token is stored externally and needs to be retrieved asynchronously, you can register an asynchronous middleware first, which exposes the token.
+ +```js +(req, res, next) => { + getCsrfTokenAsync(req) + .then((token) => { + req.asyncCsrfToken = token; + next(); + }) + .catch((error) => next(error)); +}; +``` + +And in this example, your getTokenFromRequest would look like this:
getSecret, the rest have sensible defaults (shown below).
@@ -175,82 +201,164 @@ const doubleCsrfUtilities = doubleCsrf({
});
```
-If you plan on using express-session then please ensure your cookie-parser middleware is registered after express-session, as express session parses it's own cookies and may cionflict.
Required
+ +This should return a secret key to be used for hashing the CSRF tokens.
+ +By default if a csrf-csrf cookie already exists on an incoming request, generateToken will not overwrite it, it will simply return the existing token. If you wish to force a token generation, you can use the third parameter:
+
+ Optional
+ Default: "__Host-psifi.x-csrf-token"
+
Optional: The name of the httpOnly cookie that will be used to track CSRF protection. If you change this it is recommend that you continue to use the __Host- or __Secure- security prefix.
Change for development
+ +The security prefix requires the secure flag to be true and requires requests to be received via HTTPS, unless you have your local instance running via HTTPS, you will need to change this value in your development environment.
+ +
+ Optional
+ Default:
+
Instead of importing and using generateToken, you can also use req.csrfToken any time after the doubleCsrfProtection middleware has executed on your incoming request.
+The options provided to the cookie, see cookie attributes. The remaining options are all undefined by default and consist of:
+```ts + maxAge?: number | undefined; + signed?: boolean | undefined; + expires?: Date | undefined; + domain?: string | undefined; + encode?: (val: string) => string ``` -req.csrfToken(); // same as generateToken(res, req) and generateToken(res, req, false); -req.csrfToken(true); // same as generateToken(res, req, true); + +Change for development
+ +For development you will need to set secure to false unless you're running HTTPS locally. Ensure secure is true in your live environment by using environment variables.
The generateToken function serves the purpose of establishing a CSRF (Cross-Site Request Forgery) protection mechanism by generating a token and an associated cookie. This function also provides the option to utilize a third parameter called overwrite. By default, this parameter is set to false.
It returns a CSRF token and attaches a cookie to the response object. The cookie content is `${token}|${tokenHash}`.
You should only transmit your token to the frontend as part of a response payload, do not include the token in response headers or in a cookie, and do not transmit the token hash by any other means.
-When overwrite is set to false, the function behaves in a way that preserves the existing CSRF cookie and its corresponding token and hash. In other words, if a valid CSRF cookie is already present in the incoming request, the function will reuse this cookie along with its associated token.
On the other hand, if overwrite is set to true, the function will generate a new token and cookie each time it is invoked. This behavior can potentially lead to certain complications, particularly when multiple tabs are being used to interact with your web application. In such scenarios, the creation of new cookies with every call to the function can disrupt the proper functioning of your web app across different tabs, as the changes might not be synchronized effectively (you would need to write your own synchronization logic).
+ Optional
+ Default:
+
This function should return the token sent by the frontend, the doubleCsrfProtection middleware will validate the value returned by this function against the value in the cookie.
+ +
-This should return a secret key for hashing, using a hard coded string return works:
+Optional
+Default: ["GET", "HEAD", "OPTIONS"]
An array of request types that the doubleCsrfProtection middleware will ignore, requests made matching these request methods will not be protected. It is recommended you leave this as the default.
+ +
-However it is highly recommend you implement some rotating secret key so that tokens become invalidated after a certain period of time. For example, you could use sessions, or some server side state attached to the request (via middleware). You could then have some external means of updating and rotating what your getSecret returns and you could then use that:
+ Optional
+ Default: 64
The size in bytes of the tokens that will be generated, if you plan on re-generating tokens consider dropping this to 32.
+ +Below is the documentation for what doubleCsrf returns.
+ +The middleware used to actually protect your routes, see the getting started examples above, or the examples included in the repository.
-csrf-csrf itself will not support promises or async, however there is a way around this. If your csrf token is stored externally and needs to be retrieved asynchronously, you can register an asynchronous middleware first, which exposes the token.
+And in this example, your getTokenFromRequest would look like this:
By default if a csrf-csrf cookie already exists on an incoming request, generateToken will not overwrite it, it will simply return the existing token. If you wish to force a token generation, you can use the third parameter:
-```js -(req) => req.asyncCsrfToken; +```ts +generateToken(res, req, true); // This will force a new token to be generated, and a new cookie to be set, even if one already exists ``` -Instead of importing and using generateToken, you can also use req.csrfToken any time after the doubleCsrfProtection middleware has executed on your incoming request.
+ +```ts +req.csrfToken(); // same as generateToken(res, req) and generateToken(res, req, false); +req.csrfToken(true); // same as generateToken(res, req, true); +``` + +The generateToken function serves the purpose of establishing a CSRF (Cross-Site Request Forgery) protection mechanism by generating a token and an associated cookie. This function also provides the option to utilize a third parameter called overwrite. By default, this parameter is set to false.
It returns a CSRF token and attaches a cookie to the response object. The cookie content is `${token}|${tokenHash}`.
You should only transmit your token to the frontend as part of a response payload, do not include the token in response headers or in a cookie, and do not transmit the token hash by any other means.
+When overwrite is set to false, the function behaves in a way that preserves the existing CSRF cookie and its corresponding token and hash. In other words, if a valid CSRF cookie is already present in the incoming request, the function will reuse this cookie along with its associated token.
On the other hand, if overwrite is set to true, the function will generate a new token and cookie each time it is invoked. This behavior can potentially lead to certain complications, particularly when multiple tabs are being used to interact with your web application. In such scenarios, the creation of new cookies with every call to the function can disrupt the proper functioning of your web app across different tabs, as the changes might not be synchronized effectively (you would need to write your own synchronization logic).
This is the error instance that gets passed as an error to the next call, by default this will be handled by the default error handler.
This function is used by the doubleCsrfProtection middleware to determine whether an incoming request has a valid CSRF token. You can use this to make your own custom middleware (not recommended).
+ +