Re: Resuming UAA work


Aristoteles Neto
 

From the perspective of using BOSH without CF, moving the users to the manifest is actually an improvement, as it allows you to list the actual users without logging in to the DB.

Are there any plans to split out UAA from Cloud Foundry? More specifically I’d love to be able to have groups / permissions scheme for deployments / commands without needing to install CF.

-- Neto

On 29/05/2015, at 10:33, Dmitriy Kalinin <dkalinin(a)pivotal.io> wrote:

Hey all,

We have resumed BOSH & UAA integration work: https://www.pivotaltracker.com/n/projects/1285490 to be worked on by a single pair.

As part of this work we are going to provide two options how to configure the Director auth:
- without UAA [default] (already exists, but we want to simplify it)
- with UAA (currently being worked on)

Currently Director only works without UAA and has its own user management functionality. There is the users table in the DB and CLI provides create/delete user commands. I would like to simplify this functionality as much as possible. Users would be configured statically in the manifest for the Director so that we can delete users table and associated commands.

Here is how the Director manifest would look like for 'Director without UAA' configuration:

properties:
director:
users:
- {name: admin, hashed_password: $1$0497b6da$8/0owfq5zblA3o7kXQgGy} # crypted 'password'
- {name: admin2, hashed_password: $1$0497b6da$8/0owfq5zblA3o7kXQgGy} # crypted 'password'
...

For more complex use cases, we will encourage people to use Director auth via UAA once that becomes available so that LDAP, password, lockout policies, etc. can be configured.

Thoughts?

Dmitriy
_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

Join cf-bosh@lists.cloudfoundry.org to automatically receive all group messages.