Other user authentication workflows
There are two additional methods you can use to authenticate ArcGIS Enterprise users. Both methods require additional ArcGIS Enterprise configuration and the use of ArcGIS APIs for your client-side integration.
- HTTP / Integrated Windows Authentication (IWA): Users authenticate with their Windows login to obtain an access token, which is automatically managed by the client API.
- Public key infrastructure (PKI): Users authenticate with a preconfigured certificate to obtain an access token, which is automatically managed by the client API.
|HTTP / Integrated Windows Authentication (IWA)||Public key infrastructure (PKI)|
|ArcGIS Maps SDK for Kotlin|
|ArcGIS Maps SDK for Swift|
|ArcGIS Maps SDK for Java|
|ArcGIS Maps SDK for .NET|
|ArcGIS Maps SDK for Qt|
|ArcGIS API for Python|
|MapLibre GL JS|
|ArcGIS REST JS|
Also known as HTTP basic, HTTP digest, or Integrated Windows Authentication (IWA); resources are protected by a username + password set on the service and prompted by browser pop-up or session cookie. This method manages user login through Microsoft Windows Active Directory and the user typically manually enters their username + password.
To use Integrated Window Authentication, you will need to configure it in ArcGIS Enterprise.
- ArcGIS Maps SDK for Java
- ArcGIS Maps SDK for .NET
- ArcGIS Maps SDK for Qt
- ArcGIS API for Python
Public key infrastructure (PKI) uses a mathematical cryptography technique to generate a pair of public / private digital keys representing a user, application, or organization. Users authenticate themselves by presenting their digital keys (an automated process handled by the app or web service) and are never issued a username or password. This encrypted value is the only required security measure. Public and private digital keys support authentication and secure communication over insecure networks.