coreos / coreos/fedora-coreos-docs

[Request] Document using SSSD LDAP auth against FreeIPA

Open
#77 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
68
Forks
156
Avg merge
14d 2h
Merged PRs (30d)
1

Description

I've been trying to use FreeIPA Container to manage some new infrastructure using FCOS as the primary platform. I found this comment on the fedora-coreos-tracker issues that provided some of the info, and I added some bits that seem to be required from other reading I've done.

The result, is the fcct snippet that is attached.

fcct-sssd_freeipa-snippet.yml.txt

This configuration results in a somewhat working sssd. If I'm logged in as the core user, I can successfully get some information, but not everything.

[core@example-0 ~]$ id dcode
uid=1024800001(dcode) gid=1024800001(dcode) groups=1024800001(dcode)
[core@example-0 ~]$ getent passwd dcode
dcode:*:1024800001:1024800001:Derek Ditch:/home/dcode:/bin/sh
[core@example-0 ~]$ getent group dcode
dcode:*:1024800001:
[core@example-0 ~]$ getent group admins
admins:*:1024800000:
[core@example-0 ~]$ sss_ssh_authorizedkeys dcode
Error looking up public keys

Since sssd is clearly in the platform for this explicit purpose, can we get a working example against FreeIPA? and maybe some people might be interested in AD or something.

Thanks!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the attached fcct-sssd_freeipa-snippet.yml.txt and the linked Fedora CoreOS tracker comment to understand the current SSSD and FreeIPA configuration. Document a working FreeIPA example for Fedora CoreOS, including the behavior shown by the id, getent, and sss_ssh_authorizedkeys commands; broader AD coverage is optional in the request.

Written by the indexing model from the issue text.

Assessment

Domain
authentication, documentation, operating-systems
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.