Home
SMP Configurations after Installing Innovapptive Products
This section guides you with the required SMP Configurations after installing Innovapptive Mobile Products.
Authenticate users using LDAP Server
Authenticate an end user using LDAP Authentication and manage communication between SMP and Gateway system using HTTPs ports.
LDAP Authentication with SSO2 Generator

Title and Copyright
Copyright and Terms of Use for the Post Install or Post Upgrade Configurations Guide for mAssetTag, mWorkOrder, mInventory, mServiceOrder, mWorkList and all other solutions of Connected Workforce Platform^TM.
Preface
Understand audience, know related documents and products and conventions followed in this document.
Post-Install or Post-Upgrade Configurations for Innovapptive Products
This guide contains instructions for post install or post upgrade configurations for both SCP and SMP environments. Depending on the platform you are on, choose your configuration path.
SCP Configurations after Installing Innovapptive Products
This section guides you with the required SCP Configurations after installing Innovapptive Mobile Products.
SMP Configurations after Installing Innovapptive Products
This section guides you with the required SMP Configurations after installing Innovapptive Mobile Products.
- Access SMP Management Cockpit
  Use SMP Management Cockpit to deploy, manage, and monitor SMP-based applications, user registrations, and device connections.
- Define Application Authentication
  Define authentication for your applications that are being deployed on SMP.
- Authenticate users using HTTP Authentication
  Configure Innovapptive products on SMP Server and set up HTTP communication between SMP and Gateway System.
- Authenticate users using HTTPs Authentication
  Set up HTTPs communication between SMP and Gateway System.
- Authenticate users using LDAP Server
  Authenticate an end user using LDAP Authentication and manage communication between SMP and Gateway system using HTTPs ports.
  - LDAP Authentication with SSO2 Generator
    - Generate certificate for SSO2 Generator (DSA)
    - Import ‘smp_sso2.p12’ certificate to SMP
  - Import DSA certificate to GW Sandbox
  - Create security profile for LDAP Authentication
  - Create an Application using LDAP Authentication
    Learn how to create an Application using LDAP Authentication
  - Test LDAP authentication using REST client
- Authenticate users using SAML Authentication
  Authenticate an end user using SAML/ADFS Server and manage communication between SMP and Gateway system using HTTPs ports.
- Authenticate users using X.509 Authentication
  Authenticate an end user using X.509 Server and manage communication between SMP and Gateway system using HTTPs ports.
- Integrate SMP with Azure AD
- Configure Push Notifications for SMP
  Field workers gets an alert when an item to which he /she is tagged to is created or modified. However, if the app is not launched on the device, they do not receive these alerts. You must configure Push Notifications to send the alerts to the workers even when the app is not opened in the device.
- Manage Resource File in SMP
  Resource File in SMP helps you centrally administer and manage common settings.
Configure Roles and Authorization for Products
Configure roles and provide authorizations to do tasks using Innovapptive products.

LDAP Authentication with SSO2 Generator

From SMP 3 server Service Pack 8 onwards, SMP uses SAP logon tickets to authenticate a user to a backend system. Also called as SAPSSO2 or MYSAPSSO2 cookies, SAP logon tickets are generated by SMP for an authenticated user and attached to requests going to backend system.

The authentication provider, SAPSSO2 Generator is used only in combination with other providers such as HTTP/HTTPs Authentication, LDAP, and SAML.

As there is no user mapping in SMP, the username authenticated in SMP must also exist in the backend system. User is authenticated using LDAP server and then the user details are posted to SAP backend using SSO2 Generator. To do this, a keypair is required to sign SAP logon tickets.

Note: This key must be a Digital Signature Algorithm (DSA) key as RSA is NOT supported.

Use OpenSSL to create a self-signed certificate.