That’s the main concern we have as well – we currently need LDAP for the CLI since SAML doesn’t work in that case, but we’d like SAML for web-based interactions (SSO in a portal, etc.). But

Well, that's a bummer. Is there any way around that? Our SAML is backed by the same LDAP so they are the same user. We can provide a unique ID to correlate SAML with LDAP users. Mike

yes, it would result in two different shadow accounts, differentiated by the value of the user's origin field wrote:

Would the same user logging in via SAML and LDAP result in two different UAA user objects with different sources, so that the user would have two different sets of orgs/spaces/apps? Aaron -- View

Great! I'll dig in and give it a try then. Thanks Filip! Mike

yes, it is entirely possible to run both SAML (as many providers as you need) and LDAP (single provider). we are keeping an eye on the SAML ECP profile to make it easier to handle password grants as

We're investigating converting our UAA from a custom fork that integrates with our organization's SSO to the stock UAA using SAML and/or LDAP. We would like to maintain SSO functionalities for our

Regarding manifest templates, this means that the bosh director can now look at the number of instances per job to calculate the resource pool sizes so it does not need to be specified separately. As

Hey. The simplest way to add this behaviour is to add `cf push` command to `.git/hooks/pre-push` executable file. The detail you can find in git docs [0] In this article you can find the possible

Hi Kinjal, CF push does not support git input afaik. But It would be fairly simple to implement a cf-cli plugin that does that from the client side to offer a heroku-like

Hi, I would like to know if it is possible to deploy applications on cloud foundry using git push. Or is it that only CF CLI can be used for pushing applications? Thanks, Kinjal

Hi, is there a CF API to add multiple users to multiple roles of an organization? I have looked at the CF docs, but did not find any indication that such API exists. Thank you. Regards, Anil

Great release!!! Congrat. Just a couple questions (but if this is the right thread to ask please excuse me and let me know). - Manifest templates no longer include resource pool sizes details

The cf-release v208 was released on May 12th, 2015 - Please see note about merge of UAA/Login server jobs below to maintain zero down time for CC and UAA for existing deployments. Runtime

Hi, Tom, The Diego team does deploy Diego to AWS as part of our testing pipeline. We haven't fully published our tooling for doing so, but you can see some of our process in the deploy_diego CI

Make sure you only delete the resource files, not everything... Jon Price Intel Corp.

Hi, I use spiff manifest templates included by cf-release and diego-release, and generate manifests by spiff, but I usually use the manifests as reference materials. I finally adjust my own manifests

When deploying a Java application to Cloud Foundry the Java memory settings for the application are decided based on the configured memory weighting during staging. This means that, unlike other apps,

When deploying a Java application to Cloud Foundry the Java memory settings for the application are decided based on the configured memory weighting during staging. This means that, unlike other apps,

Hi, this is a follow up on the archived posting https://groups.google.com/a/cloudfoundry.org/forum/?utm_medium=email&utm_source=footer#!msg/vcap-dev/B1W6_vO0oyo/84X1eAtFsKoJ. I cannot find any new