BaaS | Turró.Org

Understanding BaaS

BaaS is a full-featured service running in a cloud, usually with not less than 4Gb of RAM serving a minimum of 2 vCPU.

Well, this configuration is by choice. The BaaS structure is distributed and fully scalable. The databases could be located on different computers, using different database servers. The same applies to the web application, running on a JEE compliant server. BaaS fits perfectly on Amazon Web Services, like EC2, EBS and RDS.

BaaS stands for BrightSide as a Service.

BaaS from the foundations

BaaS components, BrightSide and Elephant, are Open Source projects hosted at TiC Foundation. Both can be freely distributed.

For differences and relation between Turro.Org and TiC Foundation, see here.

The full dependency tree can be found here.

For developers, source code can be downloaded here under the OSI approved AGPL license.

Also, source code can be browsed here.

How does BaaS integrates with other services?

BlueBee service is a retailer brand example, based on BaaS. As you can see in this graphic, BaaS integrates seamlessly.

The BlueBee service is described here.

BaaS Service
Foundation Hub
TiC Foundation

Turró.Org BaaS has a self-hosted unique SSO method. Only affects BaaS users and the implementation isn't provided as standard. Developers can implement their own methods by using the IElephantSSO interface.

Relevant features

Keep me signed feature, substitutes the Remember me.
Keeps client signature across multiple sessions.
Users will be able to sign out remotely from multiple equipments.
Users will be able to track their activity.

Differences when using SSO

Password is never remembered when using SSO.
After three months of inactivity, SSO assertions will be removed and user forced to introduce the password.
Major changes on browsers may invalidate an SSO session. User wil be required to re-authenticate.
Live links became optional and no longer a default option.

The flow

Single Sign On will be fully deployed on March 19. In order to make it consistent with Live Links and to actually substitute them, changes will follow this roadmap.

March 2019	SSO substitutes current login system as default authentication system. The only SSO entry point will be the login form. Live Links will continue to work as expected.
April 2019	Publication Live Links will be substituted for normal links. Password reminder will direct to a new SSO entry point. Users will be able to check on how many devices are signed. Live Links will be removed for users with an SSO session.
May 2019	Live Links will be removed except for those explicitly set.

Single Sign On and Live Links are individually activated. BaaS owners can choose to deactivate one or both whenever required.