Arvados

"Trusted client setting" in http://doc.arvados.org/install/install-workbench-app.html deployments more complicated.

Many projects use the "user-admin-password-admin" technique on fresh installation to simplify things. Once everything is installed then a password change or a new admin user can take place. Of course if the user decides to leave it after the installation and it's a production server, this will mean a security problem for the user. But my guess that no one that is concearn about seciriyt will leave the default setting of any installation

That said, creating a well known token for that admin user, will enable us to create other objects while deploying a cluster.