Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Something has to be arranged to invite people who need access to resources (invites, enrollment). Often there is a need to manage collaboration groups (membership etc).

  • Providing access to invited people to the actual resources currently often takes a relatively long time (need for setting up 'account management', provisioning etc). In addition to web-based services, this also explicitly concerns non-web services for which there are currently no possibilities for federated authentication (think of resources accessed via SSH or WebDAV ).

  • Giving access to a service to non-Dutch researchers and people without an institutional account (eg from companies involved in the research) requires a relatively large amount of work.

  • Group membership can be used to decide on authorization: what is a user allowed to do within a certain service? This requires a solution that can convert the group information into attributes that are subsequently consumed and interpreted by the resources to be shared (eg wikis, compute or data) for authorizing users.

...

  • To ensure that parties who want to share resources can do so by simple connecting the resource to the SCZ proxy. The SCZ solution takes care, amongst others, of making the service available via eduGAIN.

  • Ensure that non-web resources like SSH and WebDav can be approached via federated authentication (eg institutional account) (for the benefits of federated authentication see " Why federative"? ).

  • Provide an environment where institutions and cooperative organisations can quickly request a collaboration group, assign group managers and then manage that group themselves, invite people, etc.

  • To provide a possibility to manage specific attributes per collaborative organisation.

  • To ensure that people without an edu account can also easily be invited and access the resources, where possible with a higher 'Level of Assurance' than with a social identity.

  • To ensure that an institution only has to join the SCZ once in order to give all its researchers (via one or more collaborations) access to the participating services and resources of their collaborations.

To get an extra idea of what SCZ wants to offer for the time being, here we share the 'user stories' (in broad outline) for which we want to offer a solution with SCZ.

...

Wondering how a flow of inviting a user to access via SSH looks like? See the video at the bottom of the End user documentation SCZ COmanage .

Planning / timeline / status

...

Interested or questions? See under ' More information '.

Which technical components are used?

Interested in the components used? See Technical overview or SCZ .

COmanage documentation

Curious about how you can get started in COmanage? We have organised and provide links to End user documentation SCZ COmanage .

Connecting services

On Connecting Services to the SCZ environment you will find information about connecting services to the SCZ infrastructure.

...

We have a mailing list for this project. An archive of previously shared messages can be found via https://list.surfnet.nl/mailman/private/projectscz-fiam . Feel free to sign up for that list via https://list.surfnet.nl/mailman/listinfo/projectscz-fiam . Interested? Ask? Suggestions? Mail with Raoul Teeuwen ( raoul.teeuwen@surfnet.nl ). 

...