![]() In most cases, you'll only need to alter values for the userPassword and user parameters. If you only want to use the portal's built-in groups, delete any information in the text box and skip this step. Alternatively, you can update the following sample with group information specific to your organization. To create groups in the portal that use the existing LDAP groups in your identity store, paste your organization's LDAP group configuration information (in JSON format) in the Group store configuration (in JSON format) text box as shown below.If your LDAP is configured to be case sensitive, set the caseSensitive parameter to true. Although you type the password in clear text, it will be encrypted when you click Update Identity Store (below). The account you use for the user parameter needs permissions to look up the email address and user names of users in your organization. "ldapURLForUsers": "ldaps://myLdapServer:10636/dc=example,dc=com", In that case, the URL would look like this: If users exist in multiple OUs, the LDAP URL can point to a higher-level OU or even the root level if needed. In the above example, the LDAP URL refers to users within a specific OU (ou=users). The URL to your LDAP will need to be provided by your LDAP administrator. In most cases, you'll only need to alter values for the user, userPassword, and ldapURLForUsers parameters. If you have previously changed this option to allow both HTTP and HTTPS communication, you must reconfigure the organization to use HTTPS-only communication by following the steps below: Configureīy default, ArcGIS Enterprise enforces HTTPS for all communication. Once you've updated your portal's identity store for either LDAP or Active Directory, you can configure authentication at the portal tier. ![]() ![]() When you use Windows Active Directory, logins are managed through Microsoft Windows Active Directory. When you use LDAP, logins are managed through your organization's LDAP server. You can secure access to your portal using Lightweight Directory Access Protocol (LDAP) or Windows Active Directory. Add organization-specific accounts to your portal.Verify you can access the portal using credentials.Optionally configure additional identity store parameters.Update your organization's identity store.The organization to use HTTPS for all communication
0 Comments
Leave a Reply. |