GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages


Manual Reference Pages  -  APACHE2::SITECONTROL::USER (3)

.ds Aq ’

NAME

Apache2::SiteControl::User - User representations

    SYNOPSIS



   my $user = Apache2::SiteControl->getCurrentUser($r);

   # $r is the apache request object

   # Checking out the users name:
   if($user->getUsername eq sam) { ... }

   ...

   # Working with attributes (session persistent data)
   my $ssn = $user->getAttribute(ssn);
   $user->setAttribute($r, ssn, 333-555-6666);

   # Removing/invalidating session for the user
   $user->logout($r);



    DESCRIPTION

The SiteControl system has a base concept of a user which includes the user’s name, persistent attributes (which are persistent via session), and support for user logout.

It is assumed that you will be working from mod_perl, and some of the methods require an Apache request object. The request object is used by some methods to coordinate access to the actual session information in the underlying system (for storing attributes and implementing logout).

User objects are created by a factory (by default Apache2::SiteControl::UserFactory), so if you subclass User, you must understand the complete interaction between the factory (which is responsible for interfacing with persistence), the SiteControl, etc.

The default implementation of User and UserFactory use AuthCookie to manage the sessions, and Apache::Session::File to store the various details about a user to disk.

If you are using Apache2::SiteControl::User and Apache::SiteControl::UserFactory (the default and recommended), then you should configure the following parameters in your apache configuration file:



   # This is where the session data files will be stored
   SiteControlSessions directory_name
   # This is where the locks will be stored
   SiteControlLocks directory_name



These two directories should be different, and should be readable and writable by the apache daemon only. They must exist before trying to use SiteControl.

CONTENTS

METHODS

<B>getUsernameB> Get the name that the current user used to log in.
<B>getAttribute($name)B> Get the value of a previously stored attribute. Returns undef is there is no value.
<B>setAttribute($request, B>$name<B>, B>$value<B>)B> Add an attribute (scalar data only) to the current session. The current apache request object is required (in order to figure out the session). Future versions may support more complex storage in the session. This attribute will stay associated with this user until they log out.
<B>logout($request)B> Log the user out. If you do not pass the current apache request, then this method will log an error to the apache error logs, and the user’s session will continue to exist.

SEE ALSO

Apache2::SiteControl::UserFactory, Apache::SiteControl::ManagerFactory, Apache2::SiteControl::PermissionManager, Apache::SiteControl

AUTHOR

This module was written by Tony Kay, <tkay@uoregon.edu>.

COPYRIGHT AND LICENSE

This modules is covered by the GNU public license.
Search for    or go to Top of page |  Section 3 |  Main Index


perl v5.20.3 APACHE2::SITECONTROL::USER (3) 2006-03-17

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.