Loading Captivate HTML5 content into SharePoint

[whold90]

I am having trouble loading my Captivate projects because the Captivate generated json files are being rejected by Sharepoint. How do I get around this? I have seen some suggestions that you change the json files to js files, but that doesn't work for me.

[RodWard · Accepted solution]

Your SharePoint server will need to be configured to allow the JSON mimetype.  Changing the JSON files to JS after each publish is NOT going to be a viable long-term solution.  Talk to your SharePoint administrator.

[whold90]

Hi Rod,

I have talked to them, it's the military and they are not interested in

doing anything to change their configurations. It's their way or the

highway.

Thanks for the information,

Bill

[Lance_Treloar]

Just had a call from a former client (financial services) and they are having the same problem with SharePoint.
SharePoint Administrators will not enable .json files as they perceive integrity issues. Edits need to be made to files made in Captivate 9 - what should have been simple edits is now looking like complete re-works required.
Any other suggestions/possible solutions?

[RodWard]

That is just crazy.  Why would they see "integrity issues" with JSON and not with JS?

JSON stands for JavaScript Object Notation.  It's simply a data agnostic data interchange format that is easier for humans to read and write. It is based on a subset of the JavaScript Programming Language, Standard ECMA-262 3rd Edition - December 1999.

If they allow JS, there's really no reason NOT to allow JSON.  It's not any riskier than having JS.

[whold90]

Hi Rod,

My customer is the US DOD and they don't need reason to make a decision, only somebody's opinion. They read somewhere that the JSON files are a security risk and once that specter is raised, they will not deviate from that position, right or wrong.

I talked to Adobe development concerning the JSON problem and Widget issues. They frankly don't care that the JSON files are a problem. I suggested a software switch that would allow for JSON creation or leaving the various contents in a natural state. They felt that was my problem not theirs. To avoid the JSON problem compile your Captivate training modules in Captivate 9.1. It does not create JSON files. It leaves the various jpg, png and other display files in their native form.

You can see the differences in the dr directory of the compiled output.

[RodWard]

Ah well...I see your problem.  I've always believed that the term Military Intelligence was an oxymoron.  Refreshing to hear though that at least they seem to be able to read.  But if that IS the case then we might likely expect them to one day also ban the use of JavaScript because it is also not without potential security issues.

3 Ways JavaScript Can Breach Your Privacy & Security

It's long been touted that the major reason for ditching SWF was that it was too easy to hack and created security issues.  But one of the biggest 'elephants in the room' in all of this discussion is the mistaken belief that JavaScript is inherently more secure than ActionScript.  Both languages are based on the same ECMASCRIPT standard.  ActionScript is more powerful (in my opinion), but that doesn't mean JavaScript is immune to being used by hackers for nefarious purposes.  They have been misusing it since the internet was invented.

So NOT allowing JSON is really a bit of a double-standard.

[whold90]

I think you're being kind, but I believe that JS is in their sights. I,

unfortunately, am a cynic and expect that they will find unacceptable

security problems with JS.

However, my approach is to bypass existing restrictions to create a

workable solution for my customer. Therefore, I feel that to bypass JSON

restrictions, you must go back to Captivate 9.1. This solution

unnecessarily eliminates the benefits of Captivate 9.2 and Captivate 2017,

but it does eliminate the JSON problem. I am working directly with Govt.

personnel to determine if SharePoint 2013 implementation eliminates JSON

file restrictions. I will let the forum know once I get a definitive

answer. I was told that SharePoint 2010 restricted JSON files, but the

SharePoint 2013 deployment may eliminate this restriction. I have no idea

why or the rational behind this possible change.

I talked to Adobe Captivate Development many times in early 2017 and found

that their priorities were definitely not compatible with mine. I cited two

of my problems to them, JSON security incompatibilities and Widget fixes,

none of the problems I cited were fixed by Adobe in Captivate 2017. So much

for my ability to affect a change to Captivate future technology.

[Lance_Treloar]

Thanks Rod - will pass that information along in the hope that they can convince the Admins (slight hope - as whold90 stated, they don't need reasons, just opinions - but worth a shot).

I suggested they roll back to their earlier version to make their updates, but have been told that this is not possible. Will also pass on the possibility that SharePoint 2013 may solve the issue (thanks whold90 - understand this is unconfirmed, but something they can look into)

[whold90]

The problem with the solution is getting SharePoint administrators to change.