How it Works
Web Hosting on Active Directory or Novell eDirectory
Pointspin™ enables users and groups to publish and host Websites from the confines of their server-based network storage. With Pointspin, the process is as simple as a user placing Website content in a designated folder. Once placed in the folder, the new or updated Web content is published immediately.
Pointspin authenticates to the network directory service (Microsoft Active Directory or Novell eDirectory) and the associated network file system through a proxy account. Once authenticated, Pointspin is able to access any Website content to be published in the PUBLIC_HTML subfolder in a user’s or group’s home folder, or a manually assigned folder of a group. If Web content resides in the subfolder, the Pointspin Engine serves it up by assigning a URL based on the Webserver name and user home folder or group home folder name. For example, the URL for Web content located in a user home folder would be: http://www.domainname/~username.
If the user or group wants to restrict access to the Website, access rules are established using a PSAccess file where users and credentials are established.
Product Demo Videos
Tired of reading? Check out our videos!
Want to try Pointspin out?
Just fill out a request and we will send you a 30-day license and the software.Yes, I do!
Will Pointspin™ provide the web publishing capabilities w/in Novell Open Enterprise Server that were available in mod_edir?
Absolutely! One of the principle reasons we developed Pointspin was to address the absence of a web publishing tool in Novell Open Enterprise Server. We’re certain that former mod-edir users will be pleased with this product.
When web content is added to a designated subfolder, the Pointspin Engine serves it up by assigning a URL based on the webserver name and user home folder or group home folder name. For example, the URL for web content located in a user home folder would be: http://www.domainname/~username.
All administration work takes place in a web browser based administration interface. Much of the administrative work pertains to initial setup and configuration and once established, requires no follow-up administration. The minimalistic administrative work combined with the ability to automatically publish websites make Pointspin a product that is very cost-effective to manage.
Does Pointspin have measures in place for preventing the publication or download of copyrighted materials from our websites?
Pointspin provides a Content Management utility through the web interface. Here, an administrator can block Pointspin from serving files with a provided file extension (.mp3, .swf, etc.). This is on a domain-wide basis, not an individual basis. Lastly, content types over a certain size (in megabytes) can also be blocked in the administrative web interface.
The Pointspin Engine includes a proprietary web server that Condrey Corporation first introduced in 2005 with its Kanaka for eDirectory product. Since its initial release, the web server has continued to be enhanced in its features and performance. Thousands of Condrey Corporation customers utilize this web server every day.
How does Pointspin utilize the identity information stored in Microsoft Active Directory or Novell eDirectory?
Pointspin looks for the requested username in the directory service index and serves the website out of the proper folder.
Yes you can. In fact, we recommend that you do so to support high loads or to support the various differences in Pointspin publication settings among the users in an organization.
In addition to serving web content from a subfolder of a user home folder, from where else can Pointspin serve web content?
When configured properly, web content can automatically serve web content located in subfolders of:
- User home folders
- Group home folders
- Auxiliary Storage (created and managed using File System Factory for AD)
- Personal folders located in group home folders
- Manual storage
The client/server data is sent via industry-standard HTTPS, and the Pointspin server rejects HTTP POST requests except in the password-protected administrator page (meaning a client cannot send arbitrary data to the server; it can only receive data from the server).
Can some web pages be accessible only through a username and password, while allowing other to be fully accessible?
Of course. Through the administrative interface, a network administrator can establish settings that require that a valid username and password to access the web content. If these settings are not specified, the web site by default, is accessible to everyone.
If we already have an Apache web server or Microsoft IIS web server, can those work in conjunction with the Pointspin Engine?
Yes, if different ports are used for Pointspin and the other server software. However, we strongly recommend a dedicated server for Pointspin.
From a single class, is it possible to prevent some students from publishing web content while allowing others to publish?
Using the administrative interface, Pointspin allows you to disable specific users and groups from publishing.