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 Mon, 12 Jun 2017 20:46:00 GMT

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

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

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

AIRAVATA-2408 Remove user profile service methods from API


> 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.4.14#64029)

Mime
View raw message