Bug 1496775
| Summary: | Enterprise principals should be able to trigger a refresh of the trusted domain data in the KDC | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Sudhir Menon <sumenon> |
| Component: | ipa | Assignee: | IPA Maintainers <ipa-maint> |
| Status: | CLOSED ERRATA | QA Contact: | ipa-qe <ipa-qe> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.4 | CC: | fbarreto, ksiddiqu, ndehadra, pasik, pvoborni, rcritten, sbose, tscherf |
| Target Milestone: | rc | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ipa-4.5.4-1.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-04-10 16:46:13 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
Sudhir Menon
2017-09-28 11:43:02 UTC
Fixed upstream master: https://pagure.io/freeipa/c/fe1aad767948f4636c2251b0cf7b6a25f9bf7145 ipa-4-6: https://pagure.io/freeipa/c/f7da70183d0d15e4ee5f8f1023bf5b1697f2d67f ipa-4-5: https://pagure.io/freeipa/c/4e74685b1d6b465cd33aa5a8049db80da51de962 ipa-server-version: ipa-4.5.4-7.el7 Verified the bug on the basis of following observations: 1. Verified that the scenarios mentioned in description and comment2 PASSED successfully. Find Trust domain displays AD subdomain as enabled or disabled, bz1052973 : PASSED Access is rejected for disabled domain, bz1070924, bz1170300 : PASSED 2. Also the regression run for ipa-trust-cli was successful 3. AVC denials during the regression run are tracked in separate bug: BZ#1529845 Thus on the basis of above observations, marking status of bug to "VERIFIED" Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0918 |