Bug 32681 – "Bad lockout attempts" should be "Bad login attempts"

Bug 32681 - "Bad lockout attempts" should be "Bad login attempts"


Summary:	"Bad lockout attempts" should be "Bad login attempts"

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UMC - Domain management (Generic)
Version:	UCS 4.2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-09-24 15:07 CEST by Janis Meybohm
Modified:	2020-07-03 20:53 CEST (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Development Internal
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	Usability
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Janis Meybohm

2013-09-24 15:07:37 CEST

Samba Domain Object -> Connection -> "Bad lockout attempts" should be named "Bad login attempts"

Comment 1 Stefan Gohmann

2013-10-10 11:25:39 CEST

Hm, that's the official AD / NT name:
 http://technet.microsoft.com/en-us/library/dd277400.aspx

Comment 2 Stefan Gohmann

2013-10-10 11:58:35 CEST

(In reply to Stefan Gohmann from comment #1)
> Hm, that's the official AD / NT name:
>  http://technet.microsoft.com/en-us/library/dd277400.aspx

OK, as discussed via IRC, it is more the Samba name for it, not the AD name. We should check the AD name and use the AD name.

Comment 3 Arvid Requate

2017-01-18 18:54:40 CET

That technet article refers to "Lockout Threshold" or "Bad logon attempts".

Comment 4 Stefan Gohmann

2017-06-16 20:39:40 CEST

This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.

Comment 5 Ingo Steuwer

2020-07-03 20:53:26 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.