Bug 2152058

Summary:	[DOC] RHEL7 IdM change password expiration
Product:	Red Hat Enterprise Linux 7	Reporter:	Sunny Wu <suwu>
Component:	doc-Linux_Domain_Identity_Management_Guide	Assignee:	lmcgarry
Status:	CLOSED MIGRATED	QA Contact:	ipa-qe <ipa-qe>
Severity:	medium	Docs Contact:	Filip Hanzelka <fhanzelk>
Priority:	medium
Version:	7.9	CC:	rhel-docs, tcapek
Target Milestone:	rc	Keywords:	Documentation, MigratedToJIRA
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-14 15:44:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sunny Wu 2022-12-09 04:34:40 UTC

Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/linux_domain_identity_authentication_and_policy_guide/pwd-expiration

Section Number and Name: 
28.5. Changing Password Expiration Date with Immediate Effect

Describe the issue: 
The chatper of documentation provides ldapmodify command to modify password expiration date of user account. A safer method is to use ipa user-mod <user> --password-expiration=<date>.

In addition, providing command to update directory server conflicts our policy:

https://access.redhat.com/articles/65032

What is *NOT* supported:

- Direct update of IdM directory is NOT supported.
- It needs to be updated using ipa command, Web UI, or Identity Management API.

Suggestions for improvement: 

Additional information:

Comment 4 RHEL Program Management 2023-09-14 13:47:35 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 5 RHEL Program Management 2023-09-14 15:44:34 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.