---
sourceDocument: Brazil Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/integrate-applications
Release :
- brazil
ft:locale :
- en-US
ft:publication_title :
- Brazil Workflow Data Fabric
ft:clusterId :
- crint
bundleId :
- crint
workflow :
- Creator
---
# Web service import sets security requirements
# Web service import sets security requirements {#ariaid-title1}
Release version: Brazil
Updated September 10, 2026
 2 minutes to read
Summarize
 Summarized using AI
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.
## Summary of Web Service Import Sets Security Requirements
Web Service Import Sets in ServiceNow leverage the same security mechanisms as SOAP Web Services, enabling secure data import via web services.
This includes basic authentication, which requires a valid username and password, and contextual security, which enforces access control rules on the target table.
For instances with high security settings, the web service user may also need thesoaprole to access the service.
Show full answer Show less
## Security Mechanisms
* **Basic Authentication:** Requires credentials (username and password) for user validation.
* **Contextual Security:** Enforces access control rules based on the queried table, ensuring only authorized access.
* **Additional Role Requirement:** Under high security settings, the web service user may require the `soap` role.
## Related Links and Navigation
When working with a mapped web service table, ServiceNow provides quick access to related components:
* **Import Sets:** Lists import sets associated with the web service.
* **Transform Maps:** Displays transform maps related to the import set for data transformation.
* **Transform History:** Shows the history of data transformations.
* **Edit Web Service:** Allows editing of the web service configuration.
## Practical Example and Usage
The documentation provides a detailed example involving the `Notification` web service import set, illustrating how SOAP messages are structured and processed:
* **WSDL:** Defines the web service interface, including data types and operations.
* **SOAP Envelope:** Shows the format of the SOAP request message to insert data.
* **SOAP Response:** Demonstrates the expected response after processing the SOAP request.
* **Perl Invocation Script:** Example script using the `SOAP::Lite` Perl module to call the web service and insert an Incident record as the itil user, handling authentication and printing results or faults.
* **Resulting Data:** Displays the output on the console and the created record in the ServiceNow import set table.
## Key Benefits for ServiceNow Customers
* Secure integration of external data via SOAP web services using established authentication and access control.
* Visibility into related import sets and transform maps facilitates easier management and troubleshooting of data imports.
* Practical examples and scripts help accelerate implementation and customization of web service import sets.
* Ensures compliance with instance security policies, especially in high-security environments.
Web Service Import Sets use the same security mechanisms as SOAP Web
Services.
* Basic authentication requires a Web Service user provide a valid user name and password.
* Contextual security requires a Web Service user meet the access control rule of the queried table.
{#c_SecurityRequirements__ul_jp1_15y_sp}
If your instance uses high security settings, the Web Service user may also need the
soap role.
## Web service import sets related links {#c_SecurityRequirements__section_lwz_dww_m1b}
When displaying a mapped web service table, you have the following related links.
* Import Sets --- The import sets related to this web service import set.
* Transform Maps --- A list of transform maps related to this web service.
* Transform History --- The transformation history.
* Edit Web Service --- Edit the web service.
{#c_SecurityRequirements__ul_uxz_wgz_sp}
The following image shows a record that was inserted into the web service import set Notification. The target record is the resulting creation or modification to the Incident table record as a result of the transform.Figure 1. Soap Notification
## Web service import sets example {#c_SecurityRequirements__section_bnj_mww_m1b}
This example demonstrates the WSDL, SOAP envelope and response, Perl invocation, and result of
a SOAP web service import.
## Sample WSDL {#c_SecurityRequirements__section_lxq_qww_m1b}
## Sample SOAP Envelope {#c_SecurityRequirements__section_mxq_qww_m1b}
Host 198.10.10.210 is downHGAF76251HGF1
## Sample SOAP Response {#c_SecurityRequirements__section_nxq_qww_m1b}
b54aafbfc0a8006f0058db95daa5b88dnumberINC10008ignoredNo field values changed
## Example Invocation using Perl {#c_SecurityRequirements__section_oxq_qww_m1b}
The following example script uses the Notification web service to create an Incident as the itil user. It uses the Perl language and the SOAP::Lite package.
#!/usr/bin/perl -w
#use SOAP::Lite ( +trace => all, maptype => {} );use SOAP::Lite;
sub SOAP::Transport::HTTP::Client::get_basic_credentials{return'itil'=>'itil';// set basic auth credentials for the itil user
}
my$soap= SOAP::Lite->proxy('http://localhost:8080/glide/imp_notification.do?SOAP');
my$method= SOAP::Data->name('insert')->;attr({xmlns =>'http://www.service-now.com/'});
# insert into the web servicemy@params=( SOAP::Data->name(message =>'problem detected for database DB12DG'));push(@params, SOAP::Data->name(source =>'DB12DG'));push(@params, SOAP::Data->name(uuid =>'HGAF76251HGF2'));
my$result=$soap->call($method=>@params);
print_fault($result);//print any SOAP faults
print_result($result);//print any results
sub print_result {my($result)=@_;if($result->body&&$result->body->{'insertResponse'}){my%keyHash=%{$result->body->{'insertResponse'}};foreachmy$k(keys%keyHash){print"name=$k value=$keyHash{$k}\n";}}}
sub print_fault {my($result)=@_;if($result->fault){print"faultcode=".$result->fault->{'faultcode'}."\n";print"faultstring=".$result->fault->{'faultstring'}."\n";print"detail=".$result->fault->{'detail'}."\n";}}
The following is the result printed by the Perl script on the console.
name=display_value value=INC10011
name=status value=inserted
name=table value=incident
name=display_name value=number
name=sys_id value=cd45649c0a0a0b2b00e6f27649d6bd2c
The following image shows the resultant row created for the import set table Notification (imp_notification).Figure 2. WS Iset Perl