Authentication tab
In this tab, you select and configure an authentication protocol.
- Microsoft Entra ID authentication
-
Microsoft Entra ID is a centralized identity provider. Microsoft Entra ID enables you to use multifactor authentication, as well as Single Sign-On (SSO).
- JSON web token (JWT) authentication
-
JSON web-based token authorization (JWT) allows the user to access routes, services, and resources that are permitted with that token. This authorization is required if you want to enable your API with Authentication.
- Lightweight Directory Access Protocol (LDAP) authentication
-
Lightweight Directory Access Protocol (LDAP), is a well-supported standard-based mechanism for interacting with directory servers. You can use it for authentication processes.
- OAuth2 authentication
-
OAuth 2.0 is the industry-standard protocol for authorization. OAuth 2.0 focuses on client developer simplicity and provides specific authorization flows for web applications, desktop applications, mobile phones.
- OpenID Connect authentication
-
The OpenID connect authentication is an authentication method implemented into the Neptune DXP platform. It is the factory standard for handling authentication and covers everything from web applications to native applications.
- SAML authentication
-
Security Assertion Markup Language (SAML) provides a secure method of passing user authentication and authorization between identity provider and service providers.
- Neptune DXP - SAP Edition authentication
-
The Neptune DXP - SAP Edition authentication provides a one-to-one connection between the Neptune DXP - Open Edition system and Neptune DXP - SAP Edition, and thus the SAP system when it is running. This provides the ability for end users to log into Neptune DXP - Open Edition using their SAP credentials. When successful, a paired user is created within Neptune DXP - Open Edition.
SAML is only for browser login, not for Mobile Client or PWA.