- URL:
- https://<root>/system/handlers/soap/soaphandlerconfig
- Methods:
GET- Operations:
- Edit SOAP Handlers Config
- Version Introduced:
- 11.0
Access requirements
Required privileges
The Sever Administrator API requires privilege-based access. An administrator must be assigned a specific user privilege, or role, to access any given endpoint. Listed below are the user privileges or roles an administrator can be assigned that provides access to this endpoint. If multiple privileges are listed, only one needs to be assigned to gain access.
Note that administrators assigned a custom role must also have the administrative View all content privilege assigned to them to access the API directory as an administrator.
Tokens
This API requires token-based authentication. A token is automatically generated for administrators who sign in to the Server Administrator API directory's HTML interface. Tokens generated in this way are stored for the entirety of the session.
Those accessing the API directory outside of the HTML interface will need to acquire a session token from the generate operation in the Portal Directory API. For security reasons, all POST requests made to the Server Administrator API must include a token in the request body.
Description
The soaphandlerconfig resource lists the URLs for domains allowed to make cross-domain requests, including SOAP and OGC service requests. If the value for allowed is not updated, no restrictions on cross-domain requests will be made.
Request parameters
| Parameter | Details |
|---|---|
| The response format. The default response format is Values: |
Example usage
The following is a sample request URL used to access the soaphandlerconfig resource:
https://organization.example.com/<context>/admin/system/handlers/soap/soaphandlerconfig?f=pjsonJSON Response examples
The response below demonstrates the default for allowed, which offers no restrictions on cross-domain requests:
{"allowedOrigins": "*"}The response below demonstrates a list of URLs allowed to make cross-domain requests:
{"allowedOrigins": "https://gisserver1.example.com,https://gisserver2.example.com"}