Skip to main content

JSON REST Web Services Connector

Introduction

Description

This connector allows the integration with any Web Service able to consume and generate JSON documents through REST communication.

Managed System

Every commercial product or custom web application allows REST communication with JSON documents.

There are a lot of products that use this standard, for instance:

  • JIRA.
  • Oracle Field Service Cloud (OFSC).
  • Office 365.
  • AWS.
  • Google Cloud.

If your system is not in the previous list, it's possible to include it easily!

For more information to check if your system may be synchronized with this connector you do not hesitate to contact us through our Contact form

Prerequisites

It is needed a user with access and permissions to the endpoints and operations required in the scope of the integration.

Also, the documentation, specification, or tutorial of the implementation of the JSON REST Web Service is required to apply the mapping configuration.

Download and Install

This addon is located in the Connectors section and its name is REST (json) plugin.

You can visit the Addons Getting started page for more information about the installation process.

Agent Configuration

Basic

Generic parameters

After the installation of the addon, you may create and configure agent instances.

To configure this JSON REST Web Service Connector you must select "JSON Rest Webservice" in the attribute "Type" of the generic parameters section in the agents' page configuration.

For more information about how you may configure the generic parameters of the agent, see the following link: Agents configuration

image-1658998971348.png

Custom parameters

Below there are the specific parameters for this agent implementation:

Parameter
Description

Server URL

URL of the REST web service.  

Base URL for making calls.

Authentication method

Available options:

  • None: no authentication (User and Password are not used).
  • Basic: it uses the User and Password to generate the authentication token.
  • Bearer token: it is provided by the application to which we are trying to connect.
  • Token: generate a token from a specific authentication URL. It is no longer used.
  • Token oAuth Client Credentials: authenticates based on a client ID and a client secret.
  • Token oAuth Password Grant:  authenticates based on a client ID and a client secret plus a user name and a password.

(*) You can find more information in the Authentication method section.

Enable debug

Two options: "Yes", "No": it enables or not more log traces in the Synchronization Server log
Proxy host

Only when the proxy is needed.
Proxy port

Only when the proxy is needed.
XML Templates

Allows you to add new XML templates with SOAP requests and then configure them at attribute mappings.
Authentication method

None: no authentication is needed. There are no parameters to configure.

image-1658916253736.png

Basic: the username and password are sent with each request.

  • User Name: user to authenticate.
  • Password: the password of the user to authenticate.

image-1658916073500.png

Bearer token

  • Bearer token: this token is provided by the application to which we are going to connect.

image-1658916094610.png

Token: calls the authentication URL with the POST method and with the username and password, and the response will be the token. It is no longer used.

  • User Name: user to authenticate.
  • Password: the password of the user to authenticate.
  • Authentication URL: URL to retrieve the token for the server's authentication (for the "Token" method).

image-1658916132666.png

Token oAuth Client Credentials

  • Authentication URL: URL to retrieve the token for the server's authentication (for the "Token" method).
  • Token attr. output: the value is always access_token.
  • Request parameters:
    • Client ID: it is like the user.
    • Client secret:  it is the password.
    • Scope: it is the permissions.

image-1658916165066.png

Token oAuth Password Grant

  • User Name: user to authenticate.
  • Password: the password of the user to authenticate.
  • Authentication URL: URL to retrieve the token for the server's authentication (for the "Token" method).
  • Token attr. output: the value is always access_token.
  • Request parameters:
    • Client ID: it is like the user.
    • Client secret:  it is the password.
    • Scope: it is the permissions.

image-1658916206788.png

Attribute mapping

This connector can manage users, accounts, roles, groups, and grants.

Note that any changes made to the methods will affect the properties and vice versa.

Methods

This agent allows you to define methods to be called using the defined properties. There are some default methods, but you can customize your own methods.

Default methods:

  • load
  • delete
  • update
  • insert
  • select

For each method, the properties to set up are as follows:

Properties
Description
Path A valid URL to call. This path must be the continuation of the Server URL for making calls.
Method Available methods to call a Rest API (GET, POST, PUT, DELETE, PATCH)
Encoding

The specific type of encoded data that will be used. There are three supported types:

  • application/x-www-form-urlencoded
  • application/json
  • text/xml
XML Template Applies only if it is text/xml. You need to write the name of the corresponding template defined on the XML Templates.
Parameters

Applies with application/x-www-form-urlencoded and application/json

  • You must type which attributes, defined on the System attributes, will be sent.
  •  If none are to be sent, you must write the hyphen character "-".  
  • If nothing is typed, all parameters are sent.
Success HTTP Codes

HTTP codes that should be interpreted as OK. If no code is entered, Soffid will take as valid codes the following:  200, 201, 204 and 404.

If you type the Success HTTP codes, it will be not necessary to type the Failure HTTP codes.


204 201 200
200,212

You can use blanks or commas to separate the codes.
Failure HTTP Codes

Soffid will take by default as failure all codes not indicated in Success HTTP Codes.

If you type the Failure HTTP codes, it will be not necessary to type the Success HTTP codes. 


400 403
403,405, 400

You can use blanks or commas to separate the codes.
Results

Gets the object or object list from the response received. You need to indicate a  JSON attribute name to check and get the data. If this element is not present, or empty, the connector will conclude the user does not exist yet. You can type simple attribute names or even complex scripts.
Pagination URL

Often, the response from the API Rest service does not contain all the data because the data is too large. In these cases, you can use the paging options to request the data in blocks. 

When the response gives us the URL of the next page to fetch, you must type the tag name of this attribute.


return links{"next"};

You have to choose one of the paging methods, using both is not compatible.
Pagination script

Often, the response from the API Rest service does not contain all the data because the data is too large. In these cases, you can use the paging options to request the data in blocks.

You can type a complex script to get the next call that has to be done. There are two available objects:

  • response: JSON response as received 
  • request: allows you to update the attributes and return true if you want to make a new call or false in another case
o = response{"paging"};
if (o{"has_next_page"}) {
  nextPage = o{"page_number"} + 1;
  request.put("page", nextPage);
  return true;
} else { 
  return false;
}

You have to choose one of the paging methods, using both is not compatible.
Condition script Return false if you want to prevent a call.
Optional header

 Use this property to send HTTP header(s).
More than one header can be sent by adding multiple properties Optional Header1.
The value of the header is "HEADER:VALUE", for instance, "Accept:application/json".
Load

image-1658840538394.png

Select

image-1658840570200.png

Insert

image-1658840500870.png

Update

image-1658840611561.png

Delete

image-1658840656509.png

Properties

In this agent, the configuration of the properties attributes is very important due to they define the functionality of the integration:

This agent has five families of properties:

Family
Description
Load Used to retrieve all the objects in the target system
Select Used to retrieve an object in the target system
Insert Used to create an object in the target system
Update Used to update an object in the target system
Delete Used to remove an object in the target system

These families are involved in the following processes:

Process
Families
Reconcile automatic task Load + select
Authoritative automatic task Load + select
Sync new object Select + Insert
Sync updated object Select + Update
Sync deleted object Select + Delete

These are the pictures of the mechanisms used to synchronize objects:

Sync object


Remove object


You can find more information by visiting the Properties attributes page.

Attributes

You can customize attribute mappings, you only need to select system objects and the Soffid objects related, manage their attributes, and make either inbound and outbound attribute mappings.

You may map the attributes of the target system with the Soffid available attributes.

  • For the target system attributes is required to be access to its specification.
  • For the Soffid attributes, you may follow the next link.

For more information about how you may configure attribute mapping, see the following link: Soffid Attribute Mapping Reference

For instance:

As an example, below is how JSON connector will look like in order to manage JIRA accounts:

image-1658843268020.png

Triggers

You can define BeanShell scripts that will be triggered when data is loaded into the target system (outgoing triggers). The trigger result will be a boolean value, true to continue or false to stop.

Triggers can be used to validate or perform a specific action just before performing an operation or just after performing an operation on target objects. 

To view some examples, visit the Outgoing triggers examples page.

Load triggers

You can define BeanShell scripts that will be triggered when data is loaded into Soffid (incoming triggers). The trigger result will be a boolean value, true to continue or false to stop.

Triggers can be used to validate or perform a specific action just before performing an operation or just after performing an operation into Soffid objects. 

To view some examples, visit the Incoming triggers examples page.

Account metadata

Agents allow you to create additional data, on the "Account metadata" tab, to customize the accounts created for that agent. This additional information will be loaded with the agent's information, or calculated as defined in the mappings.
The additional data can be used in both mappings and triggers.

The attributes which you define here will be shown when you click on the proper account, on the Accounts Tabs at user page.

Operational

Monitoring

After the agent configuration you could check on the monitoring page if the service is running in the Synchronization Server, please go to:

Main Menu > Administration > Monitoring and reporting > Syscserver monitoring

Tasks

Authoritative

If you are checked "Authorized identity source", an automatic task to load identities from the managed system to Soffid is available, please go to:

Main Menu > Administration > Monitoring and reporting > Scheduled tasks

    And you will something like "Import authoritative data from <AGENT_NAME>".

    image-1659005841259.png

    You can also run the Authoritative load from the Massive actions tab in the Agent

    image-1659005376643.png

    Reconcile

    If you are configured the "Attribute Mapping" tab with some of our objects: "user, account, role, group or grant", an automatic task to synchronize these objects from the managed system to Soffid is available, please go to:

    Main Menu > Administration > Monitoring and reporting > Scheduled tasks

    And you will do something like "Reconcile all accounts from <AGENT_NAME>".

    image-1659005877627.png

    You can also run the Reconcile from the Massive actions tab in the Agent

    image-1659005620240.png

    Synchronization

    Regarding the synchronization of the objects, there are two possible options:

    • If the "Read Only" attribute is checked in the "Basics" tab (select Yes option), only the changes in the managed systems will be updated in Soffid. We recommend these options until the global configuration of Soffid will be tested.
    • If the "Read Only" attribute is not checked in the "Basics" tab (select No option), all the changes in Soffid or the managed system will be updated in the other. Note that this synchronization must be configured in the "Basic" tab correctly.

    For more information about how you may configure the generic parameters of the agent, see the following link: Agents configuration


    Back to top