Choose timezone
Your profile timezone:
Powered by Indico
v3.3.5
Aktuell finden viele Aktivitäten zu AAI statt.
Es gibt die Helmholtz AAI, HIFIS, PUNCH4NFDI, DAPHNE und AAI-Aktivitäten in Base4NFDI sowie einiges mehr.
Um die verschiedenen Aktivitäten und Interessenslagen einmal zusammen zu fassen und um herauszubekommen, ob wir als Helmholtz eine gemeinsame Sicht auf die Dinge bekommen koennen und ev. hier auch eine zentrale Rolle in Base4NFDI spielen wollen, soll ein Treffen zum Informationsaustausch statt finden.
Terminplanung via
AAI coordination meeting
participants:
- Kilian Schwarz
- Thomas Schoerner-Sadenius
- Sander Apweiler
- Uwe Jandt
- Christiane Schneide
- Anton Barty
- Christoph Wissing
- Achim Streit: excused
- Daniel Mallmann: excused
start 09:18
TOP 1: Base4NFDI
up to November 15 proposals for names for B4NFDI-tec have to be
proposed
As current chair Christian Grimm is being discussed.
Names for Secion Liason Officers are needed up to December 15
This depends on B4NFDI to be funded
Decision will be done on November 4
how much funding is unclear
Christian Grimm is currently responsible for AAI and in HIFIS he is in the advisory board.
He seems to be a good choice
There exists an e-mail from Achim Streit to Thomas Schoerner about the German involvement in AAI
CW knows Ramin from Dortmund
and D-Grid times.
He was the right hand of Uwe Schwiegelsohn
and is now Prof. in Goettingen
TECs should look at proposals and give recommendations.
They will meet 2-4 times per year
Consortia shall propose people.
The question is how to find people
We should include FAIRMAT and MARDI
==>
a second meeting in this round will be planned for middle to end of October
in order to discuss about potential candidates.
We should make sure that people do not define standards without
us being included.
With FAIRMAT and MARDI rather topics should be discussed than people.
TOP2: Technical aspects
Die NFDI Community AAI is being used for NFDI self administration.
There are many community AAIs.
There is no central NFDI AAI, but a federation of community AAIs
Community AAIs can be Unity, or KIT solution based
no Indico IAM is foreseen.
In the end Indigo IAM is just another proxy ?
4 different sofware solutions are recommended
- unity (FZJ) - RegApp (KIT) - AcademicID (GWDG) - didmos IAM (Daasi) All four are so called Proxy-IdP-SP solutions which support OIDC as well as SAML. They all support corresponding standards so that interoperability with other infrastructures as EGI, EUDAT, EOSC is possible.
No expertise about Indigo IAM exists, though,
but WLCG is using that
Is there any chance to make it interoperable ?
technically this is possible via OIDC
but WLCG is not an NFDI consortia.
The point and the challenge have been taken.
The second topic is
the attribute set and community proxies
as well as
interoperability with EOSC.
This is almost ready, but somethings are still missing.
The attribute set can be compared with EOSC AAI attribute comparision.
Most missing features for Indigo IAM
are already on the development list for Unity
and might be available quite soon.
Next release is September 22
CW states that this helps
but we will have shared resources also with WLCG
and there maybe both AAI infrastructures which have to be usable.
Also in terms of HIFIS are we talking about
incompabilities or interconnection issues ?
This can be added to the technical interconnection group
and needs to be incorporated there.
It can be possible to interconnect PUNCH AAI with Indigo IAM.
PUNCH4NFDI should create a shared document where we can list needs
==> this will be done.
but commitments will be difficult to get.
The document should consist of
2 parts:
- general needs to be shared with the participating groups
- more precise requirements for PUNCH AAI, then S. Apweiler can give feedback.
Also high level scientific requirements are needed,
as high level use cases and then break them down to technical requirements
both in 1 document.
We need also to know who does that.
Requirements need be forwarded to B4NFDI ?
The DARSI international commercial organisation
had problems to get funding.
AB agrees on this 2 level approach:
high level needs and technical solutions.
DAPHNE wants to focus on top level requirements.
UJ touched how BASE4NFDI app is structured.
Are there plans for such an application ?
For the call for proposals it
would be nice if we can coordinate these calls in this round.
So far there are no known plans.
Services need potentially to be offered to all of NFDI
AAI group in NFDI: this is the group which made the design which was shared here
Pempe is head of the group.
The people are not exactly the same
as in thesection CI/AAI
==> Sander wanted to do take part here
But he is not joining this meeting regularly.
People from consortia are doing that
and exchange is taking part with the core team.
AAI core team is where S. Apweiler was invited by Marcus Hardt
(Daniel M, Achim S, Philip ? were founders)
including DFN (8-10 people).
These are the technical experts for AAI
with knowledge about European context
==> this group is floating in parallel to infrastructure group (CI/AAI)
NFDI BASE4NFDI IAM is shared by both groups