Topic: [Announce] Howto install Open-Xchange for SME

[berdie]

I would like to announce a howto for the installation of the collaboration-suite Open-Xchange.

Thanks a lot for Vincent Filali-Ansary, who contributes this brillant work in a few rpm's.

Note: This is for SME 6.01-01 only, it doesn't work for the SME 7 !

http://no.longer.valid/phpwiki/index.php/Howto%20install%20Open-Xchange%20for%20SME%206.01-01

Rgds.

Dietmar

[jmvelez]

all we need now is the tool to create users and group in the server manager and the TB connect for the contacts.

[Franco]

Hi Dietmar,
I followed your How-To and also created a group and a user as this tutorial suggests:
http://e-smith.dyndns.org/ox/

Be careful with usernames and passwords: they should be exactly the same like your users and passwords at the SME-Server!

Do I need to create each of my users by hand?
Is this tutorial incomplete?

[berdie]

Do I need to create each of my users by hand?
Is this tutorial incomplete?

Hi Stuntshell,
at the moment there is no way to create und change the users with a panel in the server-manager. So it's right, you need to create them by hand.
But you could create a little script with all users in it and one line per user. A line of this script should look like this:
/usr/local/open-xchange/sbin/adduser_sme_ox --username="michael" --passwd="sme4711" --name="Michael" --sname="Walter" --maildomain="walter.com" --lang="EN" --ox_timezone="Europe/Berlin" --write_global_address="TRUE" --uid=5100 --gid=5100

Rgds.
Dietmar

[gordonr]

But you could create a little script with all users in it and one line per user. A line of this script should look like this:
/usr/local/open-xchange/sbin/adduser_sme_ox --username="michael" --passwd="sme4711" --name="Michael" --sname="Walter" --maildomain="walter.com" --lang="EN" --ox_timezone="Europe/Berlin" --write_global_address="TRUE" --uid=5100 --gid=5100

If you create a script in /etc/e-smith/events/user-create, it will get called as users are created from the server-manager. The username will be passed as the second argument (the first is the event name). The user-create-unix script is probably a good basis for a user-create-openxchange.

Similarly, if you create a script in /etc/e-smith/events/user-modify, it will get called as users are modified from the server-manager. Your script could check whether the Open-Xchange user exists, and create it if not.

Most of the other data you need is already available as properties of the user in the accounts database. Try "/sbin/e-smith/db accounts show michael" and you'll see you've got almost all that you need.

And finally, link a script into user-delete to handle the deletion case.

[Franco]

Certainly a nice way to integrate Gordonr, but my biggest consideration would be about the existing users and their passwords, and the fact that once they change their password through regular steps it does not reflect on Open-Xchange.
I've been throught these before, with the jabber contrib, proxy-users and chpasswd.cgi.
Thanks,

[gordonr]

Certainly a nice way to integrate Gordonr,

Not just a nice way, it's the SME Server design

but my biggest consideration would be about the existing users and their passwords, and the fact that once they change their password through regular steps it does not reflect on Open-Xchange.
I've been throught these before, with the jabber contrib, proxy-users and chpasswd.cgi.
Thanks,

There is a "password-modify" event which gets called when someone modifies their password. However, it does not currently provide a method by which subsystems can get the unencrypted password, as it is called after the new password has been set in /etc/shadow and /etc/smbpasswd. These passwords are set by library functions which are careful not to pass the password on the command line, or similar.

If these subsystems can use /etc/shadow, /etc/smbpassd, PAM or CVM to authenticate, they don't need to do anything more. I'd be really surprised if you can't use one of those methods to check passwords.

If you really need the password to be available in the password-modify event so it can be hashed into yet another password scheme (I hope not), please raise a bug in the 7.0 SourceForge bug tracker, providing details and we'll have a look at it.

Note that there is no way to recover a user's existing password. That is by design, and an important part of a secure password system. So, existing users will need to reset their password when a new subsystem is added, if that new subsystem needs another password scheme.

Again, I'd be surprised if you couldn't use one of the existing methods to authenticate users against either /etc/shadow or /etc/smbpasswd via PAM or CVM. It's usually just a matter of configuring the subsystems in the correct way.

[vinc28]

Certainly a nice way to integrate Gordonr,

Not just a nice way, it's the SME Server design
yep

but my biggest consideration would be about the existing users and their passwords, and the fact that once they change their password through regular steps it does not reflect on Open-Xchange.
I've been throught these before, with the jabber contrib, proxy-users and chpasswd.cgi.
Thanks,

I have make a automated system to create all the present users in the system, but for the password i make by default the name of the acount.

There is a "password-modify" event which gets called when someone modifies their password. However, it does not currently provide a method by which subsystems can get the unencrypted password, as it is called after the new password has been set in /etc/shadow and /etc/smbpasswd. These passwords are set by library functions and are careful not to pass the password on the command line, or similar.
[/quote]

that right, i have make a ugly modification to the useraccount.pm to send the password with the account name to resolve this.

If these subsystems can use /etc/shadow, /etc/smbpassd, PAM or CVM to authenticate, they don't need to do anything more. I'd be really surprised if you can't use one of those methods to check passwords.

for Openxchange it's use a LDAP {crypt} password for the security.

If you really need the password to be available in the password-modify even so it can be hashed into yet another password scheme (I hope not), please raise a bug in the 7.0 SourceForge bug tracker, providing details and we'll have a look at it.

i think about.

Note that there is no way to recover a user's existing password. That is by design, and an important part of a secure password system. So, existing users will need to reset their password when a new subsystem is added, if that new subsystem needs another password scheme.

that right.

Again, I'd be surprised if you couldn't use one of the existing methods to authenticate users against either /etc/shadow or /etc/smbpasswd via PAM or CVM. It's usually just a matter of configuring the subsystems in the correct way.

for who don't know me, i have made all the rpms for OX.


ps: i going to integrate all OX on sme 7 beta2.

[DarkMirage]

I'd be surprised if you couldn't use one of the existing methods to authenticate users against either /etc/shadow or /etc/smbpasswd via PAM or CVM. It's usually just a matter of configuring the subsystems in the correct way.

Which is the place where some java-knowledge would be nice. I'll look into this, since it is the reason why my efforts on Open-Xchange aren't going anywhere fast.

Speaking of which, vinc28, you might want to take a look at the source rpm of my latest release to see if you're able to use anything...

[vinc28]

on my site you could find the panels intégration of openxchange
it's sme-openexchange-conf



all this work is under heavy beta....


vincent

[berdie]

all this work is under heavy beta....
vincent

...but it goes !!
I have tested it today and I think, this is a brillant work, Vincent!
1. When installing his brandnew rpm, all existing users are also ox_users. For the synchronization of the passwords the users have to recreate their passwords.
2. Creating new SME-users after installing Vincent's rpm brings us also new ox_users. With the first time of creating the passwords for the new users the synchronization with the ox_passwords goes perfectly.

So, this could be a real "Killer-Application" for the 6.01-01 people.
While this is not for using with the new centos-based 7.0 B4, we hope for a special version for it...

Once again, thanks for the work, Vincent!

Rgds.
Dietmar

[djhomeless]

Anyone tried this on 6.5 RC1 by chance?

Geoffrey

[vinc28]

if you want to try follow this link
http://e-smith.dyndns.org/ox/ox7
save all the files in a dir and : rpm -iUvh *

good luck


vincent
 

[onsy]

Anyone tried this on 6.5 RC1 by chance?

Geoffrey

I've tried and it worked almost out of the box.
All you have to do before following this excellent Howto is to install perl module MIME-Lite (i found version 2.117) and It works fine !
Don't forget to change passwords for existing users or to create new users to trigger the update of OX Ldap.

[woyzeck]

Thanks...  The install went pretty easy.  I do have a question though.  Does anyone know if the Outlook Plugin from Open-Xchange works with this rpm?

I downloaded beta version of Outlook OXtender, and it doesn't appear to work.