• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

How to protect a WebService?

S

Sincorde

Guest
Hello.

Consider the following scenario:

I have a webservice, for example MyService.asmx, and a Application, for example MyApp.htm.

I want to block the webservice from public access but allow his acces to the application. The application will can access it, but him cannot be accessed by itself from another location.

Is there a way to authorize access from a current domain only or another way?

Thanks.

Vítor.
 
Possible solution

Hello.

Vito, you have already tried to change the permissions of the files of security?
tire of reading the permissions of the user and leave somenete for the user and system administrator.

I do not know if more help will leave here as a possible solution.

[] 's
 
Back
Top