using the same credentials on SugarCRM as zarafa

[ballapd]

Hello,

there is a possibility to using the same credentials on SugarCRM as on the zarafa?

Thank you,

p

[admin]

yes there are some relationships between the 2 projects but it is not yet implemented in Artica

[ballapd]

Hello David,

what do you think can I install the Z-Merge framework (without major problems)?

Thanks,

p

[admin]

you can, Zarfa is installed in the "supported" way

[chris_c_]

yes there are some relationships between the 2 projects but it is not yet implemented in Artica

My opinion - it should be easy for Artica management console to modify the settings in a SugarCRM (groupware) instance, to set the SugarCRM instance to use the Artica/Zarafa company organization employee directory (saved in Artica's OpenLDAP server) for authentication/login to SugarCRM using the same password and username/email as saved in the Artica organization - the same username/password that the user has for login to Zarafa.

This saves hours of administration time that would be wasted coordinating all the duplicated user accounts between the two software platforms - OpenLDAP (Artica/Zarafa user/email/password database) and SugarCRM (user/email/password database).

HEre is the information on how to set the settings in SugarCRM admin panel.. which is living either in a SugarCRM settings file, or in the SugarCRM mysql database table...

http://support.sugarcrm.com/02_Document ... 0/03_Users

Ctrl+F to search for "LDAP Support"

LDAP Support

You can enable LDAP authentication in this section.

If you are using LDAP authentication, you must disable the Forgot Password option.

To enable LDAP authentication, select the Enable LDAP box, and enter the following information in the fields below:

Server. Enter the LDAP server name.

Port Number. Enter the server’s port number.

User DN. Enter the user DN name; for example, ou=people, dc=example, dc=com.

User Filter. Enter any additional parameters to apply when authenticating users. For example, is_user_id=1.

Bind Attribute. Enter the attribute name that is used to bind the user’s name in LDAP. For example, in openLDAP, the attribute name is userPrincipleName.

Login Attribute. Enter the attribute name that is used to search for the user in LDAP. For example, in openLDAP, the attribute name is dn.

Group Membership. Select this checkbox if you wish to specify that the user is a member of a specific group, and enter the following information:

Group DN. Enter the group DN name; for example, ou=groups, dc=example, dc=com.

Group Name. Enter thegroup name; for example, cn=sugarcrm.

User Attribute. A unique identifier used to check if the user is a member of the group. For example, uid.

Group Attribute. The attribute of the group that will be used to filter against the User Attribute. For example, MemberUid.

Authentication. Select this checkbox to use specific user credentials to bind to the LDAP server, and enter the user name and password in the fields that display below.

Auto Create Users. Select this checkbox to create the user name in the Sugar database if it does not already exist.

Encryption Key. If you are using LDAP with SOAP, enter the encryption key to encrypt user passwords in the Sugar Plug-in for Microsoft Outlook. The php_mcrypt extension must be enabled in the php.ini file.

SAML Authentication.

Use this section to enable SAML authentication.

You must disable the Forgot Password option if you are using SAML authentication.

Select the Enable SAML Authentication checkbox and enter the following information:

Login URL: Enter the SAML URL for authentication. This is the path to the SAML server you are authenticating to.

X509 Certificate: Enter the SAML X.509 certificate public key.

5. Click Save.

In your opinion David - and the opinion of all Artica users of Zarafa + SugarCRM - is it a smart move, to add this feature (Make SugarCRM use Artica/Zarafa username/password database for login) to Artica Management Console ?