Mailing-List: contact commits-help@roller.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@roller.apache.org
Date: Fri, 17 May 2013 01:02:33 +0000 (UTC)
From: "tmjee (JIRA)" <jira@apache.org>
To: commits@roller.apache.org
Message-ID: <JIRA.12647903.1368690864761.336449.1368752553610@arcas>
In-Reply-To: <JIRA.12647903.1368690864761@arcas>
References: <JIRA.12647903.1368690864761@arcas>
Subject: [jira] [Comment Edited] (ROL-1961) Cannot login after installation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ROL-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660222#comment-13660222 ] 

tmjee edited comment on ROL-1961 at 5/17/13 1:01 AM:
-----------------------------------------------------

Hi Glen, 

Spot on. It was indeed due to charset. 

Tables need to be created with 

CREATE DATABASE mydb
  DEFAULT CHARACTER SET utf8
  DEFAULT COLLATE utf8_general_ci;

This should have been done by Roller and i thought that Roller would have done that but 

show variable '...' 

show me otherwise. 

Double checked the dbscripts/mysql/createdb.sql seems to indicate otherwise as well (assuming that is where Roller picked up it's db schemas) 

Like you said we could either 
 change /etc/my.cnf  to incorporate thse

or do an alter database set default_character_set .... blah blah ...
if we dun want to do a reinstall ..

Cheers Glen. 

Resolving this issue now
                
      was (Author: tmjee):
    Hi Glen, 

Spot on. It was indeed due to charset. 

Tables need to be created with 

CREATE DATABASE mydb
  DEFAULT CHARACTER SET utf8
  DEFAULT COLLATE utf8_general_ci;

This was done by Roller and i thought that Roller would have done that but 

show variable '...' 

show me otherwise. 

Double checked the dbscripts/mysql/createdb.sql seems to indicate otherwise as well (assuming that is where Roller picked up it's db schemas) 

Like you said we could either 
 change /etc/my.cnf  to incorporate thse

or do an alter database set default_character_set .... blah blah ...
if we dun want to do a reinstall ..

Cheers Glen. 

Resolving this issue now
                  
> Cannot login after installation
> -------------------------------
>
>                 Key: ROL-1961
>                 URL: https://issues.apache.org/jira/browse/ROL-1961
>             Project: Roller
>          Issue Type: Bug
>    Affects Versions: 5.0.1
>            Reporter: tmjee
>            Assignee: Roller Unassigned
>
> Hi, 
>  - Downloaded Roller version 5.0.1 from roller's download page. (the tomcat version with jpa enhanced classes)
>  - unpack the war file into servlet container of choice 
>  - change db settings in roller-custom.properties and stick it into container's classpath
>  - start up container
>  - hit roller on browser
>  - click the install tables button
>  - click "here" link after tables creation is successful
>  - click to create a user
>  - after successfully created a user when i tried to login roller keeps saying the login password is wrong.
> I've checked the algorithm and by default in roller.properties it is SHA 
> Checked the rolleruser data base passphrase and looks like it is being hashed.
> however login failed even though i'm sure i got the correct password.
> Use sql to change the passphrase to a clear text one. Attempt to login and its a success.
> I am guessing roller does not honor the hashing algorithm for soem reason.
> Tried this using Mysql.
> Just wondering is anyone else experiencing this?
> Thanks
>  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira