CRM Credential Verification

Question

My goal is simple. Using the Dynamics CRM 2013 API and the given URL, username, password, and domain, how can I verify that the values ​​are valid?

I have my own application that will use the API. I have a settings screen where the user enters the URL, username, password and domain. I also have a “Test Connection” button that will verify that it can connect using this information.

Here is the logic I use to create the connection:

string connectionString; if (_crmDomain != "") connectionString = string.Format(@"Url={0}; Username={1}\{2}; Password={3}", url, domain, userName, password); else connectionString = string.Format(@"Url={0}; Username={1}; Password={2}", url, userName, password); var css = new ConnectionStringSettings("CRMConnectionString", connectionString); var cn = new CrmConnection(css); var service = new OrganizationService(cn); 

The problem is that even if the credentials are invalid (possibly the wrong password), the line that creates the new organization works fine. Is there any way to verify that it will work when the final call is completed?

Now I will manage to make a fictitious call. This forces it to create a connection. That's what I'm doing:

 var request = new RetrieveAllEntitiesRequest(); request.EntityFilters = EntityFilters.Entity; service.Execute(request); 

If the credentials are invalid, the line service.Execute throws an exception. This works fine with one problem. Assume that the user has entered valid credentials and successfully clicked Test Connection. Now let's say that they change the password to be wrong, and click "Test Connection." In this case, he is still doing well. It looks like a pre-existing connection is being used. Is there a way to destroy or clear the previous connection so that when trying with invalid values ​​it throws an exception?

Again, my common goal is to check the input values. No matter what provides the best way to achieve this, I will follow them. Thanks!

Answer 1

Omit the use of ConnectionStringSettings and use CrmConnection.Parse() .

 var cn = CrmConnection.Parse(connectionString); var service = new OrganizationService(cn); try { service.Execute(new WhoAmIRequest()); } catch (Exception ex) { //Do something because connection setup was bad } 

UPDATED

I executed the following code and got the expected result shown below the code. When the password is changed to the wrong password, the request does not work, and when it is changed to a good password, it will be successful.

 var connectionString = @"Url=https://server.com/orgname/;Username=domain\username;Password=goodpassword;"; var cn = CrmConnection.Parse(connectionString); var service = new OrganizationService(cn); try { service.Execute(new WhoAmIRequest()); Console.WriteLine("Good Password"); } catch { Console.WriteLine("Bad Password"); } connectionString = @"Url=https://server.com/orgname/;Username=domain\username;Password=badpassword;"; cn = CrmConnection.Parse(connectionString); service = new OrganizationService(cn); try { service.Execute(new WhoAmIRequest()); Console.WriteLine("Good Password"); } catch { Console.WriteLine("Bad Password"); } connectionString = @"Url=https://server.com/orgname/;Username=domain\username;Password=goodpassword;"; cn = CrmConnection.Parse(connectionString); service = new OrganizationService(cn); try { service.Execute(new WhoAmIRequest()); Console.WriteLine("Good Password"); } catch { Console.WriteLine("Bad Password"); } 

Output to the console:

 Good Password Bad Password Good Password