Difference between revisions of "EGI-InSPIRE:Amb 2013-11-19"

From EGIWiki
Jump to: navigation, search
Line 7: Line 7:
 
== NA2 == <!-- Sergio -->  
 
== NA2 == <!-- Sergio -->  
  
=== AppDB (19/11/2013) ===
+
== Technical Outreach to New Communities  ==
 +
 
 +
=== AppDB (19/11/2013) ===
  
 
*Outdated sw items has been enabled into production
 
*Outdated sw items has been enabled into production
::*A monthly email is sent to sw entry owners after 3 years of inactivity.
+
 
 +
::*A monthly email is sent to sw entry owners after 3 years of inactivity.  
 
::*'Freshness' option has been added to the faceted search mechanism.
 
::*'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].
+
 
 +
*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.
 
*A structure for the Scientific classification API has been proposed to EGI [2]. Waiting for feedback in order to start the implementation.
  
<o:p>&nbsp;</o:p>
+
&lt;o:p&gt;&nbsp;&lt;/o:p&gt;
  
'''Ongoing tasks:'''
+
'''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)
+
*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.)
 
*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.)
  
<o:p>&nbsp;</o:p>
+
&lt;o:p&gt;&nbsp;&lt;/o:p&gt;
  
'''Next tasks:'''
+
'''Next tasks:'''  
  
*Fetching user details from VOMS servers about their VO membership.
+
*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.
+
*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.
+
*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.
+
*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.
 
*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.
  
'''&nbsp;'''
+
'''&nbsp;'''  
 
 
'''&nbsp;'''
 
 
 
[1]. https://appdb-dev.marie.hellasgrid.gr/ (... and login)
 
  
 +
'''&nbsp;'''
  
 +
[1]. https://appdb-dev.marie.hellasgrid.gr/ (... and login)
  
 +
<br>
  
 +
<br>
  
 
== SA1 == <!-- Malgorzata -->  
 
== SA1 == <!-- Malgorzata -->  

Revision as of 12:21, 19 November 2013

Back to the AMB wiki home page

Activity Reports

NA1

NA2

Technical Outreach to New Communities

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.

<o:p> </o:p>

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.)

<o:p> </o:p>

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)



SA1

SA2

SA4

JRA1

Participants

Discussion