This issue has been resolved. It was a mistake on my side, sorry to
community.
I changed the dspace.baseurl and dspace.url in config/dspace.cfg to match
then restarted tomcat6 and it has been working like a charm ever since.
--
View this message in context:
I have not yet been able to resolve this issue. However, I am able to reset
the password using the Forgot password option on the login page which
sends a reset link via email. When I do this, I can see that I am logged in.
However when open another page, I am logged-out again or if its a page that
does not work after upgrading from 1.7 to 3.2
Hey Otuoma,
this is very likely not your cause,
but in 1.8.2, we had as similar issue when a user was created automaticlly
(e.g., by Shibboleth) and the appropariate flag
can_log_in in eperson database table
was not set.
Jozef
On 15 August
*To:* Otuoma otuomathegr...@yahoo.com
*Sent:* Thursday, August 15, 2013 4:07 AM
*Subject:* Re: [Dspace-tech] Login does not work after upgrading from 1.7
to 3.2
Hey Otuoma,
this is very likely not your cause,
but in 1.8.2, we had as similar issue when a user was created automaticlly
(e.g
: Thursday, August 15, 2013 5:24 AM
Subject: Re: [Dspace-tech] Login does not work after upgrading from 1.7 to 3.2
That is correct.
Jozef
On 15 August 2013 13:18, otuoma peter otuomathegr...@yahoo.com wrote:
Just inspected by eperson table and everything under can_log_in is set to
t. Is this what
On Wed, Aug 07, 2013 at 10:24:43PM -0700, otuoma peter wrote:
I have almost succeeded upgrading our dspace repository from version 1.7 to
3.2. I followed the upgrade procedures for both versions. However, the login
including the administrator's account can not be logged-in. It does not give
I have almost succeeded upgrading our dspace repository from version 1.7 to
3.2. I followed the upgrade procedures for both versions. However, the login
including the administrator's account can not be logged-in. It does not give an
error message. The login does not just happen and one is
7 matches
Mail list logo
