One cheap and simple access control to confidential information would be for external links to be used. External to the wiki, but not to your network. Such as a file share where the client specific documentation exists and access controls, such as the usual filesystem/group/user level access controls exist. That way, if someone in the accounting group is reading the wiki, they cannot access Operations/ClientX files, as only the ClientX group can access that information. You could even do what we did at one enterprise I was at, vlan restrict certain larger groups for courser level access control. We had administrators on one vlan, equipment on another, power users on yet another and general users on yet another (with some highly specialized groups also vlan restricted for legal/financial reasons).
The path of least resistance on a labor factor is group share access, with wiki external links to the shared file(s). It would work, it's simple, it's not labor intensive and can quite probably capitalize upon existing data structure. On 8/9/13 11:10 PM, Pierre Labrecque wrote: > Hello, > > > > (sorry for my poor English.) > > > > This is probably a recurring question. > > > > I work for an IT company of around 80 000 employees and we would like to > build an enterprise wiki, where we will put all our technical documentation > (how to, troubleshooting, scripting, etc.). > > 80 000 employees, but this wiki will be for 1000 of them. It may generate a > minimum of 200 000/300 000 pages + images + etc. > > > > You have to know that in some of our documentation, we have usernames and > passwords, or maybe firewall configuration, etc. for different customers. > > Of course, I know that Mediawiki cannot provide a per page/category security > (at a read level): my understanding is that Mediawiki is "Read all pages" or > "Access denied to all pages". nothing in between. So we cannot restrict view > of some documents to a specific group. > > Fine. > > > > So let's say that it's not a problem and that all our technicians will be > able to read all the technical documents, of all our customers. > > > Someone told me that we just don't have to put some confidential > informations in our wiki documents (no user/password/confidential > config/etc.). > > Fine. But where ? If we don't put them in the wiki pages, it means that the > users will have to go in the wiki for the basic informations, then go on > another tool to have the confidential info. > > > > Now, my question: how do you manage this ? > > I really love Mediawiki and would like to implement it in our business, but > I haven't enough information on how this can be implemented in the reality > of a business. > > And no: no budget to buy something like Confluence. > > I have try Dokuwiki, XWiki, Tiki, MoinMoin, many others. I love Dokuwiki > too, but wasn't sure enough it was a strong tool to be able to manage that > amount of pages/images/. Anyway, I always come back to MediaWiki. I don't > know why. > > > > Best regards, > > > > Pierre > > > > _______________________________________________ > MediaWiki-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/mediawiki-l _______________________________________________ MediaWiki-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
