upgraded to latest version...

This is the place to report bugs and get support. When posting in this forum, please always provide as much detail as possible.

Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum, do not report it as a bug.

This is the place to report bugs and get support

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.
Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum.
This thread is closed to new posts. You must sign in to post in the forums.
12/11/2012 10:12:30 AM
Gravatar
Total Posts 46

upgraded to latest version...

I have one site that uses LDAP as fallback.  So I use the admin login otherwise a domain login.  It's no longer working (upgraded from probably 2.3.8.5).  I can not log in at all with the regular (non lday) account or any domain accounts.  Help!  

12/11/2012 10:17:19 AM
Gravatar
Total Posts 18439

Re: upgraded to latest version...

Nothing has changed in a long time in terms of ldap or other authentication. 

You need to make sure you keep the same machine key in web.config whenever you upgrade, you need to copy it from the old web.config to the new one. Not doing that could break authentication.

Hope that helps,

Joe

12/11/2012 10:24:20 AM
Gravatar
Total Posts 46

Re: upgraded to latest version...

My machine key was not the same so I copied it from the old.  But I still can't login.  I can login on my other sites that use the email only for login.

12/11/2012 10:37:54 AM
Gravatar
Total Posts 18439

Re: upgraded to latest version...

I would check the log for any clues

/Data/currentlog.config

12/11/2012 10:53:20 AM
Gravatar
Total Posts 46

Re: upgraded to latest version...

When I login with the admin account (which has no matching active directory account) it gives me System.DirectoryServices.DirectoryServicesCOMException (0x8007052E): Logon failure: unknown user name or bad password. in the log.

When I try to login with an active directory account, nothing shows up in the log.

For the first case, it's like it's no longer checking the local DB first.  For the second case I have no clue why it won't let me in.  I checked the values in the DB for my ldap server and they are still there.

12/11/2012 11:07:10 AM
Gravatar
Total Posts 1203
Proud member of the mojoPortal team

Help support mojoPortal!
Add-on modules

Re: upgraded to latest version...

I worked on the LDAP fallback code, and have a Microsoft domain I can test with, so let me download and test using the latest codeline and I'll report back.

Are you using Active Directory authentication or true LDAP?

Jamie

12/11/2012 11:10:36 AM
Gravatar
Total Posts 46

Re: upgraded to latest version...

I believe I'm using true LDAP.

I'll stay tuned... thank you.

12/11/2012 12:09:06 PM
Gravatar
Total Posts 1203
Proud member of the mojoPortal team

Help support mojoPortal!
Add-on modules

Re: upgraded to latest version...

I just tested in our environment and everything seems to be working correctly. I tried the following scenarios:

  • LDAP user (administrator)
  • Non-LDAP user with local DB authentication fallback (login by username)
  • Non-LDAP user with local DB authentication fallback (login by email address)

In my testing I did get the same LDAP failure errors logged when logging in as a local DB user. This is expected, however, because at the time of attempted LDAP login, it's not known if they are an LDAP or local user. So seeing those messages appear in your log is normal.

Unfortunately I don't have the ability to test against a true LDAP server, but as Joe said, that portion of the code has not been modified for a very long time (years).

Are you getting a login failure message displayed in mojoPortal, or does it just appear that nothing is happening? I've seen the latter occur with a misconfiguration of SSL settings.

Jamie

12/11/2012 12:18:34 PM
Gravatar
Total Posts 46

Re: upgraded to latest version...

In both cases (local used and domain user) I get a login failed.  With the local db account I get the message in the log, with the domain account nothing shows up in the log.

12/11/2012 12:36:24 PM
Gravatar
Total Posts 1203
Proud member of the mojoPortal team

Help support mojoPortal!
Add-on modules

Re: upgraded to latest version...

If no error is logged when you attempt signing in as a domain user, that should indicate that LDAP authentication succeeded. I'm not sure what would cause mojoPortal to then fail the login after that point. Hopefully Joe has some other ideas up his sleeve.

Just as a long shot, can you verify that the users you are testing with are not flagged as locked out? Or is it possible that they are under temporary lockout due to too many failed logins before you restored the machine key?

Jamie

12/11/2012 12:52:16 PM
Gravatar
Total Posts 18439

Re: upgraded to latest version...

Sounds to me like authentication is succeeding. The only thing that I know of that could prevent the user from appearing as authenticated after the authentication has happened is if cookies are blocked somehow. There is configuration that can prevent passing cookies if the request is not using https as mentioned in the article Use SSL but it is not configured this way by default. Other things that can block cookies are things like any kind of privacy guard security software (or bowser toolbars), do not track mode in web browsers etc.

I would try different browsers and different client machines to see if you get the same result.

The only other thing I can think of to try is adding this in user.config:

<add key="UseTransferRequestForUrlReWriting" value="false"/>

which would change back to the old way we were doing url rewriting. I don't really see how that could affect authentication but its one of the few recent changes that could have side effects in some environments.

12/11/2012 1:12:42 PM
Gravatar
Total Posts 46

Re: upgraded to latest version...

So my domain account is working.  That was my fault and a total head-smacker moment, my account was marked as deleted.  Ok then.

My local account won't let me in yet.  So in the DB, all but 2 of my admin accounts is NULL for PasswordSalt which would explain why I can't get in, right?  2 admin accounts have their PasswordSalt set and oddly they are the two I logged into right after the upgrade.  How does that make sense?

12/11/2012 1:24:11 PM
Gravatar
Total Posts 46

Re: upgraded to latest version...

Ok so I restored the backup copy of my db and all my admin PasswordSalt fields were NULL.  

 

Anyway, in the DB I made my domain account an admin.  Then I went to member list and was going to update the password for the admin account and see if that works.  But when I got to manage, #1 my tabs are gone.  So it's just a list on the page, not tabbed sections.  And #2 there is no password field anywhere?

 

12/11/2012 1:30:34 PM
Gravatar
Total Posts 1203
Proud member of the mojoPortal team

Help support mojoPortal!
Add-on modules

Re: upgraded to latest version...

No password field showing on the Manage User page means your site is not set to use LDAP fallback. That option was moved from a configuration key to the LDAP section of site security a while back (don't know exactly which version).

Jamie

12/11/2012 1:32:48 PM
Gravatar
Total Posts 18439

Re: upgraded to latest version...

Password salt will be created if it does not exist upon succesful login so that is not a problem, it is designed to handle it if it is empty.

12/11/2012 1:38:51 PM
Gravatar
Total Posts 46

Re: upgraded to latest version...

No password field means I can't set the password for a local db account though.  

12/11/2012 1:45:27 PM
Gravatar
Total Posts 1203
Proud member of the mojoPortal team

Help support mojoPortal!
Add-on modules

Re: upgraded to latest version...

I did some research, and the LDAP fallback option was moved into Site Settings in version 2.3.8.5.

Jamie

12/11/2012 1:48:50 PM
Gravatar
Total Posts 46

Re: upgraded to latest version...

Yeah, mine has alwasy been set with the site in the administration section.  But how am I supposed to set the password for a local account then?

12/11/2012 1:50:53 PM
Gravatar
Total Posts 46

Re: upgraded to latest version...

And can anyone explain what happened to my tabs?  I have a 2.3.9.0 copy that seems to be using jquery on google for the tabs.  This one does not.  I'm talking about the tabs within the administration pages.

12/11/2012 1:59:45 PM
Gravatar
Total Posts 46

Re: upgraded to latest version...

Your demo site and my other site running 2.3.9.0 point to 
http://ajax.googleapis.com/ajax/libs/jqueryui/1.9.0/jquery-ui.min.js for the css for the tabs it would seem.  My new site does not.  Where is that call made so I can see what happened.

 

 

12/11/2012 2:03:28 PM
Gravatar
Total Posts 18439

Re: upgraded to latest version...

"No password field means I can't set the password for a local db account though."

Do you have Use Database Authentication checked in Site Settings? What Jamie is saying is that checkbox must be checked to use both ldap and database authentication whereas in older versions there was a web.config setting. If it is checked then the password field should be available on ManageUsers.aspx

12/11/2012 2:07:40 PM
Gravatar
Total Posts 18439

Re: upgraded to latest version...

"And can anyone explain what happened to my tabs?"

Can you post a link to the site so I can view the source of the page?

By default it should load jquery and jqueryui from the google cdn unless you have configured it to host those files locally

12/11/2012 2:09:49 PM
Gravatar
Total Posts 46

Re: upgraded to latest version...

Do you have Use Database Authentication checked in Site Settings? What Jamie is saying is that checkbox must be checked to use both ldap and database authentication whereas in older versions there was a web.config setting. If it is checked then the password field should be available on ManageUsers.aspx

Oops, I missed that.  Ok, that's working! Thanks!

12/11/2012 2:40:10 PM
Gravatar
Total Posts 46

Re: upgraded to latest version...

go to dev2.lrri.org and login with tempuser@tempuser.com using pass tempuser12345

12/11/2012 2:56:30 PM
Gravatar
Total Posts 18439

Re: upgraded to latest version...

On the site where the tabs are not working it looks like an unmodified version of artisteer31-green skin, can you copy the latest version of that skin from the /Data/skins folder into /Data/Sites/5/skins and see if that solves it?

12/11/2012 3:03:30 PM
Gravatar
Total Posts 46

Re: upgraded to latest version...

That's where I got that skin from in the first place but I did it again just to make sure and reset the site guid.  Still no tabs.

12/11/2012 3:06:07 PM
Gravatar
Total Posts 18439

Re: upgraded to latest version...

If your layout.master file has this:

<portal:ScriptLoader ID="ScriptLoader1" runat="server" IncludeSizzle="true" />

remove the IncludeSizzle="true"

also if it has this:

<portal:SkinFolderScript ID="sfs1" runat="server" ScriptFileName="script.js" AddToCombinedScript="true" />

try setting AddToCombinedScript="false"

12/11/2012 3:08:34 PM
Gravatar
Total Posts 18439

Re: upgraded to latest version...

If all else fails to resolve it look for this in Web.config

<add key="GoogleCDNjQueryVersion" value="1.8.2"/>
 <add key="GoogleCDNjQueryUIVersion" value="1.9.0"/>

and change it to

<add key="GoogleCDNjQueryVersion" value="1.7.1"/>
<add key="GoogleCDNjQueryUIVersion" value="1.8.16"/>

12/11/2012 3:23:12 PM
Gravatar
Total Posts 46

Re: upgraded to latest version...

I changed the versions of the googlecdn and that fixed my tabs!  Thank you!  

You must sign in to post in the forums. This thread is closed to new posts.