There is already krbPrincipalExpiration attribute that defines the time after which the principal is not active anymore.

It can be modified on the host entries manually, by setting time in Zulu format (YYYYMMDDHHmmZ):

ipa host-mod foo.bar.z --setattr krbprincipalexpiration=202009290000Z

this would set host/foo.bar.z principal to expire on 00:00 of 2020/09/29 in UTC timezone

Unfortunately, IPA CLI does not allow to search by the principal expiration in host-find or service-find commands.

Since this attribute is not set by default for hosts, it can be then used in cleanup scripts with LDAP searches to match hosts with explicitly set expiration.

For example, I have a host 'client.ipa.test' to which I set krbPrincipalExpiration to 00:00 of 2020/09/29 in UTC timezone:

# ipa host-mod client.ipa.test --setattr krbprincipalexpiration=202009290000Z
-------------------------------
Modified host "client.ipa.test"
-------------------------------
  Host name: client.ipa.test
  Platform: x86_64
  Operating system: 5.7.17-200.fc32.x86_64
  Principal name: host/client.ipa.test
  Principal alias: host/client.ipa.test
  SSH public key fingerprint: SHA256:MmZwEvtbk+JmTij6kU1twCTEZKGgaijyKGNZx9+CNuk root.test-c49dc8 (ssh-dss), SHA256:wHymevFCzMOM2izMawZ+U+5enECUaxjGTuw31uWfPTs root.test-c49dc8 (ssh-rsa),
                              SHA256:qAGO0Yweyh0hxlpNyO/cUYJjiVACndL3+0gZNt9xLeo root.test-c49dc8 (ecdsa-sha2-nistp256), SHA256:I1V7/xsYjxUqeupQuD6NrWoH9hLCAAFw8AqU31yPA34 root.test-c49dc8 (ssh-ed25519)
  Password: False
  Keytab: True
  Managed by: client.ipa.test

The search below would match only those hosts that have expiration time between 00:00 of 2020/09/23 and 00:00 of 2020/10/01 in UTC timezone:

# ldapsearch -Y GSSAPI -b cn=computers,cn=accounts,dc=ipa,dc=test '(&(objectclass=ipaHost)(&(krbprincipalexpiration<=202010010000Z)(krbprincipalexpiration>=202009230000Z)))' fqdn
SASL/GSSAPI authentication started
SASL username: admin
SASL SSF: 256
SASL data security layer installed.
# extended LDIF
#
# LDAPv3
# base <cn=computers,cn=accounts,dc=ipa,dc=test> with scope subtree
# filter: (&(objectclass=ipaHost)(&(krbprincipalexpiration<=202010010000Z)(krbprincipalexpiration>=202009230000Z)))
# requesting: fqdn 
#

# client.ipa.test, computers, accounts, ipa.test
dn: fqdn=client.ipa.test,cn=computers,cn=accounts,dc=ipa,dc=test
fqdn: client.ipa.test

# search result
search: 4
result: 0 Success

# numResponses: 2
# numEntries: 1

Let me know if this helps to define a workaround time being.

I would assume that the hosts that belong to a specific environment can be easily put into a host group.
So then we can have a script or a system role/playbook to reset all the hosts in a specific group making all of them ready for re-enrollment. But this solves the problem of re-enrollment of the same hosts. If we are talking about dead bodies that need cleanup then yes, an attribute with time stamp and some periodic cleanup should solve the problem.

This is a regular request.

Thanks for the help, cu closed the case.

[synced to jira]

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.

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.