#4486 Hosting request for webauthinfra
Closed: Fixed Opened by adelton.

Project name:
webauthinfra

Project short summary:
Projects and modules related to web authentication, authorization, access control, and identity management

SCM choice (git/bzr/hg/svn):
git (actually, multiple gits -- please see below)

Project admin Fedora Account System account name:
adelton

Would you like a Trac instance for your project?: yes

Do you need a mailing list? If so, comma-separate a list of what you'd like them to be called. Otherwise, put "no":
webauthinfra-list

There are currently couple of Apache modules living in various places: http://fedorapeople.org/cgit/adelton/public_git/mod_authnz_pam.git/, https://fedorapeople.org/cgit/adelton/public_git/mod_lookup_identity.git/, possibly https://github.com/modauthgssapi/mod_auth_gssapi, ... In the future, there might be ngnix modules or other bits.

They are primarily maintained as client side of IPA (www.freeipa.org) technologies but are not limited to IPA setups. We'd like to host these modules under one umbrella on fedorahosted.org to get trac and mailing list for them. However, setting up separate project and trac and mailing list for each of the module seems like an overkill; also, often discussion about one module overlaps with another module, so we feel it makes sense to have them under one umbrella.

At the same time, we'd like the git repos to be independent, as those modules have different authors and release cycles and they do not share anything code-wise.

Would it be possible to have one "webauthinfra" project with trac and mailing list, and then multiple git repositories under it "webauthinfra/mod_authnz_pam", "webauthinfra/mod_lookup_identity", ...?

If that is not doable, should we create independent hosting requests for the modules that would just have git repos and then the umbrella project which would not have git repo but would have the trac and mailing list? If we go this route, will the trac instance be able to link via SHA1 of commits to git repos from those other projects?

Or is there some other way to achieve the setup we'd like?

Thank you for any hint,

Jan


yes, we can do multiple git repos no problem.

Should they all be using the same gitwebauthinfra fas group for access? Or each their own?

trac can talk to multiple git repos fine.

Replying to [comment:1 kevin]:

yes, we can do multiple git repos no problem.

Ah, awesome.

Should they all be using the same gitwebauthinfra fas group for access? Or each their own?

I think we should keep it separated.

trac can talk to multiple git repos fine.

Great.

The git repos that we'd like to have for a start under webauthinfra are mod_authnz_pam, mod_intercept_form_submit, mod_lookup_identity. We will likely add some more later.

ok. And you should be owner of the 3 new fas groups for those? Or is there any different folks for each?

Replying to [comment:3 kevin]:

ok. And you should be owner of the 3 new fas groups for those? Or is there any different folks for each?

Let me be the owner for a start.

oh, I need short descriptions for each of the repos for cgit please.

mod_authnz_pam: Apache module to run PAM authorization on result of other module's authentication; also full Basic Auth PAM provider.

mod_intercept_form_submit: Apache module to intercept application's login form submission and run PAM authentication.

mod_lookup_identity: Apache module to retrieve additional information about the authenticated user.

Done.

Please let us know if you need anything further.

I think I'm all set. Thank you!

Metadata