This content has been marked as final. Show 8 replies
Since the RoboHelp output is nothing more than a collection of HTML files and scripts that run inside Framesets, you would secure them in the same manner as you would any other web page. Just password protect the folder they are in. With no credentials, the user shouldn't be able to see them, no?
I'm guessing that as Web developers, you haven't yet been tasked with this generically?
Unfortunatly, it's not that easy. Since the files are raw HTML, they don't go through the same processing as the standard .net pages and thus buy pass any application security that is built into .NET applications. If the RoboHelp files could be exported to .NET pages (such as .aspx) the problem would be solved and we could secure the pages without a problem, but it is my understanding that isn't an option.
We could make the files only accessible via FTP that requires a username/password, but that isn't what our client wants. They want them to be able to use the help files online.
Any other thoughts?
If the parent application is password protected, that's your first line of defense.
If they can make the WebHelp's location somewhat inscrutable, it would be difficult to get there without the help link from the app.
We thought of that, but the client isn't happy with that solution.
The main web site is a Content Management System, that does have password protected pages.
Hi - did you ever find a solution for this? We are looking to do the same thing. Thanks
Sorry... we never found a solution we liked. However, you could write a handler to process all of the HTML pages and grant access, but then you would have to parse the html document for all images and other links to ensure they were secure too, which is why we didn't go with that solution.