Changes between Version 14 and Version 15 of Software
- Timestamp:
- 07/15/16 16:57:19 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Software
v14 v15 58 58 59 59 For a comparison of the structures of the HBP LDAP server and the JSC LDAP server 60 have a look at the diagram /doc/LDAP .dia.61 62 [[Image(LDAP .png, 900px)]]60 have a look at the diagram /doc/LDAP_v2.dia. 61 62 [[Image(LDAP_v2.png, 900px)]] 63 63 64 64 It summarizes the branches of the LDAP … … 67 67 The personal data for the JSC accounts is stored in the d_pers table. 68 68 While the objectclass is used at JSC to decide, to which system an account is joined 69 to, this is more complex for the HBP server. The manager attribute of an account 70 defines, on which site the user can get accounts at all. Moreover, the ismemberof 71 operator is used to determine, on which target HPC system within the site the account 72 should be created. 69 to, this is more complex for the HBP server. The manager attribute is replaced. To 70 determine the sites, a user has access to, use the connection between users and groups 71 via memberUid. The sites for each group can be detected by checking for systems, 72 which have a hbpproject attribute with the group's name. The hbpsite attribute contains 73 the site name, where each HPC system is located. 73 74 74 75 === Account application from user perspective === … … 78 79 [[Image(UseCases.png, 900px)]] 79 80 80 A HBP user needs to apply for an account through the Unified Portal, a81 A HBP user needs to apply for an account through the Collaboratory, a 81 82 web portal for all HBP users, which offers access to all HBP services and 82 83 platforms. The account application leads to an entry in the HBP LDAP server.