LinkedIn shown in Minicard


We have just been upgraded to Super Office ver. 8.0 on-premise version.
Before I had created in Gui-Web panel so I could select a contact and then the contact was automatically found in Linkedin in the mini map.
After the upgrade, I have had problems with this, ie I still Linkedin in mini map, but it no longer seeks the contact appear automatically. It looks like Linkedin has been a change in the query string as the URL that comes if I seek switch up directly in Linkedin, looks different than before, but I can not get the new work, so hope there is someone who can help :)

25 Jan 2017 | 12:00 AM

All Replies (9)

I know, but you found out that your link still works, but SuperOffice don't show it.

Is the protocol https, I think it needs to be secure to work.

Can we see how you do it? What is the URL you are using?

25 Jan 2017 | 12:00 AM

Hi Martin,
I did and it works, but would prefer to have it inside the mini card and not in another tab (as i get via Navigator button and tool bar)

25 Jan 2017 | 12:00 AM

Not the answer but a hint: Try to add the status bar to the mini card, in that way you can open the URL in a separate browser and examine it and maybe change it so that it works.

25 Jan 2017 | 12:00 AM

Hi Peter,

Thank you for the URL, it works when you open in a separate window, but the mini-panel stays empty? Is that the behaviour you get?

1 Feb 2017 | 12:00 AM

Hi Martin,
The URL is:<atfn>/<atln>

1 Feb 2017 | 12:00 AM

I get an error message in the mini card that the HTTPS server does not allow the content to be shown within a frame. If I open it in a new windows, it works fine. Can this be related to a security setting on the LinkedIn site?

3 Feb 2017 | 12:00 AM

LinkedIn is shown in the mini card but the data on the marked person is not shown.
So i need to typåe the name manually.

3 Feb 2017 | 12:00 AM

An old thread, but, this is more relevant now I think.

In attempting to mimick this (SO 9.2), it seems as Linkedin has become far more restrictive.  (also running this in chrome); It seems as if 'anything' running inside an iframe is a no-go, and variations what is called in web URL, and variations in the contact card itself, will, when 'show in separate window' cause an error.

(variations are over /in, with a known connection, as well as a firstname, lastname variable used.



Is this now something that is no longer possible in any variation, or has anyone successfully set this up recently.



29 Jun 2021 | 12:00 AM

Hi Eirik,

There is nothing we can do when sites decide to use X-Frame-Options or Content-Security-Policy to stop their site from being hosted in a frame, iframe, embed or object tag. 

It looks like linkedin is doing that.

Best regards.


30 Jun 2021 | 12:00 AM

Add reply