GakuNin VO Platform GakuNin mAP - Takeshi NISHIMURA (GakuNin, NII, - - PowerPoint PPT Presentation

gakunin vo platform gakunin map
SMART_READER_LITE
LIVE PREVIEW

GakuNin VO Platform GakuNin mAP - Takeshi NISHIMURA (GakuNin, NII, - - PowerPoint PPT Presentation

GakuNin VO Platform GakuNin mAP - Takeshi NISHIMURA (GakuNin, NII, Japan) TERENA VAMP workshop, Utrecht 2012.09.07 is an academic access federation in Japan, since 2010. *1 Current status: # of IdPs 42, # of IDs ~ 50k # of


slide-1
SLIDE 1

GakuNin VO Platform – GakuNin mAP -

Takeshi NISHIMURA (GakuNin, NII, Japan) TERENA VAMP workshop, Utrecht 2012.09.07

slide-2
SLIDE 2

is an academic access federation in Japan, since 2010. *1

 Current status:

# of IdPs – 42, # of IDs ~ 50k # of SPs - 89

 Continuously extending federation functionality

e.g. uApprove.jp, GakuNinDS, …

*1 – https://www.gakunin.jp/en/

slide-3
SLIDE 3

 Our VO Platform: GakuNin mAP

(mAP = member Attribute Provider)

 Provides membership information of groups to

services within our federation.

 It is only one entity in the federation.

 Each university does not have own entity of mAP.

(Though it is not forcible, just recommended)

 All groups are stored in this entity.

 It accepts any request of all SPs in the federation.

 various SPs, including unknown/unfamiliar SPs

 Currently it has no connector for external LDAP etc.

slide-4
SLIDE 4

 For example,

 E-book services which have contracts with small

groups

 Mailing list provider for various groups  File sharing service for communities

and any other services utilizing the concept of “group of IDs” including lightweight collaboration

slide-5
SLIDE 5

 e.g. laboratories in universities,

inter-university research groups, …

 Used by various SPs (groupware, e-Journal, …)

 each SP has a different aim  collaboration works are usually so complicated

― i.e. only 1 SP will not suffice

slide-6
SLIDE 6

 Traditional federation contains only IdPs and

SPs

 Access control is basically based on the attributes

from an IdP

 source of ID group information

 IdP-led groups

 constructible by the information which IdP has

 SP-led groups

 constructible by the information which SP has  theoretically possible but with much cost

 Third-party led groups

 constructible by the information which another entity has

slide-7
SLIDE 7

 Predefined IdP attributes are coarse-grained.

 e.g. eduPersonAffiliation and organizationalUnitName

 IdP administrators cannot handle all of them in ID management system.

 e.g. members of a laboratory, a joint research project, ...

→ There should exist another entity to handle them in the federation.

– Attribute Provider (AP)

slide-8
SLIDE 8

 Goal of our VO platform:

Widely-used & user-friendly VO platform

1.

Lightweight integration

2.

Controlled user consent

slide-9
SLIDE 9

 SimpleAggregation (Shibboleth SP built-in)

 back-channel communication just after authn. by

IdP

 just adding a few lines into SP’s configuration file

 People API / Group API (optional)

 for e.g. mailing list service

slide-10
SLIDE 10

 Which user ID do we use?

 ePPN (eduPersonPrincipalName)

 Which group ID do we use?

 specific URI

e.g.

 “gakuninhelp” group in GakuNin mAP

= https://map.gakunin.nii.ac.jp/gr/gakuninhelp

 administrators of “gakuninhelp” group

(is virtually a group) = https://map.gakunin.nii.ac.jp/gr/gakuninhelp/admin

slide-11
SLIDE 11

 VOOT-like simple protocol to retrieve member /

group information*2

 People API  Group API

 But using TLS client certificate authentication

 SP’s certificate in metadata  Even openssl command can be used to retrieve

information.

*2 - https://meatwiki.nii.ac.jp/confluence/x/lwic (in Japanese)

https://map.gakunin.nii.ac.jp/api/people/@me/GROUPID[?lang= NN] https://map.gakunin.nii.ac.jp/api/groups/@me?[lang= NN]

slide-12
SLIDE 12

On the assumption that many SPs exist,

 To avoid unintentional information disclosure

and to prevent malicious SP’s information retrieval

 Much information confuses user.  The flow of the membership information should

be under the control of group administrators

 Then users do consent for limited number of SPs on

mAP in advance.

 avoids back-channel consent issue

by SP Connector

slide-13
SLIDE 13

 provides membership information of groups to

services within an identity federation

SP P

  • Univ. A

IdP A

SP operator Group admin

  • Univ. B

IdP B

  • Univ. C

IdP C Group 1 Group 2 Group 3

GakuNin mAP

services

SP Q

User X isMemberOf: SID-P, GID-2 Access to SP P

SP Connector Q SP Connector P

slide-14
SLIDE 14

SP Connector is a representation of SP in GakuNin mAP, controlled by SP administrator.

 To avoid privacy issues

 GakuNin mAP sends minimum information of groups

which have connections with the SP Connector.

 The connection is built when Group admin and SP

admin agree.

 Then each member does the consent.

slide-15
SLIDE 15

GakuNin mAP

Users

SP SP SP

Member attribute requester Member attribute authority Group management UI

  • Create group
  • Add/remove members
  • Visualize group

connections

  • Store group membership info
  • Retrieve

membership info

like SP like IdP

slide-16
SLIDE 16

1.

“meatwiki” from NII General Wiki service to share information in an arbitrary group

2.

“shibosuke” from a private company Scheduling service among arbitrary group members

3.

“youzan” from Yamagata University Communications service for sharing academic information

4.

“meatmail” from NII Mailing list service

5.

“ARCADE” from Kanazawa University File sharing with group permission

slide-17
SLIDE 17

 IdPs in Japan do not want to release ePPN to

each SP. (due to privacy)

 Contract-base SPs does not need ePPN.  Read access on Wiki does not need ePPN.

Front Channel Aggregation*

instead of SimpleAggregation * needs Shibboleth SP modification

slide-18
SLIDE 18

 Inserts second authentication request just after

normal authentication.

 Each SP needs no NameID.

SP mAP(IdP) mAP(SP) University IdP

  • authn. request (normal flow)
  • authn. response (normal flow)

second authn. request IdP’s entityID isMemberOf retrieve group info. ePPN (for mAP) second authn. request from mAP

slide-19
SLIDE 19

Thank you for your attention