Raghd Hamzeh

> So i guess this app won't work after May 20 as the less secure access will be disabled. @schneemaier I believe you will still be able to use [App...

@39aldo39 May I recommend that you rename this issue to become: "Contact Groups/Tags/Categories" just so that people who search for those phrases come across this issue instead of creating a...

> I noticed that Semgrep and Snyk are failing, but I wasn't sure if that is expected if I don't have those accounts (I don't believe they're free offerings, but...

@mimi89999 I personally would prefer it as a second factor. Not sure if requiring some thing like TwoOff(password, webauthn, 2fa) code is worth the trouble to give users the choice....

@professorabhay how are things going? If you have decided not to work on this task, please do let us know. If you are still working on it, I would encourage...

Hi @professorabhay - there's these comments from @miparnisari and @jon-whit https://github.com/openfga/openfga/pull/1339#issuecomment-1927344675 https://github.com/openfga/openfga/pull/1339#issuecomment-1936293178 As Jon mentioned, start with focusing on pkg/server and internal to narrow down scope. You can use the...

Yep! The iframe is the main problem why you are encountering this issue and why we need CORS enabled. At the moment we allow localhost:3000 explicitly on play.fga.dev. Unfortunately until...

In your case here though the CORS is not from the playground, but from the OpenFGA server. May I ask that you show us the network tab and the logs...

> I just hit a similar error running the OpenFGA playground under a custom hostname. Hi @apexskier - the playground will only work with `localhost:3000`. It will not load on...

Thanks for asking @filipstiglic - right now we don't have enough tests to fully confirm. However we are investigating and working on [several issues](https://github.com/orgs/openfga/discussions/98) impacting performance with PostgreSQL, some related...