As an administrator of your organization, you determine whether HTTPS is required for all transactions and whether anonymous access is allowed to your portal. You can also configure trusted servers and configure a list of portals with which you want to share secure content. This is a privilege reserved for the administrator role.
Tip:
Visit ArcGIS Trust Center for more in-depth security, privacy, and compliance information.
- Verify that you are signed in as a default administrator or custom role with administrative privileges to manage security settings.
- At the top of the site, click Organization and click the Settings tab.
- Click Security on the left side of the page.
- Configure any of the following security settings:
- Click Save to save the changes you've made.
Policies
Change any of the following policy settings as needed:
- Allow access to the organization through HTTPS only—By default, Portal for ArcGIS enforces HTTPS-only communication to ensure that your organization's data as well as any temporary identification tokens that allow access to your data are encrypted during communications over the Internet. Unchecking this box will allow both HTTP and HTTPS communication. Changes to this setting may affect the performance of the site.
Allow anonymous access to your organization—Keep this box checked to allow anonymous users access to your organization's website. If this box is unchecked, anonymous access is disabled, and anonymous users will not be able to access the website. They will also not be able to view your maps with Bing Maps (if your organization is configured for Bing Maps). If you enable anonymous access (by checking the box), make sure that the groups selected for the site configuration groups are shared with the public; otherwise, anonymous users may not be able to properly view or access the public content of those groups.
- Allow members to edit biographical information and who can see their profile—Keep this box checked to allow members to modify the biographical information in their profile and specify who can see their profile.
- Allow users to create new built-in accounts—Keep this box checked to allow users to create a built-in portal account from the portal sign-in page. Uncheck this box if you are using enterprise accounts or want to create all accounts manually.
Password policy
When members change their passwords, they must conform to the organization's policy. If they don't, a message appears with the policy details. The password policy of the organization does not apply to enterprise logins or app credentials that use app IDs and app secrets.
Click Update Password Policy to configure the password length, complexity, and history requirements for members with built-in accounts. Click Use Default Portal Policy to reset the organization to use the standard Portal for ArcGIS password policy (at least eight characters with at least one letter and one number; spaces are not allowed).
You can specify the character length and whether the password must contain at least one of any of the following: uppercase letter, lowercase letter, number, or special character. You can also configure the number of days before the password expires and the number of past passwords that the member cannot reuse. Passwords are case sensitive and cannot be the same as the user name.
Note:
Weak passwords may not be accepted. A password is considered weak if it's a commonly used password such as password1 or includes repetitive or sequential characters—for example, aaaabbbb or 1234abcd.
Enterprise logins
Use the Set Identity Provider and Get Service Provider buttons to Configure a SAML-compliant identity provider with your portal if you want members to sign in to the portal using the same logins they use to access your enterprise information systems.
Sign in options
If you configured a SAML-compliant identity provider with your portal, you see a Sign In Options section where you can configure the options that appear on the portal sign in page. Click the button next to Either their (idphost) or Portal for ArcGIS account or Their (idphost) account only. For example, if you want all members to sign in only with their login for the SAML-compliant identity provider, click the second button. Otherwise, click the first button to make both options for logging in to the portal available on the portal sign in page.
Access Notice
You can provide a notice of terms to be displayed to all users who access the organization. Once enabled, the message will appear when users first access the portal, and they can only proceed to access the site if they accept the terms of the notice. After acknowledging the notice, they will not be prompted again for the remainder of the browser session.
To enable the access notice for your organization, click Set access notice and toggle on Display access notice. Add the Notice title and Notice text that you want to display. Choose the ACCEPT and DECLINE option if you want users to accept the access notice before proceeding to the site, or select OK only if you want users to only have to click OK to proceed.
Click Save to add the access notice to your organization.
Information Banner
You can use information banners to alert all users who access your organization about your site's status and content. For example, inform users about maintenance schedules, classified information alerts, and read-only modes by creating custom messages to appear at the top and bottom of your site. The banner is shown on the Home, Gallery, Map Viewer, Scene Viewer, Groups, Content, and Organization pages.
Note:
At 10.8 this information banner replaces the workflow to set the classificationBanner property in the configuration file.
To enable the information banner for your organization, click Set information banner and toggle on Display information banner. Add text in the Banner text window and choose a background color and font color. A contrast ratio will appear for your selected text and background color - a contrast ratio of at least 4.5 is recommended to adhere to WCAG 2.1 accessibility standards. You can preview the information banner in the Preview pane.
Click Save to add the banner to your organization.
Trusted servers
For Trusted Servers, configure the list of trusted servers you want your clients to send credentials to when making Cross-Origin Resource Sharing (CORS) requests to access services secured with web-tier authentication. This applies primarily to editing secure feature services from a stand-alone (unfederated) ArcGIS Server or viewing secure OGC services. ArcGIS Server hosting services secured with token-based security do not need to be added to this list. Servers added to the trusted servers list must support CORS. Layers hosted on servers without CORS support may not function as expected. ArcGIS Server supports CORS by default at versions 10.1 and later. To configure CORS on non-ArcGIS servers, refer to the vendor documentation for the web server.
The host names must be entered individually. Wildcards cannot be used and are not accepted. The host name can be entered with or without the protocol in front of it. For example, the host name secure.esri.com can be entered as secure.esri.com or https://secure.esri.com.
Note:
Editing feature services secured with web-tier authentication requires a web browser enabled with CORS. The latest versions of Firefox, Chrome, Safari, and Internet Explorer are CORS enabled. To test if your browser has CORS enabled, open http://caniuse.com/cors.
Allow portal access
Configure a list of portals (for example https://otherportal.domain.com/arcgis) with which you want to share secure content. This will allow members of your organization to use their enterprise logins (including SAML logins) to access the secure content when viewing it from these portals. Portals that your organization collaborates with will be included automatically and will not need to be added to this list. This is only applicable for portals at Portal for ArcGIS version 10.5 and later. This setting is not needed for sharing secured content with an ArcGIS Online organization.
The portal URLs must be entered individually and must include the protocol. Wildcards cannot be used and are not accepted. If the portal being added allows both HTTP and HTTPS access, two URLs need to be added for that portal (for example http://otherportal.domain.com/arcgis and https://otherportal.domain.com/arcgis). Any portal added to the list is validated first and, therefore, must be accessible from the browser.