Service access

​E-Consent is accessible through Internet. A customer test environment is available as long as you are a customer. At this page you find information about the URLs and IP addresses to the service and how to get your own test and production setup.

​Access point

The general URLs and IP addresses to the customer test and production interface:

​Interface​Host​Internett ​IP address
Customer test​​e-consent-preprod1.nets.eu

​91.102.27.123

91.102.28.50 (coming IP address)

​Productione-consent.nets.eu 91.102.27.124

Security

The communication with E-Consent is secured using HTTPS. The server certificate used is under a DigiCert root
CA: https://www.digicert.com/CACerts/DigiCertHighAssuranceEVRootCA.crt   
Make sure that the root CA is trusted in your applications.

E-Consent only supports TLS 1.2 in the communication.

Test and production configuration

To test the E-Consent service, a customer needs its own test and production configuration.

Test

To setup your test configuration, follow the below steps:

  1. Contact Nets support to request a test access.
  2. Fill out the information requested from Nets support and return to the given address. This includes:
    1. Info about your organisation.
    2. What flow to use, signing or identification.
    3. Redirect URIs to use after signing or identification.
    4. Define text/variables to Consent template
  3. Generate a certificate request. We can offer you to use KeyUtil to generate the certificate request. The KeyUtil tool may be used to generate this.
  4. Nets support will set up your test configuration and give you the needed credentials (MerchantID and certificate).
  5. To test E-Consent with an eID, a set of test users are available here.

 Production

To setup your production configuration, follow the below steps:

  1. Contact Nets support to request production access.
  2. Fill out the information requested from Nets support and return to the given address. This includes:
    1. Info about your organisation.
    2. What flow to use, signing or identification.
    3. Redirect URIs to use after signing or identification
    4. Define text/variables to Consent template
  3. Generate a certificate request. We can offer you to use KeyUtil to generate the certificate request. The KeyUtil tool may be used to generate this.
  4. Dependent on the eIDs available you need to enter into an agreement with the specific eID either through Nets as a partner or directly with the eID.
  5. Nets support will set up your production configuration and give you the needed credentials (MerchantID and certificate).