<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font size="-1">Dear all, thanks for your answers!</font></p>
<p><font size="-1">@Alan, @Mike thanks for giving details. I do not
speak in the name of my institution, I am at the step of
exploring a wish of some in my team, which is what can be done
to enable:</font></p>
<p><font size="-1">- a system admin to host a collaborative service
(etherpad, ethercalc, owncloud, etc à la framasoft.org) <br>
- and manage users easily. For this, Oauth was my first best
option.</font></p>
<p><font size="-1">I will explore OpenID and get back to you if I
can figure out how to use it for our use-case.</font></p>
<p><font size="-1">Best regards,</font></p>
<p><font size="-1">Jean-Baptiste Bohuon<br>
</font></p>
<br>
<div class="moz-cite-prefix">Le 12/06/2017 à 20:35, Cantor, Scott a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:61BE8C07-BF52-4A4F-A5C0-1C259C11391C@osu.edu">
<pre wrap="">On 6/12/17, 4:14 AM, "dev on behalf of Jean-Baptiste BOHUON" <a class="moz-txt-link-rfc2396E" href="mailto:dev-bounces@shibboleth.netonbehalfofjean-baptiste.bohuon@inra.fr"><dev-bounces@shibboleth.net on behalf of jean-baptiste.bohuon@inra.fr></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">May I ask if it is in the development roadmap of Shibboleth?
</pre>
</blockquote>
<pre wrap="">
Our roadmap is always publically available and periodically updated. [1] It accurately eflects the state of matters, which is that OIDC support is a resource issue but understood to be a requirement, so it's under Planned, while OAuth in a more general sense would have to be much more defined as a use case to do anything significant, so it's in a looser category.
GEANT has a project to develop OIDC support on top of the V3 code base and the organization the developers work for has committed to at least some period of maintenance and support after the project ends. It is not likely we would do anything until that work is done and being evaluated, no matter what resources we had.
The project team has already spent time in some minor consulting on the design and doing library reviews and will do more as time permits. Beyond that, there are insufficient resources to commit to taking on such a substantial new amount of technical debt, and nobody committing to volunteer to do it for an extended period of time by joining the project, so there is no commitment to ship anything unless something changes, more people join the project, or we drop something.
RENATER, as a consortium member, has a voice in what we do or don't do, and in shaping the financial strategy necessary to do what the members believe is necessary. If you're asking on behalf of a RENATER member organization, that's an avenue to pursue. The members ultimately control what we do.
-- Scott
[1] <a class="moz-txt-link-freetext" href="https://wiki.shibboleth.net/confluence/display/DEV/Project+Roadmap">https://wiki.shibboleth.net/confluence/display/DEV/Project+Roadmap</a>
</pre>
</blockquote>
<br>
</body>
</html>