You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/06/11 20:11:18 UTC

[jira] [Commented] (AIRAVATA-2408) PGA: user profile editor

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

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

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

AIRAVATA-2408 Updating PHP namespace for profile services


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