way to go Quarksteam! Awesome news! From: "ChrisClark" <cclark@...> To: cf-bosh@... Cc: "cf-dev@..."<cf-dev@...> Date: 20/12/201918:57 Subject: [EXTERNAL]Re: [cf-dev]

Congrats Vlad and the rest of the Quarks team! That's great news.-- Chris Clark Technical Operations Manager Cloud Foundry Foundation

Hello everyone, On behalf of the Quarks team, I'd like to introduce Cloud Foundry Operator v1.0.0. https://github.com/cloudfoundry-incubator/cf-operator/releases/tag/v1.0.0 This is our first

And if you’re looking for some new video content on Quarks, we did a webinar recently which was recorded for your educational

If anyone is looking for a small example of a BOSH release with a Helm chart for Quarks deployment and README docs, I’ve got an example at: *

This is fantastic news,Troy and team. Thanks for sharing. Ill contact you to see if a CAB presentation makes sense. Especially if a brief demo showing ease of deployment could be shown. Slack you

KubeCF (formerly the v3 branch of SUSE/scf) produces builds of CFAR which can be deployed to Kubernetes with Helm and managed by the cf-operator. Though this is currently in the SUSE namespace, the

Hi Everyone, As Abby shared in the update from “Desk of the Executive Director” here, Cloud Foundry Summits in 2020 will be slightly different. Cloud Foundry Summits in 2020 will be

Hello everyone, The Services API Team has been working on a model for the Cloud Controller V3 API for service offerings and service plans. You can view the proposals here: Service Offerings -

Hi, all, Please spare 5 minutes (might be even less) to take this 4 questions survey to help shape Cloud Foundry and the Community Advisory Board (CAB) calls and organization in 2020.

Hi, all, As per discussions in last CAB call, we are canceling the last one of the year (scheduled next week) since it's so close to the year end holidays. We will reconvene on January 15th where we

Hi Everyone, please note: I’ve shared aspreadsheet on CF Slack with a list of tech conferences, dates, and CFP deadlines, etc. I’ll be adding more to the list as I learn about other conferences;

Thanks. The SAML assertion generated by ADFS contains "https://<HIDDEN>/saml/SSO/alias/cloudfoundry-saml-login-dev" while the bearer assertion in the metadata file is

probably https:// and not http://

It's been a while since I dug into that code, but I think the Recipient should match the URL you're posting the message to, which is: http://<host>/uaa/oauth/token/alias/cloudfoundry-saml-login-dev

Thanks. I digged into this a little deeper. During the SAML verification, confirmed is never TRUE and that’s why it gives the following error 2019-12-10T16:45:24.58-0500 [APP/PROC/WEB/1] OUT

1. Take a look at the endpoint `/saml/metadata` on your server. For example https://login.run.pivotal.io/saml/metadata In the metadata, take a look at: urn:oasis:names:tc:SAML:2.0:bindings:URI

Still having issues. I tried several things and they all seem to fail. 1. Per the documenatation, the URL should go to

Assertion can be signed, encrypted(name ID) or both. Unsigned and Unencrypted is not recommended. Filip

Thanks Filip. You are correct and thanks for pointing it out. I will pass Assertion and see what happens. As a side question - I am assuming that the Assertion would have to be unencrypted. right ?