# Re: Recommendations for a Ruby Wiki, preferably with bidi su

**URL:** <https://www.ruby-forum.com/t/re-recommendations-for-a-ruby-wiki-preferably-with-bidi-su/73644>\
**Category:** Ruby\
**Created:** [October 25, 2006, 10:30pm UTC](https://www.ruby-forum.com/t/re-recommendations-for-a-ruby-wiki-preferably-with-bidi-su/73644 "2006-10-25T22:30:42Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![phrogz](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/2acd7d/32.png) [@phrogz](https://www.ruby-forum.com/u/phrogz)\
**Post date:** [October 25, 2006, 10:30pm UTC](https://www.ruby-forum.com/t/re-recommendations-for-a-ruby-wiki-preferably-with-bidi-su/73644/1 "2006-10-25T22:30:42Z")

</div>

From: Bil K. [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)]

> Matt L. wrote:
> 
> > Any suggestion on the best way to add some type of login and  
> > authentication?
> 
> For an internal wiki?! What type of employees do you have?

FWIW, at my company we use OpenWiki internally (with a bunch of  
hacked-on additions). When using IE, it’s very nice that it uses your NT  
login with auto-login as your authenticated user name.

Every edit is associated with a real known user, and the system also  
keeps track of the last time each user viewed a particular page.  
(Helpful to see if someone is making comments on a document but they  
haven’t looked at it in 10 revisions.)

Authentication (for us) is not so much about authorization as it is  
identification.