You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
i know it will be a lot of work if the aggregator had to communicate via shibboleth to its endpoints. But maybe as a starting point it would be enough to just shibbolize the aggregator GUI and do whitelisting IPs from the endpoints? That way we could add more endpoints which are bound by contracts.
Thanks,
Kai
The text was updated successfully, but these errors were encountered:
The whitelisting can be investigated since this feature request is on the road map already. I know you volunteered to do the initial investigations. So we start there.
To give you an update on the initial investigations: there would be about 30 corpora from HZSK and about 5 corpora from BBAW additionally available from german CLARIN-D centers if IP-whitelisting at the FCS aggregator/endpoint backend and a shibbolized FCS aggregator GUI were available.
Hi,
i know it will be a lot of work if the aggregator had to communicate via shibboleth to its endpoints. But maybe as a starting point it would be enough to just shibbolize the aggregator GUI and do whitelisting IPs from the endpoints? That way we could add more endpoints which are bound by contracts.
Thanks,
Kai
The text was updated successfully, but these errors were encountered: