Forum Discussion
- Created Generic project
- Added suite, test case, and HTTP request with default names
- Added 3 Project-Level properties: URL, Username, Password
- Clicked Environments, created Development env and selected Copy endpoints & credentials from the project
- Clicked Environments, created Staging env and selected Copy endpoints & credentials from the project
- Went to HTTP Request Test step (while Environment was set to Default) and clicked Auth tab
- Set Authorization to Basic. Note: in the HTTP Request Properties section on the Navigator pane, Authorization Type was set to Global HTTP Settings
- Filled in username/password/domain fields with ${#Project#Username}, ${#Project#Password}, ${#Project#URL}
- Went to Environment drop down and switched from Default to Development
- The Auth tab went grey, Username/Password/Domain fields disappeared, Authorization was set to No Authorization, and the drop down was disabled. Authentication Type on the Navigator pane was set to No Authorization (this happened when I clicked on the Global HTTPS Value).
- Switched Environment drop down from Development to Staging and the Auth remained greyed out. Authentication Type on the Navigator pane was set to No Authorization.
- Switched Environment drop down from Staging to Default and the Auth tab fields all appeared. Authorization Type drop down worked, and the Username Password Domain fields were editable. I clicked on Authentication Type on the HTTP Request Properties tab under the Navigator pane, and it changed from No Authorization to Global HTTP Settings.
I used a generic URL and User/pass values for this test, so you might not see a difference in the Http Raw responses. The writeup above mainly shows the behavior in SoapUI NG Pro. The issue is more evident using our own web services as we are posting/deleting files to file respository and the posting/deleting does not happen when the No Authorization issue blocks our credentials from being sent.
I’ve tried importing my work project to a different employee’s machine, and she has tried on 1.3.1, and 1.5.0. She is able to get the authentication working on 1.3.1 but not 1.5.0, and the rest of us are using 1.5.0.
I’m about to try downloading and installing the latest nightly build from https://support.smartbear.com/downloads/readyapi/nightly-builds/#_ga=1.187228718.724436189.1452738956. I will report back if this fixes things for me or not.
- nmrao9 years agoChampion Level 3Thank you for the details and the project.
Related Content
- 9 years ago
Recent Discussions
- 19 hours ago
- 17 days ago