For some web application which use a construct like "Bearer Tokens" Sahi removes the authorization header and so break the tests: The website will continuously logout and are not controllable.
Add a advice to Sakuli to skip the execution if removeHeader will be called with the value "Authorization"
Add the property sahi.proxy.removeAuthorizationHeader.enabled: is set to true like the default behavior of sahi (We don't know the impact on other applications)
For some web application which use a construct like "Bearer Tokens" Sahi removes the authorization header and so break the tests: The website will continuously logout and are not controllable.
Example:
Like also discussed at Sahi Community - Authorization header getting stripped out this behavior is not wanted.
Solution: Skip the execution of the action
HttpRequest.removeHeader("Authorization")
Tasks:
removeHeader
will be called with the value"Authorization"
sahi.proxy.removeAuthorizationHeader.enabled
: is set totrue
like the default behavior of sahi (We don't know the impact on other applications)