Andfrankly cloud application

You must be signed in as a super administrator for this task.

Using Security Assertion Markup Language (SAML), your users can use their Google Cloud credentials to sign in to enterprise-cloud applications.

Set up SSO via SAML for Andfrankly

Here's how to set up single sign-on (SSO) via SAML for the Andfrankly® application.

Step 1: Get Google identity provider (IdP) information
  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Security and then Set up single sign-on (SSO).

    To see Security, you might have to click More controls at the bottom. 

  3. In the Set up single sign-on (SSO) section:
    • Copy and save the SSO URL.
    • Download the IDP Metadata.

In the next step, you send this information to Andfrankly via email. After they respond, you return to the Admin console in Step 3 below to finish SSO configuration.

Step 2: Send IdP information to Andfrankly

Send an email to help@andfrankly.com asking them to enable SAML 2.0 for your organization. Include the following identity provider (IdP) information copied in Step 1:

  • SSO URL 
  • Attach the IDP metadata you downloaded in Step 1 as a text file attachment to the email.

Also, ask Andfrankly to provide you with your organization's "COMPANY_IDENTIFIER", a unique value you need to finish configuring SSO in the Admin console in Step 3 below.

Step 3: Set up Google as a SAML identity provider (IdP)
  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Apps and then SAML Apps.

    To see Apps on the Home page, you might have to click More controls at the bottom. 

  3. Click the plus (+) icon at bottom right.
  4. Locate and click Andfrankly in the application list.
  5. Click Next.

    The Basic information window shows the Application name and Description seen by users.

  6. Click Next.
  7. On the Service Provider Details page, edit the ACS URL and Entity ID, replacing {COMPANY_IDENTIFIER} with the value provided by Andfrankly.
  8. Click Next.
  9. On the Attribute Mapping page, set the Select category and Select user field values as follows for the listed attributes:
     
    Application attribute Select category Select user field
    firstname Basic Information First Name
    lastname Basic Information Last Name
    email Basic Information Primary Email
  10. Click Finish.
Step 4: Enable the Andfrankly app
  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Apps and then SAML Apps.

    To see Apps on the Home page, you might have to click More controls at the bottom. 

  3. Select Andfrankly.
  4. At the top right of the gray box, click Edit Service Compose.

  5. To apply settings to all organizations, click On for everyone or Off for everyone, and then click Save

  6. To apply settings to individual organizational units, do the following: 

    • At the left, select the organizational unit that contains the users whose settings you want to change.
    • To change the setting, select On or Off.
    • To keep the setting the same, even if the parent setting changes, click Override.
    • If the organization's status is already Overridden, choose an option:
      Inherit—Reverts to the same setting as its parent.
      Save—Saves your new setting (even if the parent setting changes).

    Learn more about the organizational structure.

  7. Ensure that your Andfrankly user account email IDs match those in your Google domain.
Step 5: Verify that the SSO is working
  1. Close all browser windows.
  2. Open https://www.andfrankly.com/en/start-page/#login and attempt to sign in. You should be automatically redirected to the Google sign-in page.
  3. Enter your username and password.

After your sign in credentials are authenticated, you are automatically redirected back to Andfrankly.

Was this article helpful?
How can we improve it?