FIX: SBM: Static Diagnostics Notification Server and Mail client database connection fails if TLS 1.0 is disabled -… https://t.co/9VH1phwPWM
JUser: :_load: Unable to load user with ID: 1005
Accepted AnswerModeratorBrian AmosOffline
Accepted Answer0My post was only to say that for me passing the userid and password via the url didn't work, and that I think I still have an active case on this issue. It used to work but stopped at some unknown time. I cannot do Web Query's any longer, they work during the initial setup but fail after you save the spreadsheet, close the doc and re-open. The post was mostly informational as I thought the OP might be dealing with a username password passing issue rather than script. Am I clear that you can run the script via url context without passing a username and password?
Accepted Answer0Hi Mike and Brian. Once a user is logged in, the script works in a browser via
If no user is logged in, the URL above leads to the logon form.
With typo3 running on another machine I need a user login to get the script running. Our Serena Consulter told me that I can use the logon like I showed in my first post:
But this is not working. I suppose I need something like a working session or a hidden parameter.
Accepted AnswerDoru VoineaOffline
Accepted AnswerEmployeeBrock BlandOffline0Hey guys,
When using SSO there's no way to do this. SBM has several authentication types available with increasing levels of security. We do support an authentication type that allows for login parameters on the URL (Form/URL/Cookie) but this does not work for all authentication types.
SSO is our most secure form of authentication and session management. It has a plethora of safe guards built into it, one of which is the prevention of replay attacks. This is why the above request to the login page doesn't work. We won't issue security tokens to unsolicited requests.
To do what you're wanting to do here it would be best to have a little programmatic interaction where you go through the login process then make the request for the script to run.
Accepted AnswerEmployeeGeorge StanchevOffline0Hi Michael,
Use the following WS-Trust request. You can call a SOAP service at
Unfortunately there is no WSDL for WS-Trust requests so you'd have to handcraft it from the snippet below.
<?xml version="1.0" encoding="UTF-8"?>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" soapenv:mustUnderstand="1">
Put the username and password in the wsse:Username and wsse:Password elements in the SOAP WS-Security header. The response would be either a SOAP fault if you failed or a WS-Trust RequestSecurityTokenResponse SOAP message. The response is too big for me to post here but you need to extract the token from
it will be an XML in the form of ...
If you convert that XML to a string and then BASE64-encode it, you'd be able to include it to your calls to Application Engine in a ALFSSOAuthnToken HTTP header.
Accepted AnswerPaul ThompsonOffline