cancel
Showing results for 
Search instead for 
Did you mean: 

Questions about Alfresco 3.2

luisg
Champ in-the-making
Champ in-the-making
Hi there…
I just install Alfresco 3.2, and tried to configure with my needs.

The 1st thing I notice is that, some configuration files just changed its place. One example is the files for LDAP configuration.

In file ldap-authentication.properties we have, for example, ldap.authentication.userNameFormat=uid\=%s,ou\=People,dc\=company,dc\=com. To configure to my needs, I need to changed the values. The thing is, should the '/' and '\' remain, or we should change that to, for example, ldap.authentication.userNameFormat=uid=%s,ou=People,dc=company,dc=com?

In directory <Alfresco_Directory>/tomcat/webapps/alfresco/WEB-INF/classes/alfresco/subsystems/Authentication we have many types of authentication. How we know the one that is used Alfresco?

Is the configuration of kerberos easier than the last versions? I ask this because I suppose that in this version CIFS's not workin with LDAP authentication yet, right (due MD4 and MD5 incompatibility)?

Finally, I would like to thank to all Alfresco engineers, by his excellent work.

Luis
14 REPLIES 14

ed_mann
Champ in-the-making
Champ in-the-making
Luca,

I have asked the same question and i have not gotten a definitive answer on it.  I have another thread going where this very same  question is asked. I did get this response from an "Alfresco Engineer":
I don't know why the PostgreSQL scripts were also dropped, it may have just been lack of opportunity to test and validate with that db.
So somebody forgot to configure the build system to test PostgreSQL and did not have time to make the necessary scripts. You would think someone from Alfresco would come out and let the community know why the scripts were not included. Granted this is just one example of why more "Community" members need to get involved with the development of Alf. My goal was to start with 3.2, but i am not 100% sure of the direction Alfresco wants to take the project. I do welcome feedback.

Thanks.

robl
Confirmed Champ
Confirmed Champ
I do hope PostgreSQL support returns.  I have been migrating most of my apps from MySQL to PostgreSQL during the past 9 months or so.  It would be nice to consolidate all of my apps to use a single type of database server, from a support perspective.

I hope this was just an oversight during the release and will be rectified soon.

mikef
Champ in-the-making
Champ in-the-making
Support for PostgreSQL has not been dropped, however, it is not included in the initial 3.2 release. An update will provided shortly to include PostgreSQL support. We will make an announcement on the forum as soon as it is available.

kbootz
Champ in-the-making
Champ in-the-making
I installed the 3.2 community release of alfresco with the default mysql db. To install postgres on Windows as local administrator here's what I did:

    Stop the tomcat/alfresco instance.

    Create a local machine user named 'postgres' using "administrative tools:computer Mgt/Local users and groups/users"(path?)

    Install Postgres. I used "postgresql-8.4.0-1-windows.exe". Record the path specified for the 'data' directory and set an env var - PGDATA - to that value

    Copy the postgres driver jar to the tomcat lib dir. I used 'postgresql-8.4-701.jdbc4.jar' from the postgres downloads page; http://jdbc.postgresql.org/download/postgresql-8.4-701.jdbc4.jar



    Get and install the postgres amp from alfresco wiki:  postgresql-3.2-community.amp ; http://process.alfresco.com/ccdl/?file=release/community/build-2039/postgresql-3.2-community.amp



   Alter your alfresco.bat file in the alfresco install location so mysql doesn't start. An annoyance more than anything else. "goto tomcat" prior to mysql startup section, something similar prior to the mysql shutdown section

     Alter your %ALF_HOME%\tomcat\shared\classes\alfresco-global.properties file to use postgres, ie.;

#

# Sample database connection properties

#————-

db.name=alfresco

db.username=alfresco

db.password=alfresco

# db.host=localhost

# db.port=3306



#

# MySQL connection

#————-

# db.driver=org.gjt.mm.mysql.Driver

# db.url=jdbc:mysql://${db.host}:${db.port}/${db.name}

# hibernate.dialect=org.hibernate.dialect.MySQLInnoDBDialect



# PostgresQL

db.driver=org.postgresql.Driver

db.url=jdbcSmiley Tongueostgresql://localhost:5432/${db.name}

hibernate.dialect=org.hibernate.dialect.PostgreSQLDialect

hibernate.query.substitutions=true TRUE, false FALSE





    Remove your lucene indexes directories from your alfresco data location . %ALF_HOME%\alf_data\lucene-indexes\"remove these dirs!"


    Execute the postgresql sql shell - psql - accepting the defaults to connect as postgres using the password you set when you created the postgres user locally.  "C:\Program Files\PostgreSQL\8.4\scripts\runpsql.bat" OR the PostgresQL program group SQL Shell item



•         create database alfresco;

•         \connect alfresco

•         create user alfresco password 'alfresco';

•         \q

trialot
Champ in-the-making
Champ in-the-making
Some remarks with respect to PostgreSQL installation:

First of all,  note that the installation manual is not entirely correct (if i am not mistaken). In this manual, the postgresql setup on page 64/65 is mentioning:

"To allow password-authenticated connections through TCP/IP, ensure the PostgreSQL
configuration file contains the following:

host all all 127.0.0.1/32 password

For PostgreSQL version 8.1.3, the file name is pg_hba.conf. For every other version, the file
name is postgresql.conf.
"

Note that the line "host … " should be in pg_hba.conf, even for versions other than PostgreSQL version 8.1.3.

Second, note that the order of listing the "host … " does seem to matter. My advice: put it on the first line of the pg_hba.conf file.

Third, another piece of advice: do not use "host all all 127.0.0.1/32 password" but use ""host [alfresco_database_name] all 127.0.0.1/32 password" or "host [alfresco_database_name] [alfresco_database_user] 127.0.0.1/32 password" instead, in order to have some degree of safety with respect to connections to the PostgreSQL database.

Finally, a question arises: somebody has experience with the change of "password" method into "md5" method? It should not make any difference in theory, but it seems that there are some issues with md5 encryption.

Can anyone shed a light on this? Does the community edition (and the PostgreSQL amp file in particular) support that md5 method?