Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
A complete cloud platform for an app or your entire digital business
Detect and predict anomalies by automating machine learning to achieve higher asset uptime and maximized yield
Automate decision processes with a no-code business rules engine
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Personalize and optimize the customer experience across digital touchpoints
Build, protect and deploy apps across any platform and mobile device
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Hi can anybody help me with this?
I need to call a soap service on the client side page. How can I do this in a save way without storing credentials and putting in a variable on the client side?
Is there an option to run a server side trigger that gives me the result of the soap call as a callback?
thanks in advance,
I ran up against this a while back. The other APIs (REST, SOAP, etc) require a separate login call from the client in order to use them. This means that without having the credentials of the user, somehow, it's not going to be possible.
You might be able to run a trigger that returns the result of a SOAP call but, at that point, you'd probably need to hard-code a username and password in the trigger script... which would reduce visibility into who was actually making calls and practically eliminate the use of permissions.
Which API method are you wanting to use? There may be another alternative.
You can make a SOAP over http call from Rollbase Application pages and Portal pages. For this, you can leverage client-side API: rbf_sendHttpRequest
Instead of coding any sensitive information (like request parameters with authentication details) directly as part of client-pages you may considering using server-side tokens (escaping them as described in documentation) so that the actual request is formulated on Rollbase server-side.
Documentation details for your reference:
Note: This API is available starting Rollbase 5.0 release.
Ah, I should have been more specific.. I was talking about making calls back to Rollbase itself. If it's another system, sure... something like the mentioned API would be helpful.
"Note: This API is available starting Rollbase 5.0 release."