Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature request] Shibbolize GUI #2

Open
kaizimmer1 opened this issue Nov 28, 2018 · 2 comments
Open

[Feature request] Shibbolize GUI #2

kaizimmer1 opened this issue Nov 28, 2018 · 2 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@kaizimmer1
Copy link

kaizimmer1 commented Nov 28, 2018

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

@ljo ljo self-assigned this Nov 29, 2018
@ljo ljo added the enhancement New feature or request label Nov 29, 2018
@ljo ljo added this to the 2020 milestone Nov 29, 2018
@ljo
Copy link
Contributor

ljo commented Nov 29, 2018

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.

@kaizimmer1
Copy link
Author

kaizimmer1 commented Mar 25, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants