# Cookie-fout met BigBlueButton-integratie

**URL:** <https://meta.discourse.org/t/cookie-bug-with-bigbluebutton-integration/162571>\
**Category:** Bug\
**Created:** [31 augustus 2020 om 15:20 UTC](https://meta.discourse.org/t/cookie-bug-with-bigbluebutton-integration/162571 "2020-08-31T15:20:24Z")\
**Posts on this page:** 1\
**Showing post:** 25

<div class="post-metadata">

**Author:** ![pmusaraj](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pmusaraj/32/119489_2.png) [@pmusaraj](https://meta.discourse.org/u/pmusaraj)\
**Post date:** [1 september 2020 om 18:44 UTC](https://meta.discourse.org/t/cookie-bug-with-bigbluebutton-integration/162571/25 "2020-09-01T18:44:59Z")

</div>

This was not an easy thing to track down (in part because I didn’t have a BBB server set up), but I found the issue. Chrome has changed its cookie policy and this affects BBB in the iframe. I see the below in my Chrome console:

> A cookie associated with a cross-site resource at `http://bbb.discourse.org/` was set without the `SameSite` attribute. It has been blocked, as Chrome now only delivers cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application\>Storage\>Cookies and see more details at [Chrome Platform Status](https://www.chromestatus.com/feature/5088147346030592) and [Chrome Platform Status](https://www.chromestatus.com/feature/5633521622188032).

One way to fix is to allow BBB to run without cookies, I followed [Problems with Full Third-Party Cookie Blocking · Issue #9998 · bigbluebutton/bigbluebutton · GitHub](https://github.com/bigbluebutton/bigbluebutton/issues/9998#issuecomment-675668529) and fixed it by setting `allowRequestsWithoutSession=true` in `/usr/share/bbb-web/WEB-INF/classes/bigbluebutton.properties` and restarting BBB via `bbb-conf --restart`.

---

_[View the full topic](https://meta.discourse.org/t/cookie-bug-with-bigbluebutton-integration/162571)._
