airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRAVATA-2408) PGA: user profile editor
Date Sun, 11 Jun 2017 20:12:18 GMT

    [ https://issues.apache.org/jira/browse/AIRAVATA-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16046092#comment-16046092
] 

ASF subversion and git services commented on AIRAVATA-2408:
-----------------------------------------------------------

Commit 3eb804ba597888f4fc7edd94da6a2d1603d1b0ad in airavata's branch refs/heads/develop from
[~marcuschristie]
[ https://git-wip-us.apache.org/repos/asf?p=airavata.git;h=3eb804b ]

AIRAVATA-2408 Adding simple validation query for profile service

This is to prevent getting this error message for stale connections
that have been disconnected on the server:

> The last packet successfully received from the server was 168,524,628
> milliseconds ago.  The last packet sent successfully to the server was
> 168,524,629 milliseconds ago. is longer than the server configured value
> of 'wait_timeout'. You should consider either expiring and/or testing
> connection validity before use in your application, increasing the
> server configured values for client timeouts, or using the Connector/J
> connection property 'autoReconnect=true' to avoid this problem.


> PGA: user profile editor
> ------------------------
>
>                 Key: AIRAVATA-2408
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2408
>             Project: Airavata
>          Issue Type: Bug
>          Components: PGA PHP Web Gateway
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>             Fix For: 0.18
>
>
> Started on this in AIRAVATA-2316 for the old user profile service, now need to integrate
with the new *profile service*.
> User should be taken to the user profile editor on first login to fill out additional
information.
> User's should be able to update:
> * first name
> * last name
> * email address
> * institution
> All of these need to be store in profile service. All of these except institution need
to be also stored in Keycloak.
> Possible problem: what happens if save to one of profile service or keycloak fails? 
We don't want these to become inconsistent.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message