Peter,<br><br>Sounds great! Cool, so I will just call it confluence-http-authenticator then for now. There was interest in combining the Jira authenticator here which was based on the Confluence authenticator:<br><a href="https://github.com/UW-Madison-DoIT/jiraRemoteUserAuth">https://github.com/UW-Madison-DoIT/jiraRemoteUserAuth</a><br>
<br>I remember there being some differences when I emailed with John Hare, and I think at the time it was easier for John to just split it off so they had their own version, but I can talk with him again and see if we could combine it once both of us have time to look at it more, though I would hesitate to say that we could or should just combine forces as part of the move and not create a new GitHub project for the existing version. If nothing else, we need somewhere to put the old release jars for the Confluence Shibboleth Authenticator just in case anyone needs them, though I admit that isn't the best reason (mostly it is just trying to be realistic about the time I'll have available between now and February to work on it).<br>
<br>Let me know if you end up becoming a user on GitHub and want to be involved later. We can always use more help, and it is easy to make you a member so you can assist when you have time or want to. Much of the time support has little to do with the code and more to do with either directing people to the right resources (like the shib users list or existing documentation) or someone like Scott Cantor or others on the team replying in tickets to assist people (which will now happen in GitHub, although we might have periodic questions via <a href="http://answers.atlassian.com">answers.atlassian.com</a>, and unfortunately I miss some of those because I don't stay on top of it like I'd like to).<br>
<br>Thanks!<br>Gary<br><br><div class="gmail_quote">On Wed, Jan 16, 2013 at 9:16 AM, Peter Schober <span dir="ltr"><<a href="mailto:peter.schober@univie.ac.at" target="_blank">peter.schober@univie.ac.at</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Gary,<br>
<br>
* Gary Weaver <<a href="mailto:garysweaver@gmail.com">garysweaver@gmail.com</a>> [2013-01-15 17:03]:<br>
<div class="im">> So, given all of that, what if I just created a group in GitHub:<br>
><br>
> <a href="https://github.com/confluence-http-header-authenticator/" target="_blank">https://github.com/confluence-http-header-authenticator/</a><br>
><br>
> and then call the new project "Confluence HTTP Header Authenticator":<br>
><br>
> <a href="https://github.com/confluence-http-header-authenticator/confluence-http-header-authenticator/" target="_blank">https://github.com/confluence-http-header-authenticator/confluence-http-header-authenticator/</a><br>
<br>
</div><div class="im">Maybe also lose the "header" as sooner or later this thing should also<br>
</div>be able to process HTTP request attributes (which is what I think Java<br>
<div class="im">calls environment variables from httpd carried over via AJP).<br>
</div>Which makes it the "confluence-http-authenticator"?<br>
That's all just about the name (also note that the Jira code base<br>
might potentially be moved or merged there as well).<br>
But I'm not a github user at this time and I'm not (anymore) in charge<br>
of running a shibbolized Confluence and Jira. So don't expect anything<br>
from me personally,<br>
<div class="HOEnZb"><div class="h5">-peter<br>
<br>
--<br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a><br>
</div></div></blockquote></div><br>