rodrigods

This post is intended to advocate among quality teams across OpenStack to try, as much as possible, to push their tests upstream. As you may see throughout this post, we have several advantages by taking this approach. Why upstream? At first, why should we bother to submit our tests upstream…

It is also possible to use the Federated Identity feature without using a browser, this is done by the SAML2 ECP (Enhanced Client or Proxy) profile. In the previous post related to TripleO and Federation the ECP part is not detailed. Using the same deployment as in the previous post…

The OpenStack Federated Identity feature has been present for a while and has reached a good mature state. In this post we will use TripleO to setup a real (minimal) OpenStack deployment and later we will manually setup a WebSSO environment using Shibboleth as service provider tool and test it…

After the debut of the feature in the Juno release, Keystone-to-Keystone (K2K) federation has received lots of improvements and bug fixes during the Kilo cycle. Here at the Distributed Systems Lab - UFCG we worked together with contributors from several companies and organizations like CERN, IBM, Rackspace, Yahoo, and HP…

Edit: This tutorial is for the OpenStack Juno release, in Kilo we have several modifications and improvements. One of the coolest features from Juno release for Keystone was the ability to Federate Multiple Keystones or Keystone-to-Keystone (K2K) federation. With this feature, two (or more) cloud providers will be able to…