Hello Jonathan, How would one get the Visual SVN to log successful logins. >
I guess that by "login" you mean a successful authentication when using a web interface to access the repositories. Right? Subversion clients and VisualSVN Server's web interface (i.e. a web-based client) does not use web-based authentication; the authentication used is HTTP authentication. Every client request gets authenticated by the server and depending on VisualSVN Server edition you have and its settings the authentication mechanism used is either Basic, NTLM or Negotiate (Kerberos or NTLM). Note that HTTP authentication log-on / log-off capabilities are controlled by web browsers and does not depend of the web interface itself. Web browsers does not show special log-on or log-off dialog for such authentication mechanisms. For example, once authenticated over Basic authentication, web browser caches user credentials and you can remove them via web browser's tools / options. If you don't remove them, web browser won't request you to enter username and password again and will use cached credentials unless the password changes. The behavior is different for NTLM and Negotiate authentication mechanisms (they are available if you have Integrated Windows Authentication enabled on VisualSVN Server) because the current Windows credentials are automatically used to access VisualSVN Server; a password itself is never cached on disk and is never transmitted over network. You can read more about authentication mechanisms available in VisualSVN Server in the article KB39: Understanding VisualSVN Server Authentication options <https://www.visualsvn.com/support/topic/00039/>. At this particular time it is only logging the failures to the Windows > event log. > Apart from Subversion repository history which can be considered as a log, VisualSVN Server provides multiple logs that can be viewed through Windows Event Viewer. The log that's only logging the failures is "VisualSVN Server" general log. But there is also VisualSVN Server Activity log that contains access and operational events. For the general reference about VisualSVN Server's logging events, see the feature description at https:// www.visualsvn.com/server/features/logging/. - Operational log of VisualSVN Server provides high-level logging of Subversion activities. For example, you can search VisualSVN Server Activity event log for events with the action log message "checkout-or- export" to determine who exported or checked out a working copy. To learn more about high-level logging, read SVNBook at https://www. visualsvn.com/support/svnbook/serverconfig/operational-logging/ <https://www.visualsvn.com/support/svnbook/serverconfig/operational-logging/> . - Access log of VisualSVN Server provides low-level logging based on HTTP protocol requests. To learn more about low-level access logging, see SVNBook | Apache logging at https://www.visualsvn.com /support/svnbook/serverconfig/httpd/#svn.serverconfig.httpd.extra.logging <https://www.visualsvn.com/support/svnbook/serverconfig/httpd/#svn.serverconfig.httpd.extra.logging> . Here is a brief events sample (for more events check the above links): - Operational events are high-level logging events and they represent logical operations. Their event ID is always 4000. Each operational event has information about what operation was performed. E.g. for commit, the event will say [[ commit r1234 Repository: MyRepository User: MyUser Host: 192.168.1.199 ]] - For working copy update it will say: [[ update / r1234 Repository: MyRepository User: MyUser Host: 192.168.1.199 ]] - For working copy checkout or a simple export it will say: [[ checkout-or-export / r1234 depth=infinity Repository: MyRepository User: MyUser Host: 192.168.1.199 ]] Windows Event Log can be accessed and managed with various programming and scripting languages, e.g. C#, VBScript, Windows PowerShell etc. So you can write a program that will access VisualSVN Server's eventlog to check what operations your users perform. We can recommend using PowerShell for this task. For the reference on the `Get-EventLog` PowerShell cmdlet please see the TechNet article at http://technet.microsoft.com/library/hh849834. -- With best regards, Pavel Lyalyakin VisualSVN Team -- You received this message because you are subscribed to the Google Groups "VisualSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to visualsvn+unsubscr...@googlegroups.com. To post to this group, send email to visualsvn@googlegroups.com. Visit this group at https://groups.google.com/group/visualsvn. For more options, visit https://groups.google.com/d/optout.
