Multi-Factor Authentication in Flownative Beach
Throughout the last weeks we've been busy with a major rework behind the scenes: We introduced a centralized authentication service for Flownative Beach and future services we are going to offer.
Insights into our work, sneak peeks at projects, interesting technology, …
Throughout the last weeks we've been busy with a major rework behind the scenes: We introduced a centralized authentication service for Flownative Beach and future services we are going to offer.
One of the benefits of using such a standard is, that many tools play well together. There are also regular expressions you can use to check your own made up version numbers. So, since there is a standard, and your tool claims to support it, everything should be clear, right?
At Flownative, we run a lot of tools and applications in Docker containers – most prominently Flownative Beach. Early on, we decided to not rely on off-the-shelf images for PHP, Redis and all the other components we need, because we wanted to know what we are running and not just hope that image maintainers will keep an eye on security issues.
This caused a loss of data from the last three days for 5 websites (as far as we know) and a downtime of about 60 minutes for 62 Beach instances. Among the affected sites were neos.io and flownative.com.
This year the Neos Conference moved to Dresden–and what seemed hardly possible became reality: It was a better conference than ever. As usual the talks, location and spirit were outstanding. Still this year was a bit different…
For me the biggest part of that difference was in the people.
An awesome community! 🚀