Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

EGI-InSPIRE:Amb 2013-11-19

From EGIWiki
Revision as of 12:59, 19 November 2013 by Ekarolis (talk | contribs)
Jump to navigation Jump to search

Back to the AMB wiki home page

Activity Reports

NA1

NA2

Technical Outreach to New Communities

NA2.5

  • NILs contacts (wiki, web tables, SSO group validation/updates)
    • user support map contacts/details validation and requests for the updates


AppDB (19/11/2013)

  • Outdated sw items has been enabled into production
  • A monthly email is sent to sw entry owners after 3 years of inactivity.
  • 'Freshness' option has been added to the faceted search mechanism.
  • First steps for personalize the home page of the logged in users, have been made [1].
  • A structure for the Scientific classification API has been proposed to EGI [2]. Waiting for feedback in order to start the implementation.


Ongoing tasks:

  • Integration with the Operation portal secured API, in order to get each user roles (this info will be needed for the VO image lists management)
  • Investigating alternative Authentication mechanisms to cover the login process into our service (Portal + API). The selected approach should offer the ability for the user to login either using his egi sso username/password or his personal certificate. The aim is the final solution to be expandable to third-party authentication sources as well (i.e. facebook etc.)


Next tasks:

  • Fetching user details from VOMS servers about their VO membership.
  • Change the authentication mechanism based on the outcome of the investigation that we are currently performing.
  • Extend the authorization module in our system in order to map VO related permissions to the existed of future user profiles.
  • Implement a separate permissions tab for every registered sw/va item, from where the owner could set/unset by whom the given item will be accessible and/or managed.
  • Extend the software (not the VAs) items metadata in order the user to be able to set the license under which an item is available.

 

 

[1]. https://appdb-dev.marie.hellasgrid.gr/ (... and login)

[2]. https://rt.egi.eu/rt/Ticket/Display.html?id=6245


SA1

SA2

SA4

JRA1

Report: Inspire_jra1_2013-11-19

Participants

Discussion