Skip to Main Content
Forums

General Development Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

OpenScript think (10.0); times are not working when using command line

Mark Morrill-OracleNov 21 2018 — edited Nov 28 2018

I have OpenScript scripts within OATS that use delays by setting up "think (10.0);". This works great within the OpenScript UI. The scripts pass and the delays work correctly. But when I run the same scripts from command line, the scripts don't delay which causes issues. Why doesn't the think (10.0); commands work when I run the scripts from command line?

Screen shot from the OpenScript UI showing the think times and looking at the Time Stamp columns we can see that it is delaying correctly.

pastedImage_1.png

Screen shot below is from the OpenScript UI showing the same script after running it from the Command Line.

pastedImage_4.png

I am using:

Version: 13.3.0.1 Build 262

Comments

gernot

Instance debugging (d0.sql) shows that HTTP header variable is found and its value is correct. But the sentry function still fails - see attachment
d2.txt (12.99 KB)Which additional conditions are checked in the sentry function (in HTTP header variable authentication scheme to login in APEX itself)?
(user exists and is open)
Thanks

user12097829

Hi,
I've the same problem here (using Apex 21.2 and Apex 22.1):
HTTP header variable is set by Apache and found by Apex. But the sentry function still fails.
Using the Oracle provided "HTTP header variable" authentication scheme, there's no possibility to specify a custom sentry function, but obviously there must be an internal sentry function.
Which additional conditions are checked in the internal sentry function?
Thanks

user12097829

Hi,
found a solution for my problem with "HTTP header variable":
Following several tutorials I had set "Verify Username" to "After Login" for my authentication scheme.
After changing setting "Verify Username" from "After Login" to "Each Request" everything works fine.
Thanks

1 - 3

Post Details

Added on Nov 21 2018
#qa-testing
1 comment
354 views