[AIRAVATA-3019] SEAGrid Desktop Client changes

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.19
• Epic Link: Group based Authorization
• Assignee: Marcus Christie
• Reporter: Marcus Christie
• Created: 12/Apr/19 19:07
• Updated: 20/Nov/19 21:34
• Resolved: 06/Nov/19 21:44

Description

Update the SEAGrid Desktop Client to accommodate group based auth changes.

TODO

• [x] specify group resource profile id in config
  • similar to AIRAVATA-3085
• [ ] check group membership instead of roles
  • not relevant, SEAGrid DC assumes user has privileges
• [x] get last status in array for most recent one
  • verified this is needed
  • similar to AIRAVATA-3089
• [x] setup sftp server in staging environment so that it can be tested
• [x] figure out how to integrate SEAGrid desktop builds with download links in Wagtail CMS
• [x] how much work to query for accessible app module, group resource profile, accessible app deployments, etc.?
  • in ExperimentCreateController
    • Need to switch app interface calls to getAccessibleAppModules
    • Need to add group resource profile picker
    • Need to load compute resources with getApplicationDeploymentsForAppModuleAndGroupResourceProfile
  • this seems fairly doable, if time permitting I'll implement this and we won't need a hard coded group resource profile id
• [ ] Switch to group based auth methods
• [x] Add a login-desktop to Django like the one in PGA to allow the Desktop client to get an access token
• [x] instead of passing less_privileged query param, check to see if user has access to any application modules, like Django does
• [x] implement refreshed-token-desktop in Django

Issue Links

• relates to: AIRAVATA-3084 Update PGA to work with group-based authorization changes