Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

GDPR - change consent

NodeBB Development

Jürgen last edited by
I searched quite a while for GDPR consent and did (not suprisingly) found this thread:

Re: Is NodeBB compliant with the GDPR (the newest legislative spam by the EU)?

As far as I understood most of the discussion is made there. Furthermore I understood that the GDPR plugin was made for migrating old forums to the new consent mostly required by EU regulations in May 2018. So my problem in 2021 is:

I would like to ask all our users to consent once again AND to change the sources they are consenting to. I thought the gdpr plugin might be helpful - but as far as I understand I am not capable to unset the consent state with it. So basically my questions are two:
- how do I unset the consent state of (all) users?
- are they forced to consent for the next login?
1 Reply Last reply
Reply Quote 0

Suggested Topics

T

No footer.js in v16.1.x?
NodeBB Development • • Teemberland

5

0
Votes

5
Posts

84
Views

T

EDIT:

@baris error is gone / fixed. Thank you!
How to setup admin user in config.json in nodebb
NodeBB Development • • venkAT

8

0
Votes

8
Posts

123
Views

@pitaj said in How to setup admin user in config.json in nodebb:

export admin__username="admin"
export admin__password="password"
export admin__password__confirm="password"

using output of cat command is a good choice 😀 , i will try this.

but i don't think using enviroment variables will work.

thanks ~ 👌
1.17.0 Breaking Changes
NodeBB Development • 1.17.0 breaking • • Julian Lam

9

2
Votes

9
Posts

520
Views

Authentication middleware is now called on every page and API route. Plugin routes are also affected if they use routeHelpers.setupPageRoute or routeHelpers.setupAPIRoute.

This fixes an issue we had previously where certain routes were treated by NodeBB as being accessed as guest even though a valid Write API token was passed in. Now, every single page and API route in NodeBB can be authenticated via Write API (or suitable third-party authenticator via response:middleware.authenticate)

In short, the changes:
middleware.authenticate has been deprecated For routes that attach directly to the router (e.g. router.post(...), replace middleware.authenticate with middleware.authenticateRequest and middleware.ensureLoggedIn in order to retain the same behaviour For routes that use setupPageRoute or setupAPIRoute, replace middleware.authenticate with middleware.ensureLoggedIn only. middleware.authenticateOrGuest has been renamed middleware.authenticateRequest Just rename the middleware as necessary
nodebb/nodebb@7da061f0d7c507146d88ce40a381a2f1d443c5b4
0 julianlam committed to nodebb/nodebb refactor: automatically authenticate all requests setup through route helpers (#9357) * refactor: automatically authenticate all requests setup through route helpers * fix: removed connect-ensure-login dependency * fix: bug with some middlewares not defined outside route helper methods
Consent Form
NodeBB Development • • LethalLuigi

2

2
Votes

2
Posts

821
Views

Same. How do I do this?
Has anyone added a third party cookie consent form?
NodeBB Development • • Miguel Guzman

2

0
Votes

2
Posts

25
Views

Please share more details about your nodebb setup. And share what errors you're seeing both on the client side and then server side.