Costin Serban

found during the implementation of #3825

Very well written and explained. The tricky part is how to break the entire functionality into smaller deliverable pieces and coming up with a store design that will adapt to...

sure thing! Spoke with @hardillb earlier this morning and he pointed me to the oauth lib that handles auth between the editor and ff. I also stumbled across https://github.com/jaredhanson/passport/issues/938 in...

I have a feeling that running the entire ff suite (and instances) with valid tls certificates locally would solve the issue, the `set-cookie` headers are being sent, but the cookie...

I would greatly appreciate it!

This is what we're dealing with in a nutshell: 

Status update: After setting up a local docker installation that uses valid TLS certificates over HTTPS with different domains, I was partially successful in loading the NR editor in an...

The impact for development will be quite limited, as you said, localhost is quite lenient specifically for these types of scenarios and localfs won't require valid https configuration _unless_ the...

Port-wise, we're safe, the documentation for CSP headers [frame-ancestor](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/frame-ancestors) host-sources directive allows the use of wildcards. If we're successful in resolving the cookie issue, the next step would be to...

POC of cross domain setup with valid tls certificates https://github.com/FlowFuse/flowfuse/assets/20094749/106cb04d-428b-4222-88c8-8fc6f908c0f4 ### Changes required are as follows: - @flowfuse - we need to allow the app to embed itself for auth...