Request Authentication using the Content-Engine

 

Accessing documents often requires user authentication, as the document may contain sensitive information that should not be accessed by an unauthorized person.

 

The IceViewer Content-Engine has no built-in authentication, although it offers multiple ways to authenticate users using SESSIONS or COOKIES.

 

All request that goes through on the Content-Engine receives a ContentEngineInput parameter, that contains all the SESSION variables, and COOKIES, along with the DocumentID.

 

For example, when the user opens a document, the GetPage API will pass each SESSION variable, and all COOKIES along with the DocumentID, which can be processed in the given Content-Engine.

 

Developers can inspect the SESSION and COOKIE values for authentication when creating their own Content-Engine.