Launching e-learning courses using Safri browser on a MacOS (running high Sierra)


I am hoping someone can provide some advice/solution to the following issue

When launching our elearnings (from our LMS) using the default safari browser on a MacOS we get a Validation error (Failed to authenticate the SAML response)

The issue does not happen with Google chrome... is there anything that can be done to enable Mac users to launch courses through their safari browser or should we just stipulate users should use Chrome??




3 Replies
Alyssa Gomez

Hi Patricia,

Your learners shouldn't have any issues using the Safari browser, so it sounds like something isn't quite right here.

What version of Storyline did you use to build the content? Also, have you tried testing the content in another environment to see if it opens in Safari there?

If not, my next step would be to host the content in SCORM Cloud, and test the link in Safari to see how it behaves. If you don't mind sharing the unpublished Storyline file with me, I'd be happy to help with that testing!

Patricia de Souza

Hi Alyssa
Thanks for your response... the particular course causing the issue was created using Studio '13. we will shortly be updating this course and will redo it using SL3 so no point spending time and effort on this to work out what is going on

However I have recently been working on a project with SL3 - the project hasnt yet been finalised, however when published to CD or Web format to enable the stakeholders to review before we publish to our LMS, one of my SME's using a Mac, has not been able to launch the project  - it either starts then sits with the "ring of death" trying to load or he gets a "Uncaught DOMException: Failed to read the 'cssRules' property from 'CSSStyleSheet': Cannot access rules" message - we havent yet got to the bottom of this issue!... any advice would be appreciated



Alyssa Gomez

Hi Patricia,

If you want to run the Published for CD output on a Mac, try using the .html file instead of the .exe:

If you still run into trouble, add the folder where the course is located to your local Flash Player Security Settings.

For the content that you Published for Web, try first uploading it to Tempshare before sending the URL to your stakeholders.

I hope that helps sort things out!