Issue

As a CloudBees customer you want to setup the authentication for hosted services using SSO with a SAML based identity provider (SAML IdP).

Environment

• CloudBees GrandCentral
• CloudBees Console
• Training portal
• DevOptics

Resolution

How to setup the Identity Provider?

There are various Identity Providers that support SAML 2.0 and their setup is specific to each of them.

If required you can build the XML metadata of a SAML Service Provider with a service like this one: https://www.samltool.com/sp_metadata.php

• EntityId: https://grandcentral.cloudbees.com/
• Attribute Consume Service Endpoint (HTTP-POST): https://grandcentral.cloudbees.com/authenticate/saml/consume
• Single Logout Service Endpoint (HTTP-REDIRECT): https://grandcentral.cloudbees.com/logout

Optional settings are:

• Organization Info
  • Organization Name: cloudbees
  • Organization DisplayName: CloudBees Inc.
  • Organization Url: https://www.cloudbees.com/
• Support Contact
  • Given Name: CloudBees Support
  • Email: support@cloudbees.com

It will give you a file like this one (Don’t use this one which is a sample with an expired validity date):

<?xml version="1.0"?>
<md:EntityDescriptor xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata"
                     validUntil="2017-10-06T13:07:09Z"
                     cacheDuration="PT604800S"
                     entityID="https://grandcentral.cloudbees.com/">
    <md:SPSSODescriptor AuthnRequestsSigned="false" WantAssertionsSigned="false" protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
        <md:SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
                                Location="https://grandcentral.cloudbees.com/logout" />
        <md:NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified</md:NameIDFormat>
        <md:AssertionConsumerService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
                                     Location="https://grandcentral.cloudbees.com/authenticate/saml/consume"
                                     index="1" />
    </md:SPSSODescriptor>
    <md:Organization>
       <md:OrganizationName xml:lang="en-US">cloudbees</md:OrganizationName>
       <md:OrganizationDisplayName xml:lang="en-US">CloudBees Inc.</md:OrganizationDisplayName>
       <md:OrganizationURL xml:lang="en-US">https://www.cloudbees.com/</md:OrganizationURL>
    </md:Organization>
    <md:ContactPerson contactType="support">
        <md:GivenName>CloudBees Support</md:GivenName>
        <md:EmailAddress>support@cloudbees.com</md:EmailAddress>
    </md:ContactPerson>
</md:EntityDescriptor>

The required URLs may differ depending on the IdP in use:

• Single Sign On URL: https://grandcentral.cloudbees.com/authenticate/saml/consume
• Recipient URL: https://grandcentral.cloudbees.com/authenticate/saml/consume
• Destination URL: https://grandcentral.cloudbees.com/authenticate/saml/consume
• Audience Restriction: https://grandcentral.cloudbees.com/

You’ll find more documentation below about SAML 2.0 IdPs and their integration with CloudBees:

• SAML 2.0 for CloudBees with OKTA
• SAML 2.0 for CloudBees with SecureAuth
• SAML 2.0 for CloudBees with OneLogin
• SAML 2.0 for CloudBees with SSOEasy

How to setup an organization with CloudBees?

1/ As an administrator of your cloudbees organization log into https://console.cloudbees.com.

2/ Click on the Organization button on the left.

3/ Click on SAML SSO button (on the right)

4/ Fill in the details as below

• Login URL: The endpoint of your SAML Identity Provider.
• Provision user: Select true if you want visitors (non existent users) with an email address matching your Email domains to be added as new users to your CloudBees organization, this is in accordance with this SAML setup.
• X.509 Certificate: Input your x509 certificate (public key) generated by your SAML identity provider.
• Email domains: Specify the comma separated list of domains for which SAML login process should be triggered.
  • Note: each domain will need to have a TXT record in the format of cloudbees-domain-verification:0123456789abcdef0123456789abcdef01234567 for verification of domain ownership (See step 6 below)

5/ Click Create button

6/ If all goes well you will see a Retry button showing the validation key in the format cloudbees-domain-verification:0123456789abcdef0123456789abcdef01234567 this key will need to added as DNS TXT record.

7/ After the DNS TXT record with above mentioned key has been added click on Retry button, this will validate the domain ownership. Note: there may be an up to 24 hour delay between your record being created and it validating with CloudBees.

8/ If domain ownership has been validated you are all set to use SAML Login process and your SAML configuration should show Certificate Fingerprint instead of the actual X509 certificate.