SOLVED

Yammer Embed Problem

%3CLINGO-SUB%20id%3D%22lingo-sub-4782%22%20slang%3D%22en-US%22%3EYammer%20Embed%20Problem%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4782%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EHi%20folks%2C%20I%20am%20out%20of%20ideas%20with%20a%20Yammer%20Embed%20Problem.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3EWe%20are%20using%20Yammer%20Embed%20since%20about%202%20years%20without%20any%20problems%20within%20our%20internal%20Intranet%20Wordpress%20Website.%20We%20just%20created%20a%20Wordpress%20Page%2C%20and%20inserted%20the%20code%20for%20%22Specified%20Feed%22%20we%20got%20from%20here%3A%20%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdeveloper.yammer.com%2Fdocs%2Fembed%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdeveloper.yammer.com%2Fdocs%2Fembed%3C%2FA%3E%3CBR%20%2F%3E%3CSPAN%3EThis%20worked%20flawlessly%20for%20us.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3ESince%20about%20a%20few%20days%20or%20weeks%2C%20IE%20throws%20the%20error%20message%20%22%3CSTRONG%3EThis%20content%20could%20not%20be%20displayed%20in%20a%20frame%3C%2FSTRONG%3E%22%20at%20our%20users%2C%20if%20they%20are%20not%20logged%20in%20or%20deleted%20their%20yammer%20cookies.%20Normally%2C%20it%20showed%20us%20the%20Yammer%20%22Login%22%20Button.%20IF%20they%20login%20to%20Yammer%2C%20the%20feed%20shows%20itself%20just%20fine.%20It's%20just%20the%20login%20part%20which%20throws%20the%20error.%20%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3EWe%20already%20made%20sure%20to%20add%20the%20following%20URLs%20to%20the%20Trusted%20Sites%20Zone%3A%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E--%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E*.assets-yammer.com%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E*.sharepoint.com%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E*.yammer.com%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3Elogin.microsoftonline.com%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E--%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3EWe%20also%20tried%20to%20enable%2Fdisable%20Protected%20Mode%2C%20but%20no%20luck%20with%20that.%20So%2C%20I%20am%20out%20of%20ideas%20now.%20Can%20anyone%20figure%20out%20why%20the%20login%20part%20seem%20to%20be%20not%20embeddable%20any%20more%3F%20%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3EI%20have%20attached%20several%20screenshots%20to%20show%20our%20configs..%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-4782%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EBugs%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EYammer%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-140283%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20Problem%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-140283%22%20slang%3D%22en-US%22%3E%3CP%3EDid%20you%20include%20the%20top%20part%20of%20the%20script%3F%26nbsp%3B%20The%20part%20that%20references%20the%20.js%20file%20hosted%20by%20Yammer.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-140219%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20Problem%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-140219%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20getting%20an%20error%20%22yam%20is%20not%20defined%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-55952%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20Problem%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-55952%22%20slang%3D%22en-US%22%3E%3CP%3E1.)%20%26nbsp%3BNot%20sure.%20%26nbsp%3BI've%20always%20set%20the%20Use_SSO%20%26nbsp%3Bto%20True.%20%26nbsp%3BI'm%20pretty%20sure%20with%20O365%20logons%20it's%20the%20best%20way%20to%20go.%20%26nbsp%3BMy%20wild%20guess%20is%20that%20Chrome%20and%20FireFox%20seem%20to%20be%20less%20strict%20with%20how%20the%20browser%20%22should%22%20function%2C%20whereas%20the%20MS%20browsers%20are%20more%20likely%20to%20follow%20exact%20instructions%2C%20with%20the%20result%20of%20when%20things%20are%20misconfigured%2C%20Chrome%20sometimes%20ignores%20the%20error%20while%20Edge%20or%20IE%20will%20stop.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2.)%20%26nbsp%3BUnfortunate%2C%20yes%2C%20but%20such%20is%20the%20nature%20of%20cloud%20computing.%20%26nbsp%3BHave%20you%20had%20much%20experience%20with%20your%20application%20breaking%2C%20or%20is%20this%20more%20of%20a%20theoretical%20problem%3F%20%26nbsp%3BPersonally%20I%20have%20never%20had%20a%20problem%20with%20an%20embed%20once%20I've%20configured%20it.%20%26nbsp%3BThere%20is%20some%20loss%20of%20functionality%20as%20compared%20with%20the%20full%20product%20through%20the%20browser%2C%20but%20I've%20never%20had%20anything%20break.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESorry%20for%20the%20delayed%20response%20-%20just%20saw%20this%20today.%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-55060%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20Problem%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-55060%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3BWe%20are%20getting%20same%20error.%20%26nbsp%3BWe%20have%20Okta%20in%20place%20for%20authentication%20for%20O365%20and%20just%20recently%20enabled%20IWA.%20%26nbsp%3BI%20thought%20that%20would%20solve%20it%20but%20still%20getting%20the%20error.%20%26nbsp%3BAny%20ideas%3F%20%26nbsp%3BAuto%20login%20for%20embedded%20feeds%20did%20work%20prior%20to%20having%20Okta%20in%20place.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-14002%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20Problem%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-14002%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Tom%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20also%20have%20experienced%20such%20stability%20issues%20where%20the%20yammer%20widget%20stops%20showing%20up%20the%20activity%20feeds%20and%20instead%20displays%20the%20login%20screen.%20This%20happened%20only%20for%20the%20edge%20browser%20and%20it%20worked%20as%20expected%20on%20chrome%20and%20firefox.%26nbsp%3BIn%20our%20recent%20troubleshooting%20effort%20we%20have%20realized%20that%20turning%20on%20the%20%22use_sso%22%20config%20flag%2C%20the%20widget%20worked%20fine%20on%20the%20edge%20browser%20too.%20I%20have%20a%20couple%20of%20questions%20related%20to%20this%3C%2FP%3E%3CP%3E1.%20What%20could%20be%20the%20reason%20why%20%22use_sso%22%20config%20is%20required%20%3CSTRONG%3Ejust%3C%2FSTRONG%3E%20for%20the%20edge%20browser%3F%3C%2FP%3E%3CP%3E2.%20How%20could%20our%20application%20be%20more%20independent%20to%20the%20developments%20to%20the%20%22platform_embed.js%22%20library%3F%20The%20javascript%20library%20is%20not%20versioned%20hence%20any%20change%20that%20breaks%20the%20functionality%20does%20affect%20our%20application.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKindly%20let%20me%20know%20your%20thoughts.%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4991%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20Problem%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4991%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20pleasure%2C%20and%20glad%20it's%20working%20for%20you%20now.%26nbsp%3B%20%3A)%3C%2Fimg%3E%26nbsp%3B%20Thanks%20for%20taking%20the%20time%20to%20follow%20up.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4985%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20Problem%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4985%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20no%20idea%20why%20my%20answer%20got%20deleted%3F%20%3A%5C%3C%2Fimg%3E%26nbsp%3B%3C%2FP%3E%3CP%3EReposting...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-----%3C%2FP%3E%3CP%3EHi%20Tom%2C%20thank%20you%20for%20taking%20some%20time%20to%20help%20us.%20We%20did%20not%20change%20anything%20in%20our%20authentication%20setup%2C%20neither%20yammer%20or%20O365.%20It%20just%20suddenly%20stopped%20working%20for%20us%20last%20week%2C%20without%20any%20changes%20from%20our%20side.%3CBR%20%2F%3E%3CBR%20%2F%3EAs%20we%20are%20speaking%2C%20it%20seems%20to%20work%20again.%20Again%2C%20we%20did%20nothing%20to%20fix%20this%20error%20on%20our%20client%20PCs%2C%20but%20since%20today%20the%20error%20suddenly%20disappeared%20on%20all%20of%20our%20client%20PCs.%20So%2C%20I%20guess%2C%20maybe%20it%20was%20a%20Microsoft%20intern%20trying%20to%20screw%20up%20some%20authentication%20things.%20No%20idea.%3CBR%20%2F%3E%3CBR%20%2F%3ENevertheless%2C%20thank%20you%20for%20trying%20to%20find%20a%20solution.%20Much%20appreciated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4940%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20Problem%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4940%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Tom%2C%20thank%20you%20for%20taking%20some%20time%20to%20help%20us.%20We%20did%20not%20change%20anything%20in%20our%20authentication%20setup%2C%20neither%20yammer%20or%20O365.%20It%20just%20suddenly%20stopped%20working%20for%20us%20last%20week%2C%20without%20any%20changes%20from%20our%20side.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20we%20are%20speaking%2C%20it%20seems%20to%20work%20again.%20We%20did%20nothing%20to%20fix%20this%20error%20on%20our%20client%20PCs%2C%20but%20since%20today%20the%20error%20suddenly%20disappeared%20on%20all%20of%20our%20client%20PCs.%20So%2C%20I%20guess%2C%20maybe%26nbsp%3Bit%20was%26nbsp%3Ba%26nbsp%3BMicrosoft%20intern%26nbsp%3Btrying%20to%20screw%20up%20some%20authentication%20things.%20No%20idea.%20FYI%2C%20it%20looks%20like%20there%26nbsp%3Bwere%20other%20companies%20affected%2C%20too.%20See%20here.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENevertheless%2C%20thank%20you%20for%20trying%20to%20find%20a%20solution.%20Much%20appreciated.%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4836%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20Problem%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4836%22%20slang%3D%22en-US%22%3E%3CP%3EAlso%2C%20try%20to%20add%20a%20config%20section%20your%20script%20and%20add%20an%20SSO%20True%20setting.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3E%26lt%3Bscript%20type%3D%22text%2Fjavascript%22%20src%3D%22https%3A%2F%2Fc64.assets-yammer.com%2Fassets%2Fplatform_embed.js%22%26gt%3B%0A%26lt%3B%2Fscript%26gt%3B%0A%0A%26lt%3Bdiv%20id%3D%22embedded-feed%22%20style%3D%22height%3A700px%3Bwidth%3A500px%3B%22%26gt%3B%0A%26lt%3B%2Fdiv%26gt%3B%0A%0A%26lt%3Bscript%26gt%3B%0A%20%20%20%20%20yam.connect.embedFeed(%7Bcontainer%3A%20'%23embedded-feed'%0A%20%20%20%20%20%20%20%20%2C%20network%3A%20'%26lt%3Bnetwork%26gt%3B'%0A%20%20%20%20%20%20%20%20%2C%20feedType%3A%20'group'%0A%20%20%20%20%20%20%20%20%2C%20feedId%3A%20'%26lt%3Bgroupnumber%26gt%3B'%0A%20%20%20%20%20%20%20%20%2C%20config%3A%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20use_sso%3A%20true%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%2C%20header%3A%20false%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%2C%20footer%3A%20false%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%2C%20showOpenGraphPreview%3A%20false%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%2C%20defaultToCanonical%3A%20false%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%2C%20hideNetworkName%3A%20false%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%2C%20defaultGroupId%3A%20'%26lt%3Bgroupnumber%26gt%3B'%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%7D)%3B%0A%26lt%3B%2Fscript%26gt%3B%3C%2FPRE%3E%3CP%3EYou%20can%20alter%20your%20parameters%20with%20what%20I%20like%20to%20call%20the%20Yammer%20Embedomatic%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.yammer.com%2Fwidget%2Fconfigure%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.yammer.com%2Fwidget%2Fconfigure%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20report%20back%20to%20let%20us%20know%20how%20it%20works.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4835%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20Problem%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4835%22%20slang%3D%22en-US%22%3E%3CP%3EDid%20your%20administrator%20recently%20change%20your%20authentication%20setup%20for%20Yammer%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi folks, I am out of ideas with a Yammer Embed Problem.

We are using Yammer Embed since about 2 years without any problems within our internal Intranet Wordpress Website. We just created a Wordpress Page, and inserted the code for "Specified Feed" we got from here: https://developer.yammer.com/docs/embed
This worked flawlessly for us.

Since about a few days or weeks, IE throws the error message "This content could not be displayed in a frame" at our users, if they are not logged in or deleted their yammer cookies. Normally, it showed us the Yammer "Login" Button. IF they login to Yammer, the feed shows itself just fine. It's just the login part which throws the error.

We already made sure to add the following URLs to the Trusted Sites Zone:
--
*.assets-yammer.com
*.sharepoint.com
*.yammer.com
login.microsoftonline.com
--
We also tried to enable/disable Protected Mode, but no luck with that. So, I am out of ideas now. Can anyone figure out why the login part seem to be not embeddable any more?

I have attached several screenshots to show our configs..

10 Replies

Did your administrator recently change your authentication setup for Yammer?

Also, try to add a config section your script and add an SSO True setting. 

 

<script type="text/javascript" src="https://c64.assets-yammer.com/assets/platform_embed.js">
</script>

<div id="embedded-feed" style="height:700px;width:500px;">
</div>

<script>
     yam.connect.embedFeed({container: '#embedded-feed'
        , network: '<network>'
        , feedType: 'group'
        , feedId: '<groupnumber>'
        , config: {
             use_sso: true
             , header: false
             , footer: false
             , showOpenGraphPreview: false
             , defaultToCanonical: false
             , hideNetworkName: false
             , defaultGroupId: '<groupnumber>'
        }
    });
</script>

You can alter your parameters with what I like to call the Yammer Embedomatic:

 

 

https://www.yammer.com/widget/configure

 

Please report back to let us know how it works. 

Best Response confirmed by Marco Hinniger (New Contributor)
Solution

Hi Tom, thank you for taking some time to help us. We did not change anything in our authentication setup, neither yammer or O365. It just suddenly stopped working for us last week, without any changes from our side. 

 

As we are speaking, it seems to work again. We did nothing to fix this error on our client PCs, but since today the error suddenly disappeared on all of our client PCs. So, I guess, maybe it was a Microsoft intern trying to screw up some authentication things. No idea. FYI, it looks like there were other companies affected, too. See here.

 

Nevertheless, thank you for trying to find a solution. Much appreciated. :)

Best Response confirmed by Marco Hinniger (New Contributor)
Solution

I have no idea why my answer got deleted? :\ 

Reposting...

 

-----

Hi Tom, thank you for taking some time to help us. We did not change anything in our authentication setup, neither yammer or O365. It just suddenly stopped working for us last week, without any changes from our side.

As we are speaking, it seems to work again. Again, we did nothing to fix this error on our client PCs, but since today the error suddenly disappeared on all of our client PCs. So, I guess, maybe it was a Microsoft intern trying to screw up some authentication things. No idea.

Nevertheless, thank you for trying to find a solution. Much appreciated.

 

My pleasure, and glad it's working for you now.  :)  Thanks for taking the time to follow up.

Hi Tom,

 

We also have experienced such stability issues where the yammer widget stops showing up the activity feeds and instead displays the login screen. This happened only for the edge browser and it worked as expected on chrome and firefox. In our recent troubleshooting effort we have realized that turning on the "use_sso" config flag, the widget worked fine on the edge browser too. I have a couple of questions related to this

1. What could be the reason why "use_sso" config is required just for the edge browser?

2. How could our application be more independent to the developments to the "platform_embed.js" library? The javascript library is not versioned hence any change that breaks the functionality does affect our application.

 

Kindly let me know your thoughts.

Thanks!

 We are getting same error.  We have Okta in place for authentication for O365 and just recently enabled IWA.  I thought that would solve it but still getting the error.  Any ideas?  Auto login for embedded feeds did work prior to having Okta in place.

1.)  Not sure.  I've always set the Use_SSO  to True.  I'm pretty sure with O365 logons it's the best way to go.  My wild guess is that Chrome and FireFox seem to be less strict with how the browser "should" function, whereas the MS browsers are more likely to follow exact instructions, with the result of when things are misconfigured, Chrome sometimes ignores the error while Edge or IE will stop.  

 

2.)  Unfortunate, yes, but such is the nature of cloud computing.  Have you had much experience with your application breaking, or is this more of a theoretical problem?  Personally I have never had a problem with an embed once I've configured it.  There is some loss of functionality as compared with the full product through the browser, but I've never had anything break.

 

Sorry for the delayed response - just saw this today.  

I am getting an error "yam is not defined"

Did you include the top part of the script?  The part that references the .js file hosted by Yammer.