Service access

• Access endpoints
  
• Test and production configuration
• Incident and change notifications

Access endpoints

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

URLs related to OIDC and SAML:

Legacy endpoin​​t

The production endpoint www.ident.nets.eu (91.102.27.92) will stop working after 3rd September 2024. Please make sure to use the new endpoint www.e-ident.nets.eu (91.102.28.77).​

TLS Security

Root ​C​A certificates

The communication with E-Ident is secured using HTTPS. The server certificate used is issued under one of the following Root CAs:​

• DigiCert High Assurance EV Root CA (until 10 April 2024):
  
• https://www.digicert.com/CACerts/DigiCertHighAssuranceEVRootCA.crt.pem
• DigiCert Global Root G2 (​from 10 April 2024):
  
• https://cacerts.digicert.com/DigiCertGlobalRootG2.crt.pem
  

Make sure that at least both these root CAs are trusted in your applications.

TLS communication

E-Ident supports TLS 1.2 in the communication. These ciphers are supported in the communication:

• TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f) ECDH secp256r1 (eq. 3072 bits RSA) FS
• TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030) ECDH secp256r1 (eq. 3072 bits RSA) FS
• TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x9e) DH 2048 bits FS
• TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x9f) DH 2048 bits FS 

Test and production configuration

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

Note: The demo app available in the get started guide will give you access to a common test configuration. This is predefined and can be used to try out the service. It is however recommended to get your own test configuration when you develop and test your own applications.

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. The service(s) to use
3. URLs to your application(s)
4. The eIDs you will use and some info about specific eID settings
5. If using standalone UI or pop-up UI, send Nets support a logo file. The logo file should either be svg or png. We recommend using svg. For png file, the  recommended size is 360 (height) x 200 (width). 
3. Nets support will set up your test configuration and give you the needed credentials (MID and password).

To test your application, 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. The service(s) to use
3. URLs to your application(s)
4. The eIDs you will use and some info about specific eID settings
5. If using standalone UI or pop-up UI, send Nets support a logo file. The logo file should either be svg or png. We recommend using svg. For png file, the  recommended size is 360 (height) x 200 (width).  Let us know if we should reuse the logo from the test setup. 
3. 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.
4. Nets support will set up your production configuration and give you the needed credentials (MID and password). 

Incident and change notifications

Nets sends out e-mail and SMS notifications to customers during on-going incidents and e-mail notifications in case of customer affected changes. Customers are added to our notification lists upon customer test and production configuration. To receive e-mail and/or SMS notifications, send your contact details to our support using the Contact us form.

Nets also sends out monthly SLA reports. If you as a customer wants to receive the report, send your contact details to support using the above form.