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 use the same security mechanisms as SOAP Web Services, enabling secure data import through SOAP protocols.Authentication is handled primarily by basic authentication, where the web service user must provide a valid username and password.Additionally, contextual security enforces access control rules on the targeted tables, ensuring users have appropriate permissions.For instances with high security settings, the web service user may also require thesoaprole to successfully interact with import sets.
Show full answerShow less
Security Details
Basic Authentication: Requires valid username and password credentials for the web service user.
Contextual Security: Requires the web service user to comply with access control rules on the queried tables.
Additional Role: In high-security instances, the soap role may be needed for the web service user.
Related Links and Functionality
When viewing a mapped web service table, you can navigate directly to related components such as:
Import Sets: The specific import sets linked to the web service import set.
Transform Maps: The list of transform maps related to the import set for data transformation.
Transform History: Records of past transformations applied.
Edit Web Service: Options to modify the web service configuration.
Practical Example
The documentation includes a detailed example involving a SOAP web service import using a Notification import set:
A sample WSDL defines the structure and operations for the SOAP service.
Sample SOAP envelope and response XML demonstrate the message format for insert operations.
A Perl script example shows how to invoke the SOAP service as the itil user, performing an insert operation to create an Incident record.
The script handles authentication, sends the insert request with parameters, and processes the SOAP response to print the result or any faults.
The outcome of the script is a new Incident record created or updated, with relevant system identifiers returned.
What ServiceNow Customers Can Expect
By leveraging Web Service Import Sets with proper security configurations:
Customers can securely import and transform data into ServiceNow tables using SOAP web services.
Access control and authentication mechanisms help protect data integrity and enforce permissions.
The provided example and related links assist customers in configuring, testing, and managing their web service import sets effectively.
Integration using languages like Perl is supported, enabling automation and external system connectivity.
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.
If your instance uses high security settings, the Web Service user may also need the
soap role.
Web service import sets related links
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.
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
This example demonstrates the WSDL, SOAP envelope and response, Perl invocation, and result of
a SOAP web service import.
<?xmlversion="1.0"encoding="UTF-8"?><SOAP-ENV:Envelope SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><SOAP-ENV:Body><insertResponse><sys_id>b54aafbfc0a8006f0058db95daa5b88d</sys_id><table>incident</table><display_name>number</display_name><display_value>INC10008</display_value><status>ignored</status><status_message>No field values changed</status_message></insertResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>
Example Invocation using Perl
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.
