[
https://issues.apache.org/jira/browse/AIRAVATA-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15613066#comment-15613066
]
Suresh Marru commented on AIRAVATA-2152:
----------------------------------------
[~marcuschristie] this is a legacy technical debt and I am surprised that you
were able to correctly navigate through these convolutions.
Going forward we need to start using the new stand alone User Profile Service -
https://github.com/apache/airavata/blob/master/thrift-interface-descriptions/data-models/user-group-models/user_profile_model.thrift
* When a new user is created (directly in IS or through CI-Logon or other
OpenID Connect providers), we should immediately create a basic profile in
Airavata.
* Also add the user to a basic group (currently done with Roles in IS)
* Use this user profile service unique user id in all catalogs (move the
foreign key constraint from database level to application level enforcement)
We need to brainstorm on a stop-gap solution before we change all
implementations from current experiment catalog user records to User Profile
Service.
> UI for to add compute resource/storage allocations
> --------------------------------------------------
>
> Key: AIRAVATA-2152
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2152
> Project: Airavata
> Issue Type: Bug
> Components: PGA PHP Web Gateway
> Reporter: Marcus Christie
> Assignee: Marcus Christie
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
