Bug 1234219

Summary: [WebUI] Error message could be better while adding idrange with untrusted domain name.
Product: Red Hat Enterprise Linux 7 Reporter: Varun Mylaraiah <mvarun>
Component: ipaAssignee: IPA Maintainers <ipa-maint>
Status: CLOSED ERRATA QA Contact: Namita Soman <nsoman>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: cheimes, mkosek, ndehadra, pasik, pvoborni, rcritten, sumenon
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: ipa-4.6.4-1.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-30 10:55:57 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:
Attachments:
Description Flags
Screenshot of adding idrange none

Description Varun Mylaraiah 2015-06-22 05:51:59 UTC 
Description of problem:
[WebUI] Error message could be better while adding idrange with untrusted domain name.

Version-Release number of selected component (if applicable):
ipa-server-4.1.0-18.el7_1.3.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Navigate to "ID Range" page
2. Select Add >> Enter "Range name" >>
   Select "Range type" -> Active Directory domain with POSIX attributes>
   Add "Base ID", "Range size" and 
   Enter untrusted domain name in "Name of the trusted domain" field
3.Hit Add

Actual results:
"invalid 'ID Range setup': SID for the specified trusted domain name could not be found. Please specify the SID directly using dom-sid option."

Expected results:
Specified trusted domain name could not be found.

Additional info:
Actually SID option is now replaced by domain in IPA 4.1 and SID will be automatically resolved from the domain name. so the above error message does not seem appropriate.
Comment 2 Petr Vobornik 2015-06-22 16:05:31 UTC 
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/5078
Comment 4 Petr Vobornik 2017-02-23 16:19:08 UTC 
The bug doesn't have high enough priority in comparison to other IdM bugs/RFEs for 7.4. Moving to next release. Without sufficient justification it can be moved again later.
Comment 6 Christian Heimes 2018-03-15 06:32:39 UTC 
Fixed upstream
master:
https://pagure.io/freeipa/c/a3060b5238cd011b972909322491a3b784e66d0d
Comment 7 Christian Heimes 2018-03-15 09:28:54 UTC 
Fixed upstream
ipa-4-6:
https://pagure.io/freeipa/c/725d081fc132c40c527d49ce93e411f4e72ba29a
ipa-4-5:
https://pagure.io/freeipa/c/f5a2142e2140b421cea52bf589809147415981b2
Comment 10 Sudhir Menon 2018-08-07 09:20:07 UTC 
Created attachment 1473909 [details]
Screenshot of adding idrange
Comment 11 Sudhir Menon 2018-08-07 09:21:06 UTC 
Fix is seen. Sceenshot attached
Verified on Red Hat Enterprise Linux Server release 7.6 Beta (Maipo)  using

ipa-server-4.6.4-3.el7.x86_64
sssd-1.16.2-11.el7.x86_64
389-ds-base-1.3.8.4-9.el7.x86_64
krb5-server-1.15.1-34.el7.x86_64
pki-server-10.5.9-4.el7.noarch
selinux-policy-3.13.1-211.el7.noarch
Comment 13 errata-xmlrpc 2018-10-30 10:55:57 UTC 
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:3187