freeipa / freeipa-tools

FreeIPA Developer tools

FreeIPA Server

FreeIPA allows Linux administrators to centrally manage identity, authentication and access control aspects of Linux and UNIX systems by providing simple to install and use command line and web based management tools.

FreeIPA is built on top of well known Open Source components and standard protocols with a very strong focus on ease of management and automation of installation and configuration tasks.

FreeIPA can seamlessly integrate into an Active Directory environment via cross-realm Kerberos trust or user synchronization.

Benefits

FreeIPA:

• Allows all your users to access all the machines with the same credentials and security settings
• Allows users to access personal files transparently from any machine in an authenticated and secure way
• Uses an advanced grouping mechanism to restrict network access to services and files only to specific users
• Allows central management of security mechanisms like passwords, SSH Public Keys, SUDO rules, Keytabs, Access Control Rules
• Enables delegation of selected administrative tasks to other power users
• Integrates into Active Directory environments

Components

The FreeIPA project provides unified installation and management tools for the following components:

• LDAP Server - based on the 389 project
• KDC - based on MIT Kerberos implementation
• PKI based on Dogtag project
• Samba libraries for Active Directory integration
• DNS Server based on BIND and the Bind-DynDB-LDAP plugin

Project Website

Releases, announcements and other information can be found on the IPA server project page at http://www.freeipa.org/ .

Documentation

The most up-to-date documentation can be found at http://freeipa.org/page/Documentation .

Quick Start

To get started quickly, start here: http://www.freeipa.org/page/Quick_Start_Guide

For developers

• Building FreeIPA from source
  • http://www.freeipa.org/page/Build
  • See the BUILD.txt file in the source root directory

Licensing

Please see the file called COPYING.

Contacts

• If you want to be informed about new code releases, bug fixes, security fixes, general news and information about the IPA server subscribe to the freeipa-announce mailing list at https://www.redhat.com/mailman/listinfo/freeipa-interest/ .
• If you have a bug report please submit it at: https://pagure.io/freeipa/issues
• If you want to participate in actively developing IPA please subscribe to the freeipa-devel mailing list at https://lists.fedoraproject.org/archives/list/[email protected]/ or join us in IRC at irc://irc.libera.chat/freeipa

freeipa-tools's Issues

Comit loading breaks when using decorated lines

          Should also add `--no-decorate` here (in a separate commit).  If user git config decorates commit lines with inbound refs, it breaks the commit loading because `COMMIT_RE` does not expect the extra data.

Originally posted by @frasertweedale in #84 (comment)

[RFE] send e-mail about CI failures

Currently the CI failures are not sent to the mailing list. It would be good to send information about failing test automatically so one does not need to go to the web interface to check it.

ipatool: closing issue on pagure fails

While attempting to close the ticket on pagure with ipatool, I got the following error:

Close issue "#6966: Document that port 8080 needs to be open on IPA masters for cert-find"? [y/n] y
Failed to close the issue: change_issue_status() got an unexpected keyword argument 'close_status'
Please close the issue manually

ipatool no longer working on Fedora 31

Traceback (most recent call last):
  File "./ipatool", line 1361, in <module>
    Context(docopt.docopt(__doc__)).run()
  File "./ipatool", line 353, in __init__
    pagure_repository=self.config['pagure-repository']
TypeError: __init__() got an unexpected keyword argument 'pagure_repository'

ipatool is broken with python3-libpagure-0.21-4.fc31.noarch in F31. libpagure 0.22 re-introduced the alias in commit https://pagure.io/libpagure/c/1d9c9b921f65af270561cb782dca46e0cc56dbf1?branch=master . ipatool should use the preferred argument repo_to instead.

Improve readability of GitHub notification mails

It gets pretty tiresome quickly to read through the "user's pull request #XX "Title title title" was VERB" every time, just to get to the VERB. I think something like a table would be better, where you can quickly locate PR ID, title, owner, and action, if necessary. Also putting the verb in subject before the title would be better. Something like this:

sssd PR#14: OPENED (Attempting to create a qualified name from a NULL pointer broke sss_groupadd)
sssd PR#14: COMMENTED (Attempting to create a qualified name from a NULL pointer broke sss_groupadd)
sssd PR#14: +NACK (Attempting to create a qualified name from a NULL pointer broke sss_groupadd)

And the body can look something (not necessarily exactly) like this:

     ID: 14
 Author: jhrozek
Subject: Attempting to create a qualified name from a NULL pointer broke sss_groupadd
    URL: https://github.com/SSSD/sssd/pull/14
 Action: OPENED

The log said:
(Tue Sep  6 15:18:31:935105 2016) [sss_groupadd] [sysdb_timestamp_cache_connect] (0x0400): No timestamp cache for LOCAL
(Tue Sep  6 15:18:31:935255 2016) [sss_groupadd] [sss_names_init_from_args] (0x0100): Using re [(?P<name>[^@]+)@?(?P<domain>[^@]*$)].
(Tue Sep  6 15:18:31:935277 2016) [sss_groupadd] [sss_fqnames_init] (0x0100): Using fq format [%1$s@%2$s].
(Tue Sep  6 15:18:31:935392 2016) [sss_groupadd] [parse_name_domain] (0x0200): Parsed username: group10000
(Tue Sep  6 15:18:31:935418 2016) [sss_groupadd] [ldb] (0x4000): start ldb transaction (nesting: 0)
(Tue Sep  6 15:18:31:935504 2016) [sss_groupadd] [ldb] (0x4000): cancel ldb transaction (nesting: 0)
(Tue Sep  6 15:18:31:935629 2016) [sss_groupadd] [main] (0x0020): sysdb operation failed (12)[Cannot allocate memory]

(note the label alignment)

[ipatool] Don't offer close ticket when backporting

When performing a pr-push with backporting, ipatool should not offer to close the ticket. Pagure tickets should only be closed after the last backport has been pushed.

ipatool sample-config is broken

I cannot create a sample config. The tool requires a config to create an example configuration.

 ./ipatool sample-config
Traceback (most recent call last):
  File "./ipatool", line 1270, in <module>
    Context(docopt.docopt(__doc__)).run()
  File "./ipatool", line 297, in __init__
    with open(os.path.expanduser(options['--config'])) as conf_file:
FileNotFoundError: [Errno 2] No such file or directory: '/home/heimes/.ipa/toolconf.yaml'

ipatool start review doesn;t work

Migration to pagure.io caused that ipatool doesn't support start review command anymore.

Start review will not update ticket manually, this is blocked by pagure.io issue: https://pagure.io/pagure/issue/1500 that prevents to have keys for users, this users cannot add themselves as reviewers

Show changes when PR si edited

When action is edited, github provides diff in json and this can be shown in email

ipatool: Prevent push if Travis CI result is not green

ipatool should refuse to push PR if Travis CI result is not green. However a special option can be provided to override this and allow to push PR in special cases.

[RFE] send information against which branch PR was created

See subject.

Resolve merge conflicts with 3-way merge

ipatool doesn't allow 3-way merge to resolve merge conflicts:

$ ./ipatool pr-push 1363 -r abok
Reviewer: Alexander Bokovoy <[email protected]>
Will apply 1 patches to: master
Fetching...
Aplying to master: Replace nose with unittest and pytest
git am
Applying: Replace nose with unittest and pytest
Patch failed at 0001 Replace nose with unittest and pytest
The copy of the patch that failed is found in: .git/rebase-apply/patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
error: patch failed: ipatests/test_webui/ui_driver.py:220
error: ipatests/test_webui/ui_driver.py: patch does not apply
→ 128
Command failed

The same merge works fine with rebase:

$ git rebase upstream/master 
First, rewinding head to replay your work on top of it...
Applying: Replace nose with unittest and pytest
Using index info to reconstruct a base tree...
M       ipatests/test_webui/ui_driver.py
Falling back to patching base and 3-way merge...
Auto-merging ipatests/test_webui/ui_driver.py

PR freeipa/freeipa#1363