Notes of the EOSC-hub AAI tech-talk, 15/June/2018

<h1>Notes of the EOSC-hub AAI tech-talk, 15/June/2018</h1>

<p>Notes by Gergely Sipos</p>

<h2>Summary of presentations:</h2>

<ul>
    <li>The &#39; AARC AAI proxy architecture&#39; is the way by which EOSC-hub enables user communities to interact with EOSC-hub services. According to this architecture AAI proxies connect user identities (from connected IdPs) - optionally enriched with user profile information (from attribute providers) - and services (connected SPs). IdPs, SPs, attribute providers can be either inside EOSC-hub, outside EOSC-hub (within the &#39;community space&#39;) or mixed.</li>
    <li>There are 4 AAI proxy solutions offered in the project: Check-In; IAM; B2ACCESS; EduTeam. The 4 technology do more-or-less the same, however there are some differences in their functionality; in the level of their integration with IdPs, SPs and attribute providers of EOSC-hub; in their usage conditions. (Note: Check-in and eduTEAMS use COmanage technology)</li>
    <li>There are 5 attribute provider solutions available in the project: Perun, COmanage, Unity IDM, HEXAA, VOMS. Perun is developed by CESNET (a project partner).</li>
    <li>AAI proxies and attribute providers can be deployed by the user community; Or can be operated by EOSC-hub &#39;as a service&#39; for the user community</li>
    <li>AAI proxies use data standards to share and exchange data with each other and with the IdPs, SPs (such as this doc about group information: https://aarc-project.eu/wp-content/uploads/2017/11/AARC-JRA1.4A-201710.pdf)</li>
    <li>Individual presentations followed, describing Check-In; IAM; B2ACCESS; EduTeam and Perun attribute provider technologies</li>
</ul>

<h2>Next steps:</h2>

<ol>
    <li>
    <p>Suggestion from communities: Technology providers to share existing materials (documentation, videos, etc.) about their technology. Add this onto the AAI page in Wiki. --&gt; Nicolas as AAI task leader</p>
    </li>
    <li>
    <p>Suggestion from communities: AAI team to setup a guide page in the EOSC-hub wiki about the AAI proxy architecture and the 4 supported technologies. The page should guide user communities in choosing the most suitable AAI proxy technology and operational model (in-house/aaS). Suggest the page to have a &#39;features table&#39; that highlights the main capabilities of the 4 options --&gt; Nicolas to follow up as AAI task leader</p>
    </li>
    <li>
    <p>WP7-8-9 collect information from their communities about which AAI proxy technology with what deployment option each community prefers to use, or the open questions they still have to decide on a solution. Those that don&#39;t have a preference will have to be provided with a catch-all service by the project. --&gt; Gergely, Claudio, Marcin</p>
    </li>
</ol>

<h2><br>
Initial ideas for the AAI proxy technology features table&nbsp;(Action 2 above):</h2>

<ul>
    <li>Already compatible services (SPs)</li>
    <li>Already compatible identity providers (IdPs)</li>
    <li>Already compatible attribute providers (Comanage and Perun for Check-In)</li>
    <li>Operational mode (in-house / as a Service / both)</li>
    <li>Support for non-web access</li>
    <li>Support for AUP enforcement</li>
    <li>Current user base</li>
    <li>Sustainability (esp. Guarantees for operation&amp;support beyond the project lifetime)</li>
    <li>...</li>
</ul>