Microsoft Dynamics GP 10.0 Service Pack 2 Login Issue Fixed

Mark has interesting information posted on his blog on a security fix addressed in Microsoft Dynamics GP 10.0 Service Pack 2 (10.00.1061). The original issue had to do with turning on password control with password expiration in GP, which is in turn address by Active Directory. Go on to read Mark’s post on the issue to get the full details.

Until next post!

MG.-
Mariano Gomez, MIS, MVP, MCP, PMP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com

Advertisements

2 Responses to Microsoft Dynamics GP 10.0 Service Pack 2 Login Issue Fixed

  1. David Musgrave [MSFT] says:

    This is documented on the Issue Resolved page.https://mbs.microsoft.com/downloads/customer/Dex1000Fixes.htmDexterity Runtime – Bug #42423 – Make SQL login incorrect password fallback configurableResolved. In previous versions, SQL Logins were tried with new the 9.0 encryption, pre 9.0 encryption, plain text login, and then the new encryption model. This would give the user 4 login attempts if they accidently typed in the wrong password. With this release, only the current encryption will be tried. If the user needs to use the “old” methods – for example just logging in after an update from 8.0 or if the password was changed via SSMS to plain text, adding the dex.ini switch SQLLoginCompatibilityMode=TRUE will revert to the previous behavior.David Musgrave [MSFT]Escalation Engineer – Microsoft Dynamics GPMicrosoft Dynamics Support – Asia PacificMicrosoft Dynamics (formerly Microsoft Business Solutions)http://www.microsoft.com/Dynamicsmailto:David.Musgrave@online.microsoft.comhttp://blogs.msdn.com/DevelopingForDynamicsGPAny views contained within are my personal views and not necessarily Microsoft policy.This posting is provided “AS IS” with no warranties, and confers no rights.

  2. David Musgrave [MSFT] says:

    This issue was raised by me after a support case I had, resulting in bug 424423 being created.I suggested the use of a dex.ini setting to control behaviour. :-)The reason why the change was needed is discussed in the following KB, Question 5.https://mbs.microsoft.com/knowledgebase/KBDisplay.aspx?scid=kb;en-us;922456David Musgrave [MSFT]Escalation Engineer – Microsoft Dynamics GPMicrosoft Dynamics Support – Asia PacificMicrosoft Dynamics (formerly Microsoft Business Solutions)http://www.microsoft.com/Dynamicsmailto:David.Musgrave@online.microsoft.comhttp://blogs.msdn.com/DevelopingForDynamicsGPAny views contained within are my personal views and not necessarily Microsoft policy.This posting is provided “AS IS” with no warranties, and confers no rights.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: