encrypt documentation
Post here questions and problems related to editing and publishing DITA content.
-
- Posts: 158
- Joined: Fri Nov 10, 2017 8:16 am
encrypt documentation
Hi,
I have published a webhelp by Oxgen XML Editor, I want to know is there any way to encrypt some documentations.
For example, in the webhelp, we have the following types of documentations:
product intro
administrator guide
end user guide
security guide
I want to encrypt "security guide". To view this guide, users need to log in to a third-party platform (for example, our partner portal) by authentication info.
Is that possible?
Thanks
Catherine
I have published a webhelp by Oxgen XML Editor, I want to know is there any way to encrypt some documentations.
For example, in the webhelp, we have the following types of documentations:
product intro
administrator guide
end user guide
security guide
I want to encrypt "security guide". To view this guide, users need to log in to a third-party platform (for example, our partner portal) by authentication info.
Is that possible?
Thanks
Catherine
-
- Site Admin
- Posts: 275
- Joined: Thu Dec 24, 2009 11:21 am
Re: encrypt documentation
Hi Catherine,
Yes, it is possible to secure and restrict access to certain resources, but this is out of scope of the output generated by the WebHelp Responsive plugin. This should be the job of the HTTP server were your output is deployed.
The WebHelp Responsive output is a collection of static resources (HTML, CSS, JS, images, fonts, etc). The HTTP server that 'serves' those resources should decide which have restricted access and which are publicly available.
In conclusion you need to check the documentation of your HTTP server in order to set up authentication and authorization for your resources.
Regards,
Alin
Yes, it is possible to secure and restrict access to certain resources, but this is out of scope of the output generated by the WebHelp Responsive plugin. This should be the job of the HTTP server were your output is deployed.
The WebHelp Responsive output is a collection of static resources (HTML, CSS, JS, images, fonts, etc). The HTTP server that 'serves' those resources should decide which have restricted access and which are publicly available.
In conclusion you need to check the documentation of your HTTP server in order to set up authentication and authorization for your resources.
Regards,
Alin
Alin Balasa
Software Developer
<oXygen/> XML Editor
http://www.oxygenxml.com
Software Developer
<oXygen/> XML Editor
http://www.oxygenxml.com
Return to “DITA (Editing and Publishing DITA Content)”
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service