You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
During navigation to the baseUrl there might be called BCP authentication page with multiple options.
Only after selecting some option BTP authentication can be continued
To Reproduce
Steps to reproduce the behavior:
Go to BTP restricted page with several identity providers
Expected behavior
Selecting default identify provider if not specified or allow identity provider selection in addition to the user/pass. Options are described as plain html tags like
Runtime Env (please complete the following information):
wdi5/wdio-ui5-service-version: 1.5.1
wdio-version (output of wdio --version): 7.3.2
node-version (output of node --version): 18.16.1
OS: Mac
Browser + Version chrome 115
Additional context
Add any other context about the problem here,
e.g. any options the target browser is started with like --headless or
if the tests run in a CI environment
The text was updated successfully, but these errors were encountered:
yeah, would be a really nice feature to have 👍. Currently the wdi5 code team is quite busy. More than welcome to add this feature yourself. See the contribution guide in the docs.
Describe the bug
During navigation to the baseUrl there might be called BCP authentication page with multiple options.
Only after selecting some option BTP authentication can be continued
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Selecting default identify provider if not specified or allow identity provider selection in addition to the user/pass. Options are described as plain html tags like
Screenshots
Runtime Env (please complete the following information):
wdi5/wdio-ui5-service
-version: 1.5.1wdio
-version (output ofwdio --version
): 7.3.2node
-version (output ofnode --version
): 18.16.1Additional context
Add any other context about the problem here,
e.g. any options the target browser is started with like
--headless
orif the tests run in a CI environment
The text was updated successfully, but these errors were encountered: