Flash Player 8 and its new Security Model

This is going to be a major topic of discussion for the next several weeks, so hopefully here, among other places, we’ll have some solid answers to questions on how to best work with Flash Player 8 and your SCORM-conformant projects.

Josh wrote on the [ADL Forums](http://www.adlnet.org/forums/messageview.cfm?threadid=2311&catid=70&messid=92480&forumid=2):

>My concern about the new security model is more based on the fact that I cannot test my SCORM courses for compliancy using the SCORM conformance test suite. I have a Flash course that communicates to the API wrapper using the Flash/Javascript Integration Kit. The Test Suite requires that it test a course that is running on the local file system, which is now restricted by Macromedia from making Javascript calls from Flash.
>When my course is running on a server, I can make all the JS to Flash calls I need, but if the course is running from the file system, I can’t make any if I use the Flash 8 plugin. So, I’m stuck in a cyclical bind where my courses work from a server, but I can’t test them in the Test Suite to verify that they are conformant.
>Does anybody know of a workaround for this?

My short answer is to downgrade the Flash Player to 7.0.19 to test your Flash 7 and below content, but that doesn’t necessarily undo the problems that a learner might have with the Flash Player 8 installed and the potential for your content to break.

Please comment here or in the ADL Forums to discuss this further…

flash, security, scorm, flash player, macromedia, e-learning, development, javascript

2 replies on “Flash Player 8 and its new Security Model”