Bug 2123216

Summary:	[RFE] - set default_domain_suffix in sssd.conf
Product:	Red Hat Satellite	Reporter:	Nagoor Shaik <nshaik>
Component:	Authentication	Assignee:	Adam Ruzicka <aruzicka>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.12.0	CC:	aruzicka, mhulan
Target Milestone:	Unspecified	Keywords:	FutureFeature, MigratedToJIRA, UserExperience
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 12:30:27 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 Nagoor Shaik 2022-09-01 05:51:16 UTC

Description of problem:

Setting a default_domain_suffix for IDM based authentication would reduce an effort to type in the @domain while authenticating.


Version-Release number of selected component (if applicable):
Satellite 6.12

How reproducible:


Steps to Reproduce:
1. Configure direct AD authentication or IPA authentication from https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html/administering_red_hat_satellite/configuring_external_authentication_admin#Configuring_Direct_AD_Integration_with_GSS_Proxy_admin
2. Check the /etc/sssd/sssd.conf as no default domain suffix is configured
3. Having this we can query user without a domain suffix.

Actual results:
An end-user would have to type the user syntax to login to Satellite

Expected results:
We can reduce this effort by setting a default_domain_suffix to the current domain that the host is joined to.

Additional info:

Under [sssd] section adding default_domain_suffix = example.com to achieve this

Comment 1 Nagoor Shaik 2022-09-01 05:56:41 UTC

We set the required attributes, so we can add this easily

https://github.com/theforeman/puppet-foreman/blob/e0fc1487740d36a5a308498576836525d3e52de1/manifests/config.pp#L205-L210

Comment 2 Adam Ruzicka 2023-06-13 11:18:06 UTC

Where should the default domain come from? Should the users state in explicitly when running the installer? Should the installer try to derive it from some other parameter?

Comment 3 Nagoor Shaik 2023-06-13 12:15:25 UTC

Assuming they are joining to the same realm, this should be defaulted to domain name of the satellite instance.

Comment 4 Adam Ruzicka 2023-06-13 13:19:29 UTC

Oh, you already opened a PR about that, thank you and sorry about not noticing it earlier.

Comment 7 Eric Helms 2024-05-16 16:17:01 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35832 has been resolved.

Comment 8 Eric Helms 2024-06-06 12:30:27 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 "SAT-" 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.