Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Search for | Example | Results |
---|---|---|
A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Search for | Operator | Example |
---|---|---|
Two or more words in the same topic |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
- Universal CMDB Login Authentication
- Setting Up an Authentication Method
- Enabling Login to Universal CMDB with LW-SSO
- Enabling Login to Universal CMDB with SAML
- Setting a Secure Connection with the SSL (Secure Sockets Layer) Protocol
- Using the JMX Console to Test LDAP Connections
- How to Enable HTTP Communication for Universal CMDB
- Hybrid User Management with Multiple User Repositories
- How to Define LDAP Servers and Enable LDAP Authentication Method
- LDAP Authentication Settings - Example
- Example: How to Configure LDAP for Sun ONE Directory Server in UCMDB Server
- Example: How to Configure Dynamic LDAP Groups
- Retrieving Current LW-SSO Configuration in Distributed Environment
- User Lockout Mechanism
User Lockout Mechanism
The user lockout mechanism allows UCMDB administrators to:
- enable or disable the lockout mechanism
- specify how many failed login attempts are allowed before a user is locked out
- specify the period of time after which the locked accounts will be automatically released
- retrieve a list of locked out users and unlock certain users
In addition, all failed login attempts are logged, and consecutive attempts are reported to the proper security administration personnel in your organization.
The table below describes the infrastructure settings available with the lockout mechanism (Administration > Infrastructure Settings Manager > Security Settings):
Name | Description | Default Value |
---|---|---|
User lockout mechanism enabled | Enable the user lockout mechanism after a number of failed login attempts. Setting the value to false disables this feature. The default value is true. | True |
User lockout timeout value (minutes) | The time value in minutes until the next login attempt can be successfully permitted in case the current user is locked out. | 10 |
The maximum number of failed login attempts prior to a user lockout | The maximum number of failed login attempts before a user enters the timed lock out state. | 3 |
In the JMX console, under Security Services, the following JMX methods can be used for unlocking users:
- retrieveCurrentlyLockedOutUsers. Retrieves a list of the currently locked out users and allows individual unlocking.
- unlockUser. Allows unlocking a certain user that is currently locked out by the login mechanism.
User Lockout Mechanism for the Server Status page, JMX Console, and SDK
When users access the Server Status page, JMX Console, or SDK, they could be locked out if they fail the login authentication for a number of times. You can configure the maximum failed login attempts allowed, maximum lockout time period for them using the following infrastructure settings.
Name | Description | Default Value |
---|---|---|
failed.login.attempts.limit | The maximum number of failed login attempts allowed. | 3 |
invalid.login.expiration.in.minutes | The maximum time period (in minutes) allowed for invalid login attempts. | 15 |
user.blocking.time.in.minutes | The maximum time period (in minutes) that a user is locked out after failed login attempts. | 10 |
invalid.login.lock.out.enabled | Enable or disable the user lockout mechanism for the Server Status page, JMX Console, or SDK. By default it is enabled. | True |
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to cms-doc@microfocus.com.
Help Topic ID:
Product:
Topic Title:
Feedback: