[jira] [Comment Edited] (AIRAVATA-2204) User Profile thrift service for New Registry CPI
[ https://issues.apache.org/jira/browse/AIRAVATA-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15872262#comment-15872262 ] Anuj Bhandar edited comment on AIRAVATA-2204 at 2/17/17 6:31 PM: - No [~smarru], This is just a simple User Profile Service with crud operations with its own registry, I am waiting for [~scnakandala] 's changes to group and sharing registry, will merge once he finishes it was (Author: anujbhan): No Suresh, This is just a simple User Profile Service with crud operations with its own registry, I am waiting for [~scnakandala] 's changes to group and sharing registry, will merge once he finsihes it > User Profile thrift service for New Registry CPI > > > Key: AIRAVATA-2204 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2204 > Project: Airavata > Issue Type: Task >Reporter: Anuj Bhandar >Assignee: Abhijit Karanjkar > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AIRAVATA-2204) User Profile thrift service for New Registry CPI
[ https://issues.apache.org/jira/browse/AIRAVATA-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15872262#comment-15872262 ] Anuj Bhandar commented on AIRAVATA-2204: No Suresh, This is just a simple User Profile Service with crud operations with its own registry, I am waiting for [~scnakandala] 's changes to group and sharing registry, will merge once he finsihes it > User Profile thrift service for New Registry CPI > > > Key: AIRAVATA-2204 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2204 > Project: Airavata > Issue Type: Task >Reporter: Anuj Bhandar >Assignee: Abhijit Karanjkar > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AIRAVATA-2079) Email notifications when a gateway request status changes
[ https://issues.apache.org/jira/browse/AIRAVATA-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma reassigned AIRAVATA-2079: --- Assignee: Anuj Bhandar (was: Nipurn Doshi) > Email notifications when a gateway request status changes > - > > Key: AIRAVATA-2079 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2079 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.17 >Reporter: Eroma >Assignee: Anuj Bhandar > Fix For: 0.17 > > > Gateway provider should receive email notifications when > 1. The gateway request is approved and available to download credentials. > 2. Gateway request is denied. > SciGaP admin should get notifications when > 1. Gateway request is created. > 2. When the request is CANCELLED by the provider -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AIRAVATA-2079) Email notifications when a gateway request status changes
[ https://issues.apache.org/jira/browse/AIRAVATA-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma updated AIRAVATA-2079: Fix Version/s: 0.17 > Email notifications when a gateway request status changes > - > > Key: AIRAVATA-2079 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2079 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.17 >Reporter: Eroma >Assignee: Nipurn Doshi > Fix For: 0.17 > > > Gateway provider should receive email notifications when > 1. The gateway request is approved and available to download credentials. > 2. Gateway request is denied. > SciGaP admin should get notifications when > 1. Gateway request is created. > 2. When the request is CANCELLED by the provider -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AIRAVATA-2222) Existing .chk file is not copied back to the working directory.
[ https://issues.apache.org/jira/browse/AIRAVATA-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma updated AIRAVATA-: Fix Version/s: 0.18 > Existing .chk file is not copied back to the working directory. > --- > > Key: AIRAVATA- > URL: https://issues.apache.org/jira/browse/AIRAVATA- > Project: Airavata > Issue Type: Bug > Components: Airavata System, GFac > Environment: dev.seagrid.org >Reporter: Eroma >Assignee: Shameera Rathnayaka > Fix For: 0.18 > > > When there is already a .chk file for the user for gaussian it is not copied > to the working directory. > for this experiment Clone_of_Gaussian_C1_68e5705a-dcaf-4f40-85e2-6106c47afb59 > the existing .chk file is not in the working directory. > User ProdE2017 launched two gaussian experiments and the .chk created and > copied to central location is not copied in this experiment. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AIRAVATA-2106) Add content to 'Help' menu item in SEArid desktop
[ https://issues.apache.org/jira/browse/AIRAVATA-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma updated AIRAVATA-2106: Fix Version/s: 0.18 > Add content to 'Help' menu item in SEArid desktop > - > > Key: AIRAVATA-2106 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2106 > Project: Airavata > Issue Type: Task >Reporter: Eroma >Assignee: Sudhakar Pamidighantam > Fix For: 0.18 > > > Currently when clicked on' About' in Help menu it goes to Information dialog > but it does not contain any infromation useful to the client user. > Suggestions > 1. Links to user guide > 2. FAQs -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AIRAVATA-2214) When a gaussian application executed for the second time a new .chk file is created. The existing in central directory for the user is not replaced.
[ https://issues.apache.org/jira/browse/AIRAVATA-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma updated AIRAVATA-2214: Fix Version/s: 0.18 > When a gaussian application executed for the second time a new .chk file is > created. The existing in central directory for the user is not replaced. > > > Key: AIRAVATA-2214 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2214 > Project: Airavata > Issue Type: Bug > Components: GFac, PGA PHP Web Gateway > Environment: https://dev.seagrid.org >Reporter: Eroma >Assignee: Shameera Rathnayaka > Fix For: 0.18 > > > When we run a subsequent Gaussian job the created checkpoint file should > replace the existing in the central location for the user. > But instead a new .chk file is created and now there are two .chk files. > Always at a given time there should be only a single .chk file. > Immediate previous one should be renamed as a backup and every time a new > .chk file is created the existing one should replace the backup and the new > should replace the current. > Hope this is not confusing! -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (AIRAVATA-2265) in SciGaP latest record should be on top of the list in Gateway requests.
[ https://issues.apache.org/jira/browse/AIRAVATA-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-2265. --- Tested and verified in https://dev.scigap.org > in SciGaP latest record should be on top of the list in Gateway requests. > - > > Key: AIRAVATA-2265 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2265 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway > Environment: dev.scigap.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.18 > > > Currently in Gateway requests page displays the REQUESTED gateway requests > but the latest is at the bottom. Please show the latest on top of the list > for all status categories. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (AIRAVATA-2267) In view credential please show the domain.
[ https://issues.apache.org/jira/browse/AIRAVATA-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-2267. --- Tested and verified in https://dev.seagrid.org > In view credential please show the domain. > -- > > Key: AIRAVATA-2267 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2267 > Project: Airavata > Issue Type: Bug > Environment: dev.scigap.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.18 > > > Gateway provider need to add the domain to the pga_config. So after the > gateway request is approved please display the domain in 'View Credentials' -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AIRAVATA-2323) Django PGA: WSO2 IS authentication
[ https://issues.apache.org/jira/browse/AIRAVATA-2323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871946#comment-15871946 ] Marcus Christie commented on AIRAVATA-2323: --- I'm going to try creating my own authentication backend. I think this will be better for a few reasons: * all of these Django apps, like python-social-auth, would require writing some code. There isn't really an off the shelf solution. * python-social-auth seems relatively complex to configure. I'm not sure it would be faster to use. * creating our own authentication backend will give us more flexibility going forward. > Django PGA: WSO2 IS authentication > -- > > Key: AIRAVATA-2323 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2323 > Project: Airavata > Issue Type: Bug >Reporter: Marcus Christie >Assignee: Marcus Christie > > Enable OpenID Connect code flow from Django to WSO2 IS. > The current PGA does an OAuth password flow but for the Django based PGA > we'll do a code flow. We essentially need to support code flow anyhow to > support CILogon. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AIRAVATA-2326) PGA: handle multiple file uploads that together exceed post_max_size
Marcus Christie created AIRAVATA-2326: - Summary: PGA: handle multiple file uploads that together exceed post_max_size Key: AIRAVATA-2326 URL: https://issues.apache.org/jira/browse/AIRAVATA-2326 Project: Airavata Issue Type: Bug Reporter: Marcus Christie Assignee: Marcus Christie AIRAVATA-1397 added handling for when files are uploaded that exceed upload_max_filesize. However it's possible for multiple files to not exceed upload_max_filesize but when combined together do exceed the post_max_size. Zhong ran into this problem with uploading a couple large files as inputs to the dREG application. One problem with post_max_size is that when it is exceed PHP provides only an empty $_POST variable. So it is pretty hard to gracefully handle when it happens. That said, I think there are a couple of things that can be done: * we can detect when post_max_size is exceed and when it is we can at least display an error message to the user. Right now they just get dumped to the home page without any idea that anything went wrong. * We currently have JavaScript to detect when a file exceeds upload_max_filesize. We could also add JavaScript to run before form submission to check to check all of the files, add up their combined file size and compare with post_max_size -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AIRAVATA-2204) User Profile thrift service for New Registry CPI
[ https://issues.apache.org/jira/browse/AIRAVATA-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871842#comment-15871842 ] Suresh Marru commented on AIRAVATA-2204: [~anujbhan] does this also include the group management and sharing bundled? > User Profile thrift service for New Registry CPI > > > Key: AIRAVATA-2204 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2204 > Project: Airavata > Issue Type: Task >Reporter: Anuj Bhandar >Assignee: Abhijit Karanjkar > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
