cf-dev@lists.cloudfoundry.org

Re: [EXTERNAL MESSAGE] Re: [cf-dev] Using SAML 2 Bearer token with our own UAA Server #uaa

probably https:// and not http://

By Filip Hanik · #8808 ·

Re: [EXTERNAL MESSAGE] Re: [cf-dev] Using SAML 2 Bearer token with our own UAA Server #uaa

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

By Filip Hanik · #8807 ·

Re: [EXTERNAL MESSAGE] Re: [cf-dev] Using SAML 2 Bearer token with our own UAA Server #uaa

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

By Shetty, Viraj S [CTR] · #8806 · Edited

Re: Using SAML 2 Bearer token with our own UAA Server #uaa

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

By Filip Hanik · #8805 ·

Re: Using SAML 2 Bearer token with our own UAA Server #uaa

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

By Shetty, Viraj S [CTR] · #8804 ·

Re: Using SAML 2 Bearer token with our own UAA Server #uaa

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

By Filip Hanik · #8803 ·

Re: Using SAML 2 Bearer token with our own UAA Server #uaa

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 ?

By Shetty, Viraj S [CTR] · #8802 ·

Re: Using SAML 2 Bearer token with our own UAA Server #uaa

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]

By Martijn de Boer · #8801 ·

Re: Using SAML 2 Bearer token with our own UAA Server #uaa

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:

By Filip Hanik · #8800 ·

Using SAML 2 Bearer token with our own UAA Server #uaa

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

By Shetty, Viraj S [CTR] · #8799 ·

IMPORTANT NOTICE: [python-buildpack] End of support for Python versions 2.7.x after 2020-01-01

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

By Kashyap Vedurmudi <kvedurmudi@...> · #8798 ·

IMPORTANT NOTICE: [nodejs-buildpack] End of support for Node.js versions 8.x after 2020-01-05

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

By Elliott Shanks · #8797 ·

Routing Release 0.196.0

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

By Keshav Sharma <ksharma@...> · #8796 ·

CF CLI 6.48.0 released today

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

By Mukesh Gadiya · #8795 ·

IMPORTANT NOTICE: [.NET Core buildpack] End of support for .NET Core versions 2.2.x after 2020-01-04

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

By Elliott Shanks · #8794 ·

Re: Eirini is 1.0!

I am delighted. Congratulations!

By Julian Fischer · #8793 ·

Upcoming changes to bosh-linux-stemcell-builder

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

By Aakash Shah · #8792 ·

Re: Announcing cf-abacus end of life

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

By Michael Maximilien · #8791 ·

Announcing cf-abacus end of life

Hi cf-dev, Abacus was started in 2015 by IBM with SAP joining shortly after. Since several years SAP is the only contributor, as it used Abacus in production. Most users do not find the project robust

By Hristo Iliev · #8790 ·

Routing Release 0.195.0

Hello CF community, Routing Release 0.195.0 has been cut! Release Highlights Platform Operators can continue routing to applications and system components even during a control plane outage

By Keshav Sharma <ksharma@...> · #8789 ·

Messages