User's Can't Log In!
Page: 1, 2
Recent posts in this topic
joomlajunkie
on May 4. 2008. 8:48 pm
I'm pretty darn frustrated I can login no problems but when I create a new company and a user and add them to the project they cannot login. Any reason why?
I am running Activecollab Beta 3, I don't feel like upgrading yet to the latest version.
Please can someone tell me why I can sign-in as the admin but other users get the following error even though the account info is correct.
Failed to log you in with data your provided. Please check your data and try again
Thanks!
I am running Activecollab Beta 3, I don't feel like upgrading yet to the latest version.
Please can someone tell me why I can sign-in as the admin but other users get the following error even though the account info is correct.
Failed to log you in with data your provided. Please check your data and try again
Thanks!
Hi joomlajunkie,
Are you sure they are trying to log in with their email address and not the newly created username?
Have you tried logging in to the user account yourself, or is this a report from your user?
Are you sure they are trying to log in with their email address and not the newly created username?
Have you tried logging in to the user account yourself, or is this a report from your user?
Ilija Studen
on May 5. 2008. 12:06 am
If you can log in and use the system normally with your own account than it's not the normal set of issues that cause login problems (session misconfiguration etc as explained here). There is also no known bugs with login system in beta...
It must be something with the new account or the way it is accessed.
Make sure that login credentials are 100% correct (change the password to known value and try it with your own browser on your computer). If that doesn't help contact us on support@a51dev.com and we'll take a look.
It must be something with the new account or the way it is accessed.
Make sure that login credentials are 100% correct (change the password to known value and try it with your own browser on your computer). If that doesn't help contact us on support@a51dev.com and we'll take a look.
activeCollab team member
joomlajunkie
on May 5. 2008. 4:24 am
Okay I have re-set the passwords on an account then Using Firefox and Safari I attempted to login myself using the account info making sure 100% correct and it still gave me the same error.
Do you think I should just downgrade or something? to 1.0.6
It's strange that I can login though using my account info, Do you think its something to do with the fix I did in User.Class.php ?
Thanks
Do you think I should just downgrade or something? to 1.0.6
It's strange that I can login though using my account info, Do you think its something to do with the fix I did in User.Class.php ?
Thanks
Ilija Studen
on May 5. 2008. 4:36 am
What changes did you make to User.class.php?
activeCollab team member
Ilija Studen
on May 5. 2008. 6:00 am
What is the exact piece of code (block or entire method with highlighted change would be great)? I have 5 versions of User.class.php on my computer, all different :)
Strange thing here is that login is actually working, but not for a specific account. It's problem with credentials or the way they are interpreted.
Strange thing here is that login is actually working, but not for a specific account. It's problem with credentials or the way they are interpreted.
activeCollab team member
Not sure if this is related, but I created two 'Project Roles', then used them for two new users. Everything seemed fine until they logged in using the credentials in the email and received a access denied page. The ONLY difference between these two users and all other users who could login and access the system, was the role. So I changed them both to 'Administrators' and asked them to try again. They were both able to sign in and access the system.
We are using beta 3.
Each off the 'Project Roles' had mostly ...and manage settings, but both ALSO had 'no access' for checklists.
So, my guess is that this issue lies in the 'Project Roles' code, IF one or more of the modules is set to 'no access'. NOTE: I have not tried setting a 'Project Role' with all 'has access' settings, which would help rule out the 'no access' setting assumption for the bug.
We are using beta 3.
Each off the 'Project Roles' had mostly ...and manage settings, but both ALSO had 'no access' for checklists.
So, my guess is that this issue lies in the 'Project Roles' code, IF one or more of the modules is set to 'no access'. NOTE: I have not tried setting a 'Project Role' with all 'has access' settings, which would help rule out the 'no access' setting assumption for the bug.
Ilija Studen
on May 6. 2008. 4:40 am
Project roles are per project only and does not have anything to do with login. If for any reason (there was a bug in one of the earlier beta versions) user has a project role selected in his profile - change it and use system role.
activeCollab team member
Maybe the issue I am referring to was fixed in beta 4. I'll explain it in a different way to help be sure.
Start by creating a new user as and 'Administrator' (or any System Role) Call this the 'TEST' user.
Login as that users and confirm that you can access the system.
Logout, then back in as an Administrator.
STEPS:
1. Create a new 'Project Role' named 'TEST' in admin/roles.
2. Set all 'Permission Levels' to 'Has Access', then save.
3. now change the 'TEST' user's role to 'TEST' (on the update Profile page)
4. Logout, then try to login as the 'TEST' user again.
RESULT:
After entering 'TEST' username/password, and pressing enter, you get an error page:
HTTP/1.1 403 Forbidden @ http://ac.ourdomain.com/dashboard
Change the user back to any System Role and they now can login. Am I missing something here or is this a bug?
Start by creating a new user as and 'Administrator' (or any System Role) Call this the 'TEST' user.
Login as that users and confirm that you can access the system.
Logout, then back in as an Administrator.
STEPS:
1. Create a new 'Project Role' named 'TEST' in admin/roles.
2. Set all 'Permission Levels' to 'Has Access', then save.
3. now change the 'TEST' user's role to 'TEST' (on the update Profile page)
4. Logout, then try to login as the 'TEST' user again.
RESULT:
After entering 'TEST' username/password, and pressing enter, you get an error page:
HTTP/1.1 403 Forbidden @ http://ac.ourdomain.com/dashboard
Change the user back to any System Role and they now can login. Am I missing something here or is this a bug?
