Help – Litmus http://litmus.com/help Sun, 16 Sep 2018 18:49:00 +0000 en-US hourly 1 http://wordpress.org/?v=4.2.2 Why do I see a spike in Yahoo! Mail opens? https://litmus.com/help/uncategorized/why-do-i-see-a-spike-in-yahoo-mail-opens/ https://litmus.com/help/uncategorized/why-do-i-see-a-spike-in-yahoo-mail-opens/#comments Sun, 16 Sep 2018 18:49:00 +0000 https://litmus.com/help/?p=3785 In July and August of 2018 we identified an issue that caused an increase in Yahoo! Mail open reports in Email Analytics triggered by Yahoo! Mail’s Proxy Server. What’s Yahoo! Mail’s Proxy? In March 2018, Yahoo! Mail introduced image caching. Rather than serving images from their original server, Yahoo! started caching all images, and now…

The post Why do I see a spike in Yahoo! Mail opens? appeared first on Help – Litmus.

]]>
In July and August of 2018 we identified an issue that caused an increase in Yahoo! Mail open reports in Email Analytics triggered by Yahoo! Mail’s Proxy Server.

What’s Yahoo! Mail’s Proxy?
In March 2018, Yahoo! Mail introduced image caching. Rather than serving images from their original server, Yahoo! started caching all images, and now serves them via their own proxy servers. You can read more about this update on the Litmus Blog.

Increases in email opens triggered by Yahoo! Mail’s proxy server
In Litmus Email Analytics, any opens triggered by Yahoo! Mail’s proxy are recorded as “Yahoo Mail”, “Via Yahoo’s Image Cache“. Beginning around July 13, 2018, we’ve discovered a steep increase in open reports triggered by Yahoo! Mail’s proxy.

On or around this date, Yahoo! and AOL merged their backend infrastructures. As part of this merger two things happened:
– Both Yahoo! and AOL opens are now processed by the same Yahoo! Proxy server
– Yahoo! made a subtle change to their proxy server that caused it to retry Litmus’ Email Analytics tracking pixel up to 4 times, resulting in an increase in open reports for Yahoo! Mail

We have fixed the way we record these opens, so they will no longer be inflated. However, since both Yahoo! Mail and AOL are now processed by the same backend servers, we can no longer distinguish between them. That’s why both AOL and Yahoo! opens will report as Yahoo!/AOL going forward.

The net result of these changes are:

– Opens on AOL and Yahoo! Mail from July 13 to August 8 will be reported as Yahoo! and will likely be 4 times larger than normal. For example if you had 3 Yahoo! opens and 2 AOL opens in this window that would report as 20 Yahoo! Opens (3 + 2 = 5 real opens, 5*4 = 20). Only opens in that window are affected by this.
– Going forward, all Yahoo! and AOL opens will be reported as Yahoo/ AOL.

If you have any questions, please don’t hesitate to reach out to hello@litmus.com.

The post Why do I see a spike in Yahoo! Mail opens? appeared first on Help – Litmus.

]]>
https://litmus.com/help/uncategorized/why-do-i-see-a-spike-in-yahoo-mail-opens/feed/ 0
Setting up ESP Sync for Salesforce Marketing Cloud https://litmus.com/help/testing/builder/setting-up-esp-sync-for-salesforce-marketing-cloud/ https://litmus.com/help/testing/builder/setting-up-esp-sync-for-salesforce-marketing-cloud/#comments Tue, 04 Sep 2018 14:56:08 +0000 https://litmus.com/help/?p=3688 With ESP Syncing for Salesforce Marketing Cloud, you can automatically sync your email from Builder to SFMC in a single click. Setting up SFMC requires some extra inputs: Username, Password, Client ID and Client secret. To connect Litmus to your Salesforce Marketing Cloud instance you need to setup Litmus as a “Connected App”. The instructions…

The post Setting up ESP Sync for Salesforce Marketing Cloud appeared first on Help – Litmus.

]]>
With ESP Syncing for Salesforce Marketing Cloud, you can automatically sync your email from Builder to SFMC in a single click.

Setting up SFMC requires some extra inputs: Username, Password, Client ID and Client secret.

Screen Shot 2017-07-21 at 10.41.38 PM

To connect Litmus to your Salesforce Marketing Cloud instance you need to setup Litmus as a “Connected App”. The instructions are available here on the Salesforce website and below in detail.
Important: You will need Administrative rights on you SFMC account to set this up.

  1. The first step is to create an installed package. Go to Administration -> Account -> Installed Packages and create NEW
    create-package
  2. Give the package a name and description and save it. name-package
  3. Under Components, click Add Component and select API Integrationselect-api-integration
  4. In the permissions section select permissions for Email: Read, Write, Send; and Documents and Images: Read, Write
    select-permissions
  5. Once you click Save you will see the API details CLIENT ID and CLIENT SECRET. Copy these details and enter them into Litmus. You can set up your connection to Salesforce Marketing Cloud either in the Builder Sync Setup area of a Litmus Builder document (Sync to ESP -> Add New ESP) or go to the Settings -> Manage ESP page in Litmus. You will need to enter your administrative credentials and the Client ID and Secret for the API component.

The post Setting up ESP Sync for Salesforce Marketing Cloud appeared first on Help – Litmus.

]]>
https://litmus.com/help/testing/builder/setting-up-esp-sync-for-salesforce-marketing-cloud/feed/ 0
How to start a spam test using an ESP connection https://litmus.com/help/testing/spam/how-to-start-a-spam-test-using-an-esp-connection/ https://litmus.com/help/testing/spam/how-to-start-a-spam-test-using-an-esp-connection/#comments Fri, 13 Jul 2018 15:12:25 +0000 https://litmus.com/help/?p=3634 Connecting your ESP to Litmus makes it fast and easy to start a Spam test. Simply select the draft email to test and Litmus will automatically use your ESP connection to get your email scanned across 25+ different deliverability tests and blacklists. We currently have ESP Integrations support for the following ESPs: MailChimp (Plus plans…

The post How to start a spam test using an ESP connection appeared first on Help – Litmus.

]]>
Connecting your ESP to Litmus makes it fast and easy to start a Spam test. Simply select the draft email to test and Litmus will automatically use your ESP connection to get your email scanned across 25+ different deliverability tests and blacklists.

We currently have ESP Integrations support for the following ESPs:

  • MailChimp (Plus plans and above)
  • Campaign Monitor (Plus plans and above)
  • Salesforce Marketing Cloud, formerly ExactTarget (Available exclusively on Litmus Enterprise)
  • Eloqua (Available exclusively on Litmus Enterprise)
  • Marketo (Available exclusively on Litmus Enterprise)

How to use ESP Integrations for Spam Testing:

  1. First use the Manage ESPs page to connect to Litmus to your ESP account.
  2. Select “Start a new Spam Test” in the Spam Test section of Litmus
  3. On the “Connect ESP and Send” tab, select one of your connected ESPs from the dropdown.starting a spam test2
  4. Once selected, your recently created draft emails will appear in a list below.  Litmus provides a list of the last 30 email drafts by creation date.
  5. Select one of the draft emails.
  6. Select “Start your test”.
  7. Your tests results will automatically begin to start populating.  Litmus uses your ESP to send your email to more than 25 different deliverability testing locations to assess issues that may lower your deliverability rates.
  8. Click  “Results” to view your results.

For more information on Spam Testing see this article.   

For more information on how to integrate Litmus with your ESP see this article.

The post How to start a spam test using an ESP connection appeared first on Help – Litmus.

]]>
https://litmus.com/help/testing/spam/how-to-start-a-spam-test-using-an-esp-connection/feed/ 0
How to use the Settings > Integrations page https://litmus.com/help/accounts/account-settings/how-to-use-the-settings-integrations-page/ https://litmus.com/help/accounts/account-settings/how-to-use-the-settings-integrations-page/#comments Tue, 19 Jun 2018 18:57:24 +0000 https://litmus.com/help/?p=3594 The Integrations page in settings is only available to customers who have authorized an external application, like an ESP, to access their Litmus account. You must authorize access to Litmus from within the partner application, which will enable you to seamlessly test and preview using Litmus directly within that application for increased productivity. The Integrations…

The post How to use the Settings > Integrations page appeared first on Help – Litmus.

]]>
The Integrations page in settings is only available to customers who have authorized an external application, like an ESP, to access their Litmus account. You must authorize access to Litmus from within the partner application, which will enable you to seamlessly test and preview using Litmus directly within that application for increased productivity.

The Integrations page lets you disconnect Litmus from an authorized application when you no longer want to allow that application to have access to your Litmus account. The page can only be used by Full Users, Admins, and Account Holders.

To disconnect an authorized application, click on the trash can icon to the left of the application for which you wish to remove access.

The post How to use the Settings > Integrations page appeared first on Help – Litmus.

]]>
https://litmus.com/help/accounts/account-settings/how-to-use-the-settings-integrations-page/feed/ 0
How to use the Settings > Manage ESPs page https://litmus.com/help/testing/spam/how-to-use-the-settings-manage-esps-page/ https://litmus.com/help/testing/spam/how-to-use-the-settings-manage-esps-page/#comments Tue, 05 Jun 2018 20:12:23 +0000 https://litmus.com/help/?p=3589 The Manage ESPs page in Litmus settings is only available to Plus, Pro, and Enterprise plan customers.  The page can only be used by Full Users, Admins, and Account Holders. The Manage ESPs page lets you connect Litmus and your Email Service Providers (ESPs) to automate the saving of email content. This saves you from…

The post How to use the Settings > Manage ESPs page appeared first on Help – Litmus.

]]>
The Manage ESPs page in Litmus settings is only available to Plus, Pro, and Enterprise plan customers.  The page can only be used by Full Users, Admins, and Account Holders.

The Manage ESPs page lets you connect Litmus and your Email Service Providers (ESPs) to automate the saving of email content. This saves you from having to copy and paste content between Litmus and your ESP.

To add an ESP connection:  

  1. Click on “Add a new ESP” to connect your ESP to your Litmus account.
  2. A new tab will open that asks for your credentials to your ESP
  3. Once you enter your credentials for your ESP, you will be able to use your ESP connection in either Builder, Spam Testing, or both.  
  4. You should create an ESP connection for each login you have with your ESP
  5. The Manage ESP page will display which service the ESP connection works with

To delete an ESP connection:

  1. Click on the trash can icon on the Manage ESP page for the connected ESP account
  2. Press “OK”

For more help with setting up an ESP Integration see, check out this article.

Frequently Asked Questions: Connecting to ESPs

Which ESPs does Litmus integrate with for ESP Synching for Builder?

We currently have ESP Syncing support for the following ESPs:

  • MailChimp (Plus plans and above)
  • Campaign Monitor (Plus plans and above)
  • Salesforce Marketing Cloud, formerly ExactTarget (Available exclusively on Litmus Enterprise)
  • IBM Watson Campaign Automation, formerly Silverpop (Available exclusively on Litmus Enterprise)
  • Eloqua (Available exclusively on Litmus Enterprise)
  • Marketo (Available exclusively on Litmus Enterprise)
Which ESPs does Litmus integrate with for Spam Testing?

We currently have ESP Integrations support in Spam Testing for the following ESPs:

  • MailChimp (Plus plans and above)
  • Campaign Monitor (Plus plans and above)
  • Salesforce Marketing Cloud, formerly ExactTarget (Available exclusively on Litmus Enterprise)
  • Eloqua (Available exclusively on Litmus Enterprise)
  • Marketo (Available exclusively on Litmus Enterprise)

 

The post How to use the Settings > Manage ESPs page appeared first on Help – Litmus.

]]>
https://litmus.com/help/testing/spam/how-to-use-the-settings-manage-esps-page/feed/ 0
Integrate Litmus with Your Email Service Provider https://litmus.com/help/testing/spam/integrate-litmus-with-your-email-service-provider/ https://litmus.com/help/testing/spam/integrate-litmus-with-your-email-service-provider/#comments Tue, 05 Jun 2018 20:12:28 +0000 https://litmus.com/help/?p=3587 By connecting your email service provider (ESP) and Litmus, it’s never been easier to build and test your email.  Connect to your ESPs to enable file syncing from Litmus Builder and to enable Spam Testing by selecting your email drafts without leaving Litmus.   ESP Syncing for Litmus Builder With ESP Syncing for Litmus Builder,…

The post Integrate Litmus with Your Email Service Provider appeared first on Help – Litmus.

]]>
By connecting your email service provider (ESP) and Litmus, it’s never been easier to build and test your email.  Connect to your ESPs to enable file syncing from Litmus Builder and to enable Spam Testing by selecting your email drafts without leaving Litmus.  

ESP Syncing for Litmus Builder

With ESP Syncing for Litmus Builder, you can automatically sync your code from Builder to your ESP with a click of a button. Once connected, whenever you make any changes to your code in Builder, it automatically updates in your ESP, too.

ESP Syncing for Litmus Builder is available on the following ESPs by plan type:

Plus + Pro:

  • MailChimp
  • Campaign Monitor

Enterprise

  • MailChimp
  • Campaign Monitor
  • Salesforce Marketing Cloud (formerly ExactTarget)
  • IBM Watson Campaign Automation (formerly Silverpop)
  • Marketo
  • Eloqua

Learn more about ESP Syncing for Litmus Builder, including how to set it up for each ESP and troubleshooting.

ESP Integrations for Spam Testing

Connect your ESP to Litmus to start a spam test by selecting a draft email. Email drafts appear in the Litmus Spam Testing modal.  Select one and Litmus will automatically have your draft scanned across 25+ different deliverability tests and blacklists.

We currently have ESP Integrations support in Spam Testing for the following ESPs:

Plus + Pro:

  • MailChimp
  • Campaign Monitor

Enterprise

  • MailChimp
  • Campaign Monitor
  • Salesforce Marketing Cloud (formerly ExactTarget)
  • Marketo
  • Eloqua

 

The post Integrate Litmus with Your Email Service Provider appeared first on Help – Litmus.

]]>
https://litmus.com/help/testing/spam/integrate-litmus-with-your-email-service-provider/feed/ 0
Litmus Proof FAQs https://litmus.com/help/products/proof/getting-started-with-proof/ https://litmus.com/help/products/proof/getting-started-with-proof/#comments Wed, 23 May 2018 14:58:45 +0000 https://litmus.com/help/?p=3574 What is Proof? Proof is a new feature for customers with a Litmus Enterprise plan. Proof aims to simplify the review and approval process of email design and development. Use Proof to get feedback from stakeholders directly on your email campaigns so you can easily review, collaborate, and resolve changes and get your campaigns out the…

The post Litmus Proof FAQs appeared first on Help – Litmus.

]]>
What is Proof?
Proof is a new feature for customers with a Litmus Enterprise plan. Proof aims to simplify the review and approval process of email design and development. Use Proof to get feedback from stakeholders directly on your email campaigns so you can easily review, collaborate, and resolve changes and get your campaigns out the door faster.

Which plans and users can access Proof?
Proof is available on the Litmus Enterprise plan. Users with Administrative or Full access can create Proofs and comment on Proofs, while “Reviewer” users are restricted to viewing and commenting on proofs.

Will Proof be available on Basic, Plus or Pro plans in the future?
For the time being Proof is an Enterprise-only feature. We may in the future make it available in other plans. Timing and details have not been determined.

What are the new “Full” and “Reviewer” user roles?
Litmus recently renamed the “Active” user role to “Full” to better indicate what permissions the role provides. For Enterprise customers we have also renamed the Read-Only role to “Reviewer”.

Full users can create Emails in Builder, generate Checklists, use the campaign features in Analytics and create Proofs. Full users count toward an account’s seat limits.

Reviewers can view and comment on Proofs and have access to view Checklists, Previews and Analytics reports. Reviewer users do not count toward any seat limits.

What are the Litmus user privileges and roles?
For customers on Plus and above plans, members of your Litmus account can be given different privileges, enabling you to control access to the various features of Litmus. Permissions and roles differ by plan type. Here is a breakdown of the roles and privileges available to your team members:

Plus and Pro Accounts:
Admin: Access to all aspects of your account including billing and team members.
Full: Can create new emails in Builder, create Checklists and Previews, generate Email Analytics codes and CSV reports. Full users can also create new ESP connections
Read Only: Can view existing emails, tests, and campaign results in Analytics. Read Only members cannot delete or modify anything in your Litmus account.

Enterprise Accounts:
Admin: Access to all aspects of your account including billing and team members.
Full: Can create new emails in Builder, create Checklists and Previews, generate Email Analytics codes and CSV reports. Full users can also create new ESP connections
Reviewer: Can view existing emails, tests, and campaign results in Analytics. Can review Proofs they were invited to and comment on them. Reviewers cannot delete or modify anything in your Litmus account.
Proof Reviewer: Can view only the Proof section of Litmus. Can review Proofs they were invited to and comment on them.  Proof Reviewers cannot create new Proofs or delete or modify anything in your Litmus account.  Proof Reviewers are created when you invite a new user, not currently on your account, to view a Proof by entering their email into the ‘Share’ dialog. The Proof Reviewer role is also automatically assigned to all new users who are added to an account by commenting on a public Proof page.

How do I share Proofs?

Sharing a Proof enables you to get feedback from others.  Proofs can be shared t by using the “Share” button. There are two methods of sharing a Proof with others: inviting users and creating a share link.

  1. Inviting users

Proof Share ModalInviting users sends an email invitation and link directly to those you want to provide feedback. Users and Groups on the account are shown in the list in the dialog box.  

Simply check off which user or Group you wish to send to, type a note and and click Share.

If you need to share with someone who is not on your Litmus account you can add them as a Reviewer.  Simply type in their email address and hit Enter to add them. Newly invited users become Proof Reviewers on the account and are granted access to the Proofs you share with them.  They will appear in the user list when sharing any subsequent Proofs.

Enterprise accounts can add an unlimited number of free Reviewer members to their accounts so that you can easily get feedback on Proofs from clients and other stakeholders.

Note: Proof Reviewers do not have access to other areas of Litmus.

  1. Creating a Share Link

Proof share public
Create a public sharing link in order to easily share an email proof in other collaboration or project management tools like Slack, Asana, Jira or Trello.  The public sharing link allows anyone with the Link to view the Proof so share it only with people you trust. Simply use the switch to turn on the Public link and copy and paste the link where you want to share it. If you are concerned about making your Proof public, use the Invite Users tab which requires users to be invited and login before viewing the Proof.

Public links remain public for 30 days or until the Public switch is turned off in the Create a Share Link dialog box. Although Public Share Links can be seen by anyone, commenting requires a user to sign in or create an account.  New users who sign in on the Public Sharing Link are added to your account as Proof Reviewers and only have permission to view the Proof you have shared with them.

Can I share Proofs with users who are not on my Litmus account?

You can share Proofs with anyone on your account so you do currently need to add them as a member before you can request feedback. Enterprise accounts can add an unlimited number of Reviewer members to their accounts so that you can easily get feedback on Proofs from clients and other stakeholders. There is no charge for Enterprise accounts to add Reviewers.

How do I restrict access to Proofs on my account?
Reviewers can access and review Proofs that they have been invited to. When a reviewer is asked to provide feedback they receive an email that links them directly to a single Proof. (Note that prior to July 4, 2018 Reviewers had access to all Proofs on an account. Since that date Reviewers only get access to Proofs they are asked to provide feedback on).

Enterprise customers can use Subaccounts to restrict access to Proofs by placing the reviewers on an account that contains only the Proofs they want to share with them.

The post Litmus Proof FAQs appeared first on Help – Litmus.

]]>
https://litmus.com/help/products/proof/getting-started-with-proof/feed/ 0
Setting up SAML/SSO with a generic or custom IdP https://litmus.com/help/accounts/account-settings/setting-up-samlsso-with-a-generic-or-custom-idp/ https://litmus.com/help/accounts/account-settings/setting-up-samlsso-with-a-generic-or-custom-idp/#comments Wed, 18 Apr 2018 01:39:48 +0000 https://litmus.com/help/?p=3536 This section explains step by step how to configure SAML single sign-on (SSO) between Litmus and your custom identity provider (IdP). This feature is currently in beta testing. If you are interested in enabling SAML SSO in Litmus using a generic or custom IdP, please contact us at SSObeta@litmus.com. New user seat creation is not…

The post Setting up SAML/SSO with a generic or custom IdP appeared first on Help – Litmus.

]]>
This section explains step by step how to configure SAML single sign-on (SSO) between Litmus and your custom identity provider (IdP).

  • This feature is currently in beta testing. If you are interested in enabling SAML SSO in Litmus using a generic or custom IdP, please contact us at SSObeta@litmus.com.
  • New user seat creation is not supported via SAML. Users must be created within Litmus first and then authenticated via you IdP prior to logging into Litmus.
  • Only the Litmus account holder will be able to access and configure SAML settings on an account.
  • SAML functionality is available with a Litmus Enterprise plan.

1) As the Litmus account holder, log into your parent Litmus account, select “Sub accounts” from the side menu, then “Security” and finally the “SAML” tab in the settings.

2) Toggle on “Enable SAML.”

3) If you would like your users to only access Litmus via SSO with your IdP solution, you can check the box “Force sign in with SAML.”

Note: When this option is active

  • The main Litmus account holder will still be able to sign in to Litmus using their Litmus credentials via the Litmus login screen. (This is to prevent the main account holder from getting locked out of full account administrative functionality. Other users will be forced to login via SAML)
  • Password resets using the “Forgotten Password?” option on the regular Litmus login screen will be disabled for all users

4) Select ‘Generic’ as your IdP.

5) Take note of the “Post-back URL (Assertion Consumer Service URL)” and “Audience URI (Service Provider Entity ID)”, as you will need these when configuring a new app for Litmus within your IdP solution.

onelogin13

6) Log in to your preferred Identity Provider as an administrator.

7) Following the IdP documentation, create an “app” that uses the Post-back URL and the Audience URI from step 5. If you have the option to upload a Litmus logo as an app icon, you can find one here.

8) Configure the IdP application to allow access to all the relevant users within the organization.

9) Once the app is created within your IdP solution, locate and copy the “single sign-on URL”. Then return to the SAML configuration page within Litmus (as outlined within step 1) and paste it into the “SAML 2.0 Endpoint (HTTP)” field.

onelogin14

10) Repeat the above process, but this time locate and copy the “X.509 Signing Certificate” from your IdP and paste it into the “X.509 Certificate” field on the SAML configuration page within Litmus.

onelogin15

11) Once done, click the “Save SAML settings” button at the bottom of the SAML configuration page within Litmus.

The post Setting up SAML/SSO with a generic or custom IdP appeared first on Help – Litmus.

]]>
https://litmus.com/help/accounts/account-settings/setting-up-samlsso-with-a-generic-or-custom-idp/feed/ 0
Setting up SAML/SSO with OneLogin https://litmus.com/help/accounts/account-settings/setting-up-samlsso-with-onelogin/ https://litmus.com/help/accounts/account-settings/setting-up-samlsso-with-onelogin/#comments Wed, 18 Apr 2018 01:23:17 +0000 https://litmus.com/help/?p=3511 This section explains step by step how to configure SAML single sign-on (SSO) between Litmus and OneLogin as the identity provider. New user seat creation is not supported via SAML. Users must be created within Litmus first and then authenticated via OneLogin prior to logging into Litmus. Only the Litmus account holder will be able…

The post Setting up SAML/SSO with OneLogin appeared first on Help – Litmus.

]]>
This section explains step by step how to configure SAML single sign-on (SSO) between Litmus and OneLogin as the identity provider.

  • New user seat creation is not supported via SAML. Users must be created within Litmus first and then authenticated via OneLogin prior to logging into Litmus.
  • Only the Litmus account holder will be able to access and configure SAML settings on an account.
  • SAML functionality is available with a Litmus Enterprise plan.

 

1) As the Litmus account holder, log into the parent Litmus account, select “Sub-accounts” from the side menu, then “Security”, and finally the “SAML” tab in the settings.

2) Toggle on “Enable SAML.”

3) If you would like your users to only access Litmus via SSO with OneLogin, you can check the box “Force sign in with SAML.”

Note: When this option is active

  • The main Litmus account holder will still be able to sign in to Litmus using their Litmus credentials via the Litmus login screen. (This is to prevent the main account holder from getting locked out of full account administrative functionality. Other users will be forced to login via SAML)
  • Password resets using the “Forgotten Password?” option on the regular Litmus login screen will be disabled for all users

4) Select OneLogin as your IdP.

5) Take note of the “Audience URN”, “ACS (Consumer) URL Validator” and “ACS (Consumer) URL”, as you will need these when configuring a new app for Litmus within OneLogin.

Onelogin1

6) In a new browser tab or window (as you will need to view both OneLogin and Litmus during configuration), log in to OneLogin as an administrator and go to Administration → Apps → Add Apps.

Onelogin2

7) Look up the term “SAML Test Connector (IdP)” in the ‘Find Apps’ search box and select the result titled SAML Test Connector (IdP).”

onelogin3

8) Next configure the new application by changing the display name to “Litmus”, ensuring the “Visible in Portal” option is toggled on and uploading a copy of the Litmus logo (found here) as the icon for the app. Once done, click “save” in the top right of the screen.

onelogin4

9) Once saved, navigate to the “Configuration” tab and paste in the “Audience URN”, “ACS (Consumer) URL Validator” and “ACS (Consumer) URL” from Litmus (as referenced in step 5) and click save.
Note: You may also add your “single Logout URL” at this time if you wish.

onelogin5

10) Next, navigate to the “SSO” tab. Copy the “SAML 2.0 endpoint (HTTP)” field from OneLogin and paste it into the corresponding field on the Litmus SAML configuration tab (See step 1).

onelogin6

onelogin7

11) Return to Onelogin SSO tab and open the X.509 Certificate by right-clicking the “View Details” link under the certificate field and selecting “Open Link in a New Tab.” Then copy the certificate using the “Copy to Clipboard” icon. Paste the X.509 Certificate into the corresponding field on the Litmus SAML configuration tab (See step 1). Once the certificate has been pasted into Litmus, click “Save SAML settings.”

onelogin8

onelogin9

onelogin10

12) You are now ready to assign the Litmus application to your OneLogin users, groups or role types. To do this, return to OneLogin as an administrator and go to Administration →Users then select the relevant option within the “Users” drop-down menu.

onelogin11

13) Select the users, roles or groups that require access to Litmus, then navigate to the “Applications” tab and click the “New App” button. From here, follow the on-screen instructions and select the newly created “Litmus” application before saving.

onelogin12

The post Setting up SAML/SSO with OneLogin appeared first on Help – Litmus.

]]>
https://litmus.com/help/accounts/account-settings/setting-up-samlsso-with-onelogin/feed/ 0
Setting up SAML/SSO with Okta https://litmus.com/help/products/setting-up-samlsso-with-okta/ https://litmus.com/help/products/setting-up-samlsso-with-okta/#comments Tue, 27 Mar 2018 13:56:54 +0000 https://litmus.com/help/?p=3486 This section explains step by step how to configure SAML single sign-on (SSO) between Litmus and Okta as the identity provider. Things to Note New user seat creation is not supported via SAML. Users must be created within Litmus first and then authenticated via Okta prior to logging into Litmus. Only the Litmus account holder…

The post Setting up SAML/SSO with Okta appeared first on Help – Litmus.

]]>
This section explains step by step how to configure SAML single sign-on (SSO) between Litmus and Okta as the identity provider.

Things to Note

  • New user seat creation is not supported via SAML. Users must be created within Litmus first and then authenticated via Okta prior to logging into Litmus.
  • Only the Litmus account holder will be able to access and configure SAML settings on an account.
  • SAML functionality is available with a Litmus Enterprise plan.

 

1) Log into Litmus and select “Sub-accounts” from the side menu, then “Security” and finally the “SAML” tab in the settings.

    2) Toggle on “Enable SAML.”
    3) If you would like your users to only access Litmus via SSO with Okta, you can check the box “Force sign in with SAML”.

Note: When this option is active

  • The main Litmus account holder will still be able to sign in to Litmus using their Litmus credentials via the Litmus login screen. (This is to prevent the main account holder from getting locked out of full account administrative functionality. Other users will be forced to login via SAML)
  • Password resets using the “Forgotten Password?” option on the regular Litmus login screen will be disabled for all users
    4) Select Okta as your IDP.
    5) Take note of the Post-back URL and the Audience URI, as you will need these when configuring a new App for Litmus within Okta.

saml1

    6) Log in to Okta as an administrator, go to Admin → Applications (menu) → Applications (item)
    7) Click the “Add Application” button.

saml2

      8) Click

Create New App

    (under the “Can’t find an app?”) heading on the left)

saml3

    9) Select SAML 2.0 as the sign on method and click the Create button.

saml4

      10) Enter Litmus as the name of the new app. If you wish to upload a Litmus logo (

one can be found here

    ) you can do so by clicking on the “Upload Logo” button, then click the “Next” button.

saml5

    11) Paste the “Post-back URL” and the “Audience URI” from Litmus (as shown in step 3) into the “Single sign-on URL” and “Audience URI (SP Entity ID)” fields respectively.

saml6

    12) On the same screen, but a little bit further down the page, you’ll see the ATTRIBUTE STATEMENTS (OPTIONAL) section. You want to add three “attributes” here:

saml7

Once added, click the Next button to save the app settings:

saml8

    13) When asked “Are you a customer or partner? on the final set up screen pick “I’m an Okta customer adding an internal app “, and press Finish. The app is now created.
    14) Next, navigate to the Sign On tab and save the “Identity Provider metadata” URL. To do this, right-click on the “Identity Provider metadata” link shown below the “View Setup Instructions” button and select “copy Link Address” from the options.

saml10

    15) You can now add users or entire groups via the “Assignments” tab. Any users added will now see the Litmus app within their Okta dashboard.

saml11

    16) Log out from Okta (you will want to test with a non-admin user in a moment) and head back to the SAML settings page in Litmus (subaccounts/security/SAML)
    17) Paste the “Identity Provider metadata” URL (from step 15) into the “Metadata URL” field.

saml12

    18) Finish by clicking the “Save SAML settings” button.

Single sign-on will now be enabled. Any users of the Litmus account can now login in via the Litmus application within their Okta Apps view.

If “Force sign in with SAML” is also activated any users who try to log in via the Litmus Log in screen will be taken to Okta to authenticate, and then redirected to Litmus upon a successful login.

The post Setting up SAML/SSO with Okta appeared first on Help – Litmus.

]]>
https://litmus.com/help/products/setting-up-samlsso-with-okta/feed/ 0