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 ?

Hi, For SAML Bearer an Assertion object is expected as bas64-url(base64(assertion)). Looks like you are send not the Assertion, but the SAML response object. See 10:44:22.088: [APP/PROC/WEB.0]

The SAML 2 Bearer Grant expects an Assertion XML in the parameter `assertion` You are currently passing a `Response` XML data instead. Correct: <saml:Assertion> Incorrect:

I am trying to prototype a situation where a user is already authenticated to an On-prem application using ADFS using SAML. Now, this application needs to call a web service deployed on cloud.gov

The first release of the Python buildpack after January 1, 2020 will no longer include Python versions 2.7.x. These Python versions will no longer be supported upstream.[1] Please migrate your Python

The first release of the Node.js buildpack after January 5, 2020 will no longer include Node.js versions 8.x. These Node.js versions will no longer be supported upstream.[1] Please migrate your

Hello CF community, Routing Release 0.196.0 has been cut! Release Highlights Platform Operators can now know the maximum impact from a single component on their database details Application

Hi everyone, The CF CLI team released v6.48.0 today which includes improved behavior of random-route flag, few bug fixes and and windows installer update. Please reach out to us in cloudfoundry #cli

The first release of the .NET Core buildpack after January 4, 2020 will no longer include .NET Core versions 2.2.x. These .NET Core versions will no longer be supported upstream.[1] Please migrate

I am delighted. Congratulations!

Hey all, In an effort to have the bosh-linux-stemcell-builder be more maintainable for the bosh team, we are hoping to remove build targets not explicitly maintained by the bosh team. These include

Thanks for the summary email and blog post Hristo and for all of your work and dedication to this project. Like any projects, it had its heyday and moments of excitement. And now retirement. I know at