Maybe I misunderstood. So, you cannot even record a script because the authentication fails? When not recording you can use the application fine? Is it a functional script or load test script you are trying to create? What kind of authentication is it - NTLM?
I clear you the exact scenario my application will only be accessed if specified domain/username/password are authenticated. And while recording or on manual access we need to authenticate by entering the details in the window and then can move further to access any step of the application But as I mentioned I am unable to record window authentication part while recording and further cannot even record my application steps for load testing.
Here, I am using the load testing (HTTP Protocol) scripts. Yes, right I can use my application on manual access (without recording) which is perfectly fine. Yes, it is kind of NTLM. To tell more in brief I have prepared its functional script which I am able to record and working fine too.
Although I have started downloading OATS version 12.x which I will see if works.
Just an update I am able to record whole script(including authentication) with version 12.x of OATS but on playback it gives error at authentication.
oracle.oats.scripting.modules.http.api.exceptions.ThinBrowserException: HTTP response code: 401 Unauthorized
* at oracle.oats.scripting.modules.http.api.exceptions.ThinBrowserException.createErrorInvalidHttpResponseCode(ThinBrowserException.java:66)*
* at oracle.oats.scripting.modules.http.api.internal.ResponseCodeValidator.validate(ResponseCodeValidator.java:21)*
* at oracle.oats.scripting.modules.http.api.internal.AbstractHTTPService.validate(AbstractHTTPService.java:953)*
* at oracle.oats.scripting.modules.http.api.internal.AbstractHTTPService.navigate(AbstractHTTPService.java:521)*
* at oracle.oats.scripting.modules.http.api.internal.AbstractHTTPService.doNavigate(AbstractHTTPService.java:424)*
* at oracle.oats.scripting.modules.http.api.internal.InternalHTTPService.get(InternalHTTPService.java:1937)*
* at oracle.oats.scripting.modules.http.api.internal.browser.WebHTTPNavigator.get(WebHTTPNavigator.java:40)*
* at oracle.oats.scripting.modules.http.api.internal.domElement.AbstractWindowElement.get(AbstractWindowElement.java:106)*
* at oracle.oats.scripting.modules.http.api.elements.WebHTTPTestObject.get(WebHTTPTestObject.java:451)*
* at oracle.oats.scripting.modules.http.api.elements.WebHTTPWindow.get(WebHTTPWindow.java:54)*
* at script.run(script.java:30)*
* at oracle.oats.scripting.modules.basic.api.IteratingVUser.run(IteratingVUser.java:342)*
* at oracle.oats.scripting.modules.basic.api.internal.IteratingAgent.run(IteratingAgent.java:770)*
* at java.lang.Thread.run(Thread.java:619)*
So, the authentication is not happening hence the 401. Difficult to offer a reason without more information to be honest. Correct user authentication details? Have you compared the headers from the playback and recorded pages?
Yes the authentication is right. I have compared that too but there are authentication line inlcuding some encrytped values starting from NTLM written in recorded part and the complete authentication line is missing in playback section
The change for Authentication in OATS 12.x only refers to the automatically created code. Regardless of how the code is created, you still must ensure the parameters to the addAuthentication() call are correct.
You have not answered the question about the domain prefix in the user name field. Please show your code: