At cloud.gov, we email our customers when there's a newer buildpack available for their applications: https://github.com/cloud-gov/cg-buildpack-notify The template (https://github.com/cloud-gov/cg-bui

This is really a promising step. cloud.gov uses "service accounts", https://cloud.gov/docs/services/cloud-gov-service-account/, which are implemented with: https://github.com/cloudfoundry-community/ua

We may run into similar requirements for cloud.gov, so TLS everywhere would be A+.

Sorry my response was so blunt. Product tradeoff decisions are always hard and you can't make everyone happy. Just wanted to let you know that there are consumers for this feature if you do revisit an

> We see the UAA more frequently used as an identity proxy than as an IdP This may be true because UAA doesn't support MFA. cloud.gov runs its own IdP simply because MFA is not supported by UAA. To qu