Skip to main content
Hi,

I have migrated Uniface from 9.7 to 10.4 and I'm using a new linux server for Uniface 10.4

Regarding our web application, when I access the URL, the web server requests the new linux server and trying to access the usp. But throwing an error in the webpage : "Security Error" - uspname.operationname cannot be executed from the browser.

The urouter is running fine and the web asv log file (I don't see any error) is also created.

Please note : This is an existing application and it works fine with Uniface 9.7. The same webserver was requesting the old linux server and the response looks fine in the web page. I changed the web.xml with new linux server and port.

Am I missing something with Uniface 10.4 in the new linux server ?


------------------------------
Thanks,
Satheesh MuthuGopal
------------------------------
Hi,

I have migrated Uniface from 9.7 to 10.4 and I'm using a new linux server for Uniface 10.4

Regarding our web application, when I access the URL, the web server requests the new linux server and trying to access the usp. But throwing an error in the webpage : "Security Error" - uspname.operationname cannot be executed from the browser.

The urouter is running fine and the web asv log file (I don't see any error) is also created.

Please note : This is an existing application and it works fine with Uniface 9.7. The same webserver was requesting the old linux server and the response looks fine in the web page. I changed the web.xml with new linux server and port.

Am I missing something with Uniface 10.4 in the new linux server ?


------------------------------
Thanks,
Satheesh MuthuGopal
------------------------------
The one that trips me up most often is that the operation needs to be explicitly set to “Public web” in version 10.0+, this was mostly implied in V9.
Then you’ll need to recompile the signature….

Regards,
Iain
The one that trips me up most often is that the operation needs to be explicitly set to “Public web” in version 10.0+, this was mostly implied in V9.
Then you’ll need to recompile the signature….

Regards,
Iain
For details see:
  • Rocket Uniface Library 10.4 > Uniface 10: Changes per Release > What's New in Uniface 10.3.01

    Security Enhancements: Protected Triggers and Operations

    "Triggers and operations that are exposed to the web cannot be activated over the internet unless they contain an explicit declaration to enable this. In Uniface 9, this behavior could be optionally enforced. In Uniface 10, it is default behavior.


------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland
------------------------------
The one that trips me up most often is that the operation needs to be explicitly set to “Public web” in version 10.0+, this was mostly implied in V9.
Then you’ll need to recompile the signature….

Regards,
Iain
Hi Lain, it helps. Thanks a lot.

------------------------------
Thanks,
Satheesh MuthuGopal
------------------------------
For details see:
  • Rocket Uniface Library 10.4 > Uniface 10: Changes per Release > What's New in Uniface 10.3.01

    Security Enhancements: Protected Triggers and Operations

    "Triggers and operations that are exposed to the web cannot be activated over the internet unless they contain an explicit declaration to enable this. In Uniface 9, this behavior could be optionally enforced. In Uniface 10, it is default behavior.


------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland
------------------------------
Hi Daniel,

Thanks for your reply. it helps.

------------------------------
Thanks,
Satheesh MuthuGopal
------------------------------
Terms & ConditionsAccessibility statement