#3357 Support autodiscovered subdomains with application type domains
Closed: wontfix a year ago by pbrezina. Opened 4 years ago by jhrozek.

Currently the application domains support only LDAP provider well. The autodiscovered subdomains of application domains turn into POSIX subdomains.

The tricky part here might be to suggest a naming for the discovered subdomains, because if the default naming derived from the remote domain name is used, the names will clash with potential POSIX subdomains from a POSIX subdomain the application domain inherits from.

Metadata Update from @jhrozek:
- Issue assigned to jhrozek

4 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.15.4

4 years ago

Metadata Update from @jhrozek:
- Issue tagged with: cleanup-future

3 years ago

Metadata Update from @jhrozek:
- Assignee reset
- Issue untagged with: cleanup-future
- Issue set to the milestone: SSSD Future releases (no date set yet) (was: SSSD 1.15.4)

3 years ago

Metadata Update from @thalman:
- Issue tagged with: Canditate to close

a year ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

a year ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/4387

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.