Since kano is deployed with kargo on customer infrastructures local registration has often to be prohibited (eg access by a global service account or SSO).
On the client side routes should be removed and login footer configured. On the server side disallow('external') hooks should be added whenever required (eg on the user service create operation).
Since kano is deployed with kargo on customer infrastructures local registration has often to be prohibited (eg access by a global service account or SSO).
On the client side routes should be removed and login footer configured. On the server side
disallow('external')hooks should be added whenever required (eg on the user service create operation).