Nexus' software components have new names:

Nexus PRIME -> Smart ID Identity Manager
Nexus Certificate Manager -> Smart ID Certificate Manager
Nexus Hybrid Access Gateway -> Smart ID Digital Access component
Nexus Personal -> Smart ID clients

Go to Nexus homepage for overviews of Nexus' solutions, customer cases, news and more.

This article gives an overview of the different ways to fetch user data from the customer into the GO Workforce service. There is also information regarding how to federate towards the service with SAML. 

Expand/Collapse All

User catalogue options

These are the options where user data can be fetched from, and then created in the GO Workforce service. See the prerequisites for the respective options.

When using LDAP as a user creation/management option, it is mandatory to install "Nexus Smart ID Agent" inside the network. Read more here: Access local services from Identity Manager in the cloud.

When using API as a user creation/management option, this is REST API based. For more information, see Identity Manager Process REST API.

When using manual and/or CSV as an option for user creation, there are no prerequisites. A template for CSV will be provided by the GO Services team.

User federation options

With SAML (2.0) federation, there is an option to federate the customer Service Provider (SP) with the GO Services Identity Provider (IdP).

Metadata information

  • Metadata information from the customer can be provided via an XML file or manually. 
  • IdP Metadata will be provided from Nexus in a standard SAML XML file.

Required customer information

When federating with SAML, the following information is required from the customer: 

  • Entity ID
  • Service Provider URL

Signed authentication requests

Nexus requires signed authentication requests. To achieve that, the customer must set these values in the customer environment to which the federation shall be done:

  • Sign Assertion: True
  • Signing Digest Method: SHA256
  • Digest Method: SHA256