Administrator
- Administrator
- All Products
ASK INFAPreview
Please log in to access Ask INFA.
ASK INFAPreview
Property
| Description
|
|---|---|
Minimum Password Length
| Minimum password length required for a valid password. Must be a number
between 8 and 25 characters. If the organization uses multi-factor
authentication, the minimum password length is 8 characters.
Otherwise, the minimum password length is 15
characters. |
Minimum Character Mix
| Minimum number of character types required for a valid password.
Passwords can contain a mix of the following character sets:
For example, if you set Minimum Character
Mix to 1, then passwords must contain at least one
of the character sets. If you set Minimum Character
Mix to 2, then passwords must contain at least two
of the character sets. |
Password Reuse
| Controls whether users can reuse passwords.
|
Password Expires
| Determines how often users must reset their passwords.
|
Enable Multi-Factor Authentication | Enables multi-factor authentication for native human users. By
default, multi-factor authentication is enabled when organizations
are provisioned. With multi-factor authentication, native
human users receive a verification code through email when they log
in to the user interface. The email address for each human user must
be valid. Categorize users as human or non-human users on the
Users page. For more information, see
User Administration . |
Session Idle Timeout | Amount of time before a user's session times out due to inactivity. IDMC displays a warning message to the user 60 seconds
before the user is logged out. Default is 30 minutes, which is the
recommended value. |
Authentication Type | Authentication type used after a user logs in. Default is
Session ID . For JWT authentication, select
a duration for tokens to expire. Default is 30 minutes. When
you change the authentication type, the new type takes effect at the
next login. The change doesn't affect sessions that are in
progress. Before you use the JWT authentication type, modify
custom scripts to refresh the tokens before they expire. For
more information, see the JWT Support Knowledge article. Don't use the JWT
authentication type if your organization uses REST V2 Connector to
call IDMC APIs.
|
Use Trusted IP Ranges
| Enables IP address filtering. IP address filtering uses trusted IP
address ranges in addition to account passwords to prevent
unauthorized users from accessing your organization. When you enable
IP address filtering, a user with a valid login must also have an IP
address within the range of trusted IP addresses, or the user can't
log in to your organization. This option applies to all
Informatica clients that connect to IDMC, including human and
non-human users, REST API users, Secure Agents, and Secure Agent
services. When you enable this option, you must also enter one
or more trusted IP address ranges. Use the following
guidelines:
|
Allowed Trusted IP Ranges
| The trusted ranges of IP addresses from which users can log in to access
the organization. IDMC supports IP address formats in IP version 4 (IPv4) and
version 6 (IPv6). Fields for the trusted IP address range appear when
you enable IP address filtering. To enter additional address ranges,
click + . To ensure seamless
communication between resources across both IPv4 and IPv6 networks,
enable a dual stack configuration. For example, if your virtual
machine uses one network type, IPv4 or IPv6, and the servers that
host the connectors use another network type, enable dual stack on
your virtual machine to ensure seamless communication regardless of
their network type. If you enter an
invalid IP address range, users cannot access your organization.
Contact your network administrator for valid IP address ranges.
|
