Yammer (IdP-initiated) Integration Guide
Introduction
Use this guide to enable Multi-Factor Authentication and Single Sign-on (SSO) access via SAML to Yammer.
Prerequisites
1. Have a Yammer account
2. Ensure that SAML SSO is enabled
Contact Yammer's customer support to enable SAML SSO
3. Create a New Realm for the Yammer integration in the SecureAuth IdP Web Admin
4. Configure the following tabs in the Web Admin before configuring the Post Authentication tab:
Overview – the description of the realm and SMTP connections must be defined
Data – an enterprise directory must be integrated with SecureAuth IdP
Workflow – the way in which users will access this application must be defined
Multi-Factor Methods – the Multi-Factor Authentication methods that will be used to access this page (if any) must be defined
SecureAuth IdP Configuration Steps
Data
1. In the Profile Fields section, map the directory field that contains the user's Yammer ID to the SecureAuth IdP Property
For example, add the Yammer ID Field to the Email 2 Property if it is not already contained somewhere else
Warning
Click Save once the configurations have been completed and before leaving the Data page to avoid losing changes
Post Authentication
2. Select SAML 2.0 (IdP Initiated) Assertion Page from the Authenticated User Redirect dropdown in the Post Authentication tab in the Web Admin
3. An unalterable URL will be auto-populated in the Redirect To field, which will append to the domain name and realm number in the address bar (Authorized/SAML20IdPInit.aspx)
4. A customized post authentication page can be uploaded, but it is not required
User ID Mapping
5. Select the SecureAuth IdP Property that corresponds to the directory field that contains the Yammer ID (Email 2)
6. Select urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified from the Name ID Format dropdown (default)
Select a different option if Yammer requires it, which the Service Provider (SP) will provide
7. Select False from the Encode to Base64 dropdown
SAML Assertion / WS Federation
8. Set the WSFed Reply To/SAML Target URL to https://saml.yammer.com
9. Set the SAML Consumer URL to https://saml.yammer.com/sp/ACS.saml2
Note
In typical integrations, this is the SAML Consumer URL and SAML Recipient; confirm with Yammer to ensure correct configuration
10. Set the WSFed/SAML Issuer to a Unique Name that will be shared with Yammer
The WSFed/SAML Issuer must match exactly on the SecureAuth IdP side and the Yammer side
11. Set the SAML Recipient to https://saml.yammer.com/sp/ACS.saml2 (see note above)
12. Set the SAML Audience to yammer.com
13. Set the SAML Offset Minutes to make up for time differences between devices
14. Set the SAML Valid Hours to limit for how long the SAML assertion is valid
Note
No configuration is required for the SP Start URL field
15. Select False from the SubjectConfirmationData Not Before dropdown
16. Leave the Signing Cert Serial Number as the default value, unless there is a third-party certificate being used for the SAML assertion
If using a third-party certificate, click Select Certificate and choose the appropriate certificate
17. Provide the Domain in order to Download the Metadata File to send to Yammer
This will assist Yammer in enabling SSO
Warning
Click Save once the configurations have been completed and before leaving the Post Authentication page to avoid losing changes
Forms Auth / SSO Token
Optionally, in the Forms Auth / SSO Token section, click the View and Configure FormsAuth keys/SSO token link to configure the token/cookie settings and configure this realm for SSO.
Yammer Configuration Steps
Contact Yammer customer support to enable SAML SSO and send the Metadata File from the SecureAuth IdP Web Admin (step 17)