dynamics crm 2016 outlook client remember password

#Dynamics crm 2016 outlook client remember password update

You also likely don’t want these integrating applications to fail when the specific password expires for that user account.

#Dynamics crm 2016 outlook client remember password update

“Dave, why did you update all of the account records last night at 2am?” When in fact, Dave’s user account was used in an integration to update discount rates from another system. Discovery!Īnother reason is that you don’t want the “created by” or “modified by” values of your Common Data Service records to reflect a specific user when in fact it was an external application.

“Oh, here is Dave’s login for Dynamics!” Oops. A server admin could stumble upon a config file and grab the credentials to an otherwise protected business system. First off, you need to store the username and password somewhere, ideally somewhere safe so malicious agents can’t extract the credentials and use them for other reasons. These “user accounts” would also at times be setup as non-interactive users so they wouldn’t consume a license.Ī couple of key issues come up with the approach. Other custom applications could use the same approach.

A common example would be legacy portals where the username and password would be stored in the web.config file. This used to be a common way for external applications and integrations to authenticate to the Common Data Service (Dynamics 365). When you build custom solutions where you need to create, read, update or delete data in the Common Data Service (including Dynamics 365 apps), you don’t necessarily want that application to use specific user credentials to do its work.