The portal security model in ArcGIS protects data, services, and applications. It includes security controls to prevent unauthorized access. It ensures the confidentiality, integrity, and availability of geospatial data and applications.
Portal service
The portal service
The key security features the portal service supports are:
Aspect | Description |
|---|---|
| Users (identity) | All members |
| Sharing | There are four different sharing levels for accessing content. This includes owner (private), organization, group, and everyone (public). Learn more here. |
| Authentication | The portal service supports all types of authentication with the use of access tokens |
| Developer credentials | You can create and manage developer credentials |
Additionally, you use the portal service to securely:
- Access content items like web maps
A web map is a map stored as a JSON object that defines properties such as the basemap layer, data layers, layer styles, and pop-up styles. Its JSON structure is defined by the web map specification. , web scenesA web scene is a scene stored as a JSON object that defines properties such as the basemap layer, data layers, layer styles, and pop-up styles. Its JSON structure is defined by the web scene specification. , and feature layersA layer is a reference to a collection of geographic data that is used to access and display data. The data for layers are typically provided by the basemap layer service and data services. . - Share content to specific users or group of users.
- Manage users and groups.
Access content items
To access an item in the portal using the portal service, you can create access tokens
You can get an access token by:
Share content
Sharing in ArcGIS is the process of making geographic content available in both ArcGIS Online and ArcGIS Enterprise. The share setting enables you to determine the accessibility level of an item, thereby securing both the item and its underlying data.
You use the portal service to share an item to:
- Change an item's discoverability
- Configure an item's privacy settings
- Grant access to specific user groups or organizations
- Require access tokens for data services.
Sharing levels
The sharing levels in a portal
The following is a list of the sharing levels available for the different types of ArcGIS products:
- Owner (private): Only the owner has access. The hosted layer (item) and data service are private and will not be visible or accessible to others. A valid access token or scoped API key is required. Learn more about scoping items to an API key in API keys.
Manage users and groups
Using the portal service
Through the portal service, you can create groups to organize content
- Invite members.
- Manage content and membership requests.
- Edit group properties.
- Change sharing settings like update roles, remove members, transfer ownership, and delete groups.
Types of authentication
Portal service
You authenticate to:
- Ensure authorized users can access protected information, location services, and private data.
- Manage users and groups to provide access to resources based on user roles and permissions.
- Enable integration of apps with ArcGIS which allows users to sign in to access resources.
You can use the following authentication options to access items in your portal. Learn more about the differences between the authentication types in Authentication comparison.
Type | Description | Best use |
|---|---|---|
| API key authentication | Involves using a long-lived API key to access ArcGIS resources, granting public-facing apps access to specific services, including private content and client referrers. | * Create personal automation scripts that access the portal service * Quickly and easily generate access tokens * Create long-lived access tokens that remain valid for up to one year. |
| User authentication | Allows users with an ArcGIS account to sign in to an application and access content, services, and resources based on their account type, roles, and privileges. | * Create sign-in apps that require users to authenticate with an ArcGIS account * Create apps that let members of your organization * Access and manage secure items stored in a user's portal |
| App authentication | Grants short-lived access tokens based on application credentials, authorizing apps to access specific resources within ArcGIS Online. | * Create automation scripts that access the portal service * Create public apps * Build apps that access location services |
Developer credentials
To support authentication workflow and manage your custom applications, you create developer credentialsclient ID and client secret are used to securely authenticate your application and obtain an access token.
There are two types of developer credentials: API key credentialsclient_id, client_secret, and redirect URIs. They are a type of developer credential.
| Type of developer credentials | Type of authentication |
|---|---|
| API key credentials | API key authentication |
| OAuth credentials | User authentication App authentication |
Authentication with privileges
Privileges
- Manage content such as create, update, and delete content.
- Manage groups such as create, update, delete groups.
- Share content with groups, organization, or publicly.
- Edit features in hosted feature layers.
- Manage users, configure organization settings (for administrators only).
Privileges are associated with an access token
- Access tokens from API key authentication
API key authentication is a type of authentication that uses an API key to authenticate requests to ArcGIS services and secure portal items. and app authenticationApp authentication is a type of authentication that grants a short-lived access token based on an OAuth 2.0 client ID and client secret, authorizing an application to access ArcGIS services and items. have privileges managed by the developer credentials. - Access tokens from User authentication
User authentication is a type of authentication that allows users with an ArcGIS account to sign into an application and allow it to access ArcGIS content, services, and resources on their behalf. The typical authorization protocol used is OAuth2.0. have privileges based on the a user's ArcGIS account.
REST authentication operations
The following REST operations from ArcGIS REST APIs
Operation | Description |
|---|---|
| Authorize | User authentication starts with the authorization step at the oauth2/authorize/ endpoint. Apps are required to direct users to the authorize REST endpoint. |
| Token | The oauth2/token/ endpoint grants an access token when queried with a valid authorization code, client secret, or refresh token. |
| Generate token | The generate operation create an access token in exchange for user credentials. The access token represents an authenticated user for limited time to all other API functionality. |
ArcGIS accounts
An ArcGIS account
| Product | Account | Subscription | Plan |
|---|---|---|---|
| ArcGIS Location Platform | ArcGIS Location Platform account | ArcGIS Developer subscription | Essentials plan (default) See all plans |
| ArcGIS Online | ArcGIS Online account | ArcGIS Online subscription | See all plans |
| ArcGIS Enterprise | ArcGIS Enterprise account | See all plans |
ArcGIS Enterprise
Some organizations require stricter security measures or do not permit the use of distributed online environments like ArcGIS Online
Portal for ArcGIS is a component of ArcGIS Enterprise, allowing organizations to deploy GIS capabilities on their own infrastructure. This deployment supports secure access to maps
For more information about how ArcGIS Enterprise and Portal for ArcGIS can meet your organization's security needs, visit the ArcGIS Enterprise product page.