12/21/2017
Topic:
Credential problems getting into Microsoft CRM
Alex
|
We are evaluating this tool for use in doing load testing with Microsoft Dynamics CRM. The problem seems to be where StresStimulus is obtaining the logon credentials. This is what occurs; 1. I go to record a test via the tool. 2. The URL is entered and it goes to the correct Microsoft Dynamics 365 logon screen. 3. I have multiple userids who can access the Microsoft Dynamics site (BTW, I have all my Security - User Authorization setting set to "Prompt for Userid and Password") 4. I select one of the userids I have available to me and enter it into the logon screen (this is different from the userid I have logged onto my Windows 7 system with). These are generic test Ids that have the appropriate security access to our in-house application built in Microsoft Dynamics. 5. Once one of the userids are selected for the Microsoft Dynamics signon screen this gets validated and should proceed to our in-house built application signon screen. However the userid and password that gets passed to seems to be the one that I signed onto the Windows 7 Machine and get the following message
 6. Inspecting the code I find that in the "login.microsoftonline.com/common/userrealm" is pointing to my system userid rather than the one I initially selected. Question: Is there a way to bypass this and if so how is this accomplished. If further clarification is required let me know. |
1/16/2018
Topic:
Credential problems getting into Microsoft CRM
Alex
|
Already did that George, Derek's solution was just the ticket.
Thanks for everyones help!
Alex |
2/14/2018
Topic:
Cookies JSON etc...
Alex
|
Hello, So I am evaluating StresStimulus to work with our Microsoft Dynamic CRM in house written application. Some of the issues that I seem to have revolve around the use of Session cookies and some JSON being using in the application/run of my test. I record a very simple test, logging into our CRM environment (which was the first hurdle, since I was not using my own Id to do, but after some advice about using Microsoft Credential Manager, this was overcome). However, now after I record my simple script. Basically going into the application, performing some simple navigation and selecting a report and displaying it, when I perform the verify I get some warnings and errors. The warnings are primarily the replayed command giving a response code of 302 versus 200. Looking at a compare between the recorded and replayed it can be noted that the Cookies are different. I think I was able to solve this using the Set-Cookie override. However, the errors in the JSON present a bit more of a challenge as I think these are somehow set within the application at runtime. Anyone ever encountered this type of situation before and how is it dealt with. Sincerely, Alex |