Integration using API access keys

An all new feature for those who work with integrating Next® with various business systems. 

When you implement Next® in an enterprise, you mostly use the existing user management infrastructure. Inside a company network, this is typically Active Directory. For this you need the Next® LDAP/AD connector. Secure single sign on (SSO) is then available using Kerberos, when you integrate to Next® features using URL linking. Outside the domain you will need SAML (or OAUTH2). SAML is supported by Next® Enterprise Single Sign On. And soon OAuth2 will be.

For system to system integration, Next® comes with a complete REST API. When you use this API, you provide user id and password as part of the request , and encrypted using https.

Now Next® API Access Keys, allows you to control the integration from within Next®, and thereby improve the security of your entire setup.

Create individual API Access Keys for each integration point. Give the 'secret' key to the external programs. And control from within Next® exactly what can be done using this access point. 


Each integration point is associated with a unique 'secret' key.


Each integration point can be restricted to improve security.


For the techie ones

This is a highly technical matter. We always suggest that you consult our Security Center of Competences before setting up integration.

Additional information

Please refer to the online product guide for additional information on this feature, once it is released.

If you work in a cloud environment or connect to applications outside your own network take a look at  Next® Enterprise Single Sign On -->

Commercial terms and conditions

This feature is available at no additional cost, to users with an active service plan. Any consultancy assistance will be invoiced.

Disclaimer

Despite our best efforts, we may be forced to change both content and expected delivery of future product updates without notice.


Details

Title:

Integration using API access keys

Type:

New feature

Status:

Released 

Release time:

January 2020

Affected products:

Next® Bank Statements
Next® Contracts
Next® Emails
Next® Enterprise Archive
Next® ExCustody
Next® Invoices
Next® Mailroom
Next® Processes

Audience:

Architect
Admin

Classification:

Public

Responsible product manager:

Kim Hellum

Updated:

12.02.2020

By:

Kim Hellum