Need to get my UBB Classic to recognize my web sites members when they login so they do not have to login to both the web site and the UBB. Infopop provided the following information on how to do this. You can contact me at butchgr@snowhill.com

Thanks

Butch

Regarding the membership integration you're talking about, it is possible with the UBB.classic, but it does require some manual labor on your part. I have a very long, detailed document on our 'recommeneded' method of integration. I'll paste it here, but I can also email it to you if you prefer.

Thanks!

Here are the Cliff's Notes on how to integrate the ubb with your existing site:
The UBB uses Flat-text files for it's Member data, thus, when anyone "Registers" on your site, the existing routine could be altered to include a subroutine for member registration on the UBB as well.

Effectively what you will do is this:
Once the user registers on your site this sub-routine will
1) create the Member file as above with the structure as shown
2) Add the appropriate line in the memberslist.cgi file
3) Add the appropriate line in the emailfile.cgi file
4) Add the appropriate line to the public_names.cgi file
5) Increment the last_number.cgi file
6) Increment the membertotal.cgi file

One major difference on the above file is that they all have a .cgi extension so that any browser cannot view the contents.

Here are those steps enumerated and expanded upon.

1) create the Member file as above with this structure:

1 User name
2 Password
3 Email Address
4 URL
5 Permissions Line (Write&)
6 Occupation
7 Location
8 Post count
9 Status (Admin|Mod|Member)
10 Interests
11 Reg Date (YYYY-MM-DD)
12 Email View (yes|no)
13 Signature
14 ICQ UIN
15 Allow Mass Mail (yes|no)
16 Public Display Name
17 Custom Field 1
18 Custom Field 2
19 Custom Field 3
20 Custom Field 4
21 Picture URL
22 DaysPrune
23 AIM ID
24 Last edit information
25 Profile locked? (yes|no)
26 Allow User Ratings (yes|no)
27 Awaiting Moderation Queue? (yes|no)
28 Allow Incoming PMs? (yes|no)
29 Notify on email on PM? (yes|no)
30 Admin allows to SEND PMs? (yes|no)
31 Last Post Information (forum|thread|post|YYYY-MM-DD)
32 Admin-assigned user title
33 Reserved for Infopop Corporation use at a later date
34 Reserved for Infopop Corporation use at a later date
35 Reserved for Infopop Corporation use at a later date
36 Reserved for Infopop Corporation use at a later date
37 Reserved for Infopop Corporation use at a later date
38 Reserved for Infopop Corporation use at a later date
39 Reserved for Infopop Corporation use at a later date
40 Reserved for Infopop Corporation use at a later date
41 Reserved for Infopop Corporation use at a later date
42 Reserved for Infopop Corporation use at a later date
43 Reserved for Infopop Corporation use at a later date
44 Reserved for Infopop Corporation use at a later date
45 Reserved for Infopop Corporation use at a later date
46 Reserved for Infopop Corporation use at a later date
47 Reserved for Infopop Corporation use at a later date
48 Reserved for Infopop Corporation use at a later date
49 Reserved for Infopop Corporation use at a later date
50 Reserved for Infopop Corporation use at a later date

*Note* If you would like to add your own fields you may do so, consider adding them AFTER line #50

Next are two text files called memberlist.cgi and emaillist.cgi - these two files serve as 'verification' files for the text files as above and have a simple format.

2) Add the appropriate line in the memberslist.cgi file

bharris|!!|00000002
Nitesh|!!|00000003
Rosemary|!!|00000004
Ted|!!|00000005
Don|!!|00000006
MFaber|!!|00000007
MFarris|!!|00000008
Peter|!!|00000009

Simple pattern - Username - pipe - exclamation - exclamation - pipe - Member file number

3) Add the appropriate line in the emailfile file

Here are a few lines from emailfile.cgi

bharris@infopop.com| |00000002
nitesh@infopop.com| |00000003
rosemary@infopop.com| |00000004
ted@infopop.com| |00000005
donco@infopop.com| |00000006
mike@infopop.com| |00000007
mfarris@infopop.com| |00000008
peter@infopop.com| |00000009

Again, simple pattern.

member e-mail of record- pipe - pipe - Member file number.

4) Add the appropriate line to the publicnames file

bharris
nitesh
rosemary
donco
Kalico

{etc...}

5) Increment the last_number.cgi file

Simply the number of the last member file created.

00000009

6) Increment the membertotal.cgi file.

Just as the name infers, this is only a total of members to display on the board.

7) Increment the last_approved.cgi file.

Just as the name infers, this is the last Member number approved.

To polish the whole illusion off and set the cookies for the user you will use this code within the registration application that sets the cookies:

The UBB uses three cookies for all front end requests.

The cookie names are login, session, and ubber. All names are proceeded
by a Julian date string, a period, and an HHMM string. This information
is created during the UBB's initial setup, and is stored in vars_config.cgi
as $vars_config{Cookie_Number}. This allows for multiple, independant UBBs
on one server without conflicting cookies, as the cookie number would be
different on each board.

All values are URL-escaped. Individual cookie elements are seperated by
ampersands.

For more information on the Julian date format, read chapter six of
Selena Sol's "Instant Web Scripts with CGI/PERL". You can find this
chapter online at http://www.extropia.com/books/instant_web_scripts/chap06.pdf


------------------------------
login2452044.1355=05-25-2001%2010%3A55%20AM&2452055.1055

login2452044.1355 =
05-25-2001 %20 10 %3A 55 %20 AM
2452055.1055

The login cookie contains two elements.
1) A datetime string in the format: MM-DD-YYYY HH:MM (AM|PM)
2) A Julian date string followed by a period and an HHMM string

The login cookie is stored for one year past the set date. It is read
into the session cookie at the beginning of a browser session to control
the new post indicators.

------------------------------
session2452044.1355=05-25-2001%2010%3A55%20AM&2452055.1055

session2452044.1355 =
05-25-2001 %20 10 %3A 55 %20 AM
2452055.1055

The session cookie is the same format as the login cookie. It is a
session based cookie, which expires when the user ends their browser session.

------------------------------
ubber2452044.1355 =
User%20Name&password&Displayname&1000&00000028

ubber2452044.1355 =
User%20Name
password
Displayname
1000
00000028

The ubber cookie stores the user's login information. The fields are:
1) Username
2) Password
3) Displayed name
4) Daysprune value (the number of days the user has selected to view in forums)
5) The usernumber

The ubber cookie is authenticated against the UBB member database on each request.


Regards,


Infopop Corporation