Welcome to blog series part 6 of 17 on migrating Notes apps to DOCOVA. In this entry I’m going to talk about three things. Security, security and security.
We thought the security in Notes/Domino was pretty good. It was clear, easy to manage and provided for a lot of variable implementation. DOCOVA’s enhanced security capabilities were made so that it is flexible enough to support the Notes/Domino approach to security.
DOCOVA application access control is handled similarly to Notes database ACLs. They are managed through the UI of the DOCOVA App Builder integrated development environment (yes, all browser based) in the Properties of an application. People, groups and roles can be added and created in the access control of an application and specific functionality can be assigned like the ability to delete documents/records and more.
DOCOVA also supports Authors and Readers fields and yes, in conjunction with the access control of the application, similar to how Notes/Domino did. Additionally, things like controlled access sections and document modes like read mode and edit mode are also supported.
From a directory/address book perspective, DOCOVA connects to Address Books and Directories via LDAP for things like authentication. For DOCOVA instances that are on non-Domino platforms, DOCOVA allows for the creation of its own self-contained Directory which can be used to manage users and authentication services. What’s cool is that both internal directories and the DOCOVA directory can be used simultaneously to do things like manage internal staff in your own internal directories like Active Directory while managing external users via DOCOVA’s directory.
You can fast-track and get all the whitepapers on our migration methodology and everything that is being discussed in this series of posts. Specifically, you can get the DOCOVA Notes/Domino Migration Methodology – MIGRATE whitepaper which goes over these technical aspects.
If you have any questions or comments, post ’em below.