> 1) Can the password type be changed to MD5? Most of our other web
> packages use MD5 for passwords. If so, any idea which files would
> need to be modified. I didn't see a plugin for this.
Boltwire seems to use the PHP crypt function. Here is what I found
about the PHP crypt function:
"Crypt uses standard MD5 encryption but can also use DES or other
encryption as available."
It seems to already use MD5 encryption.
> 2) I assume that an external program could create and update these
> files as long as the format is correct as well as permissions. Right?
Yup. I do that all the time with other things. I recommend tapping
into the boltwire core whenever possible though, and having the
external program be a plugin form command.
> 3) I see that there are stamps versions of files. Not 100% sure how
> to deal with that. I don't know that versions of these files are all
> that important for my purposes.
They can be retrieved by the undo function. People expect it of a
wiki. They are eventually deleted when too old anyway, so if you don't
need them, ignore them.
> I have already built extensive staff management functions in the
> primary websites of sites that might start using the wiki. There are
> also links to the same userid's for email access, and other access
> throughout the sites.
>
> The wiki won't replace the websites, but I would like to create a
> bridge between them and the wiki logins so that management of the
> users remains in the website. I already bridge to other packages doing
> this.
>
> It would be much easier for me to do this externally than trying to
> use the Wiki to do it.
>
> Comments?
The first way that came to mind, is to turn off registration on the
boltwire site, create a synch-function that takes information from the
other site and builds login pages on boltwire with that information.
Put it on cron or build it into the other site. Assuming the same
encrypt method is used, you can then use the same login and password.
If that is not possible, it may be neccesary to override the Boltwire
login function. This is not difficult.
The following code from the login function should be run from a
boltwire session to log in:
global $msg, $BOLTid, $BOLTmember, $BOLTfieldKey;
session_start();
$_SESSION[$BOLTfieldKey]['ID']['id'] = $id;
$_SESSION[$BOLTfieldKey]['ID']['member'] = $member;
session_write_close();
$BOLTid = $id;
$BOLTmember = $member;
$memberships = BOLTFmemberships(Array
('output'=>'true'));
$msg['login_success'] = "~$member";
setcookie('cache', $memberships, time() + 86000);
So if you create a plugin with the following method:
function BOLTXnewlogin($value, $field) {
<extract login name and password from global $BOLTarray>
if( CALL_THE_OTHER_SITES'_LOGIN ) {
<above code>
}
}
You should be able to reuse the login code from your other website.
You bypass regular Boltwire login pages completly, for good and ill.
... My keyboard is about to get thrown out: the keys stick.I hope I
havent made too many typos.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"BoltWire" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---
