[
https://issues.apache.org/jira/browse/AIRAVATA-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16856953#comment-16856953
]
Marcus Christie commented on AIRAVATA-3046:
-------------------------------------------
This turned out to be an issue with Airavata's metadata for this tenant and the
Keycloak configuration for the 'pga' oauth client. Here's what I did to fix
this:
* on the database I added the OAUTH_CLIENT_ID and OAUTH_CLIENT_SECRET to the
experiment_catalog.GATEWAY table for GATEWAY_ID {{scigap}}
{noformat}
MariaDB [experiment_catalog]> select * from GATEWAY where GATEWAY_ID =
'scigap'\G
*************************** 1. row ***************************
GATEWAY_ID: scigap
GATEWAY_NAME: Dev SciGaP
DOMAIN: NULL
EMAIL_ADDRESS: NULL
GATEWAY_ACRONYM: NULL
GATEWAY_ADMIN_EMAIL: NULL
GATEWAY_ADMIN_FIRST_NAME: NULL
GATEWAY_APPROVAL_STATUS: APPROVED
GATEWAY_PUBLIC_ABSTRACT: NULL
GATEWAY_URL: NULL
GATEWAY_ADMIN_LAST_NAME: NULL
IDENTITY_SERVER_PASSWORD_TOKEN: NULL
IDENTITY_SERVER_USERNAME: NULL
GATEWAY_REVIEW_PROPOSAL_DESCRIPTION: NULL
DECLINED_REASON: NULL
OAUTH_CLIENT_SECRET: NULL
OAUTH_CLIENT_ID: NULL
REQUEST_CREATION_TIME: 2019-02-05 18:34:24
REQUESTER_USERNAME: NULL
1 row in set (0.00 sec)
MariaDB [experiment_catalog]> begin; update GATEWAY set OAUTH_CLIENT_SECRET =
'xxxxxxx', OAUTH_CLIENT_ID = 'pga' where GATEWAY_ID = 'scigap';
Query OK, 0 rows affected (0.00 sec)
Query OK, 1 row affected (0.00 sec)
Rows matched: 1 Changed: 1 Warnings: 0
MariaDB [experiment_catalog]> select * from GATEWAY where GATEWAY_ID =
'scigap'\G
*************************** 1. row ***************************
GATEWAY_ID: scigap
GATEWAY_NAME: Dev SciGaP
DOMAIN: NULL
EMAIL_ADDRESS: NULL
GATEWAY_ACRONYM: NULL
GATEWAY_ADMIN_EMAIL: NULL
GATEWAY_ADMIN_FIRST_NAME: NULL
GATEWAY_APPROVAL_STATUS: APPROVED
GATEWAY_PUBLIC_ABSTRACT: NULL
GATEWAY_URL: NULL
GATEWAY_ADMIN_LAST_NAME: NULL
IDENTITY_SERVER_PASSWORD_TOKEN: NULL
IDENTITY_SERVER_USERNAME: NULL
GATEWAY_REVIEW_PROPOSAL_DESCRIPTION: NULL
DECLINED_REASON: NULL
OAUTH_CLIENT_SECRET: xxxxxx
OAUTH_CLIENT_ID: pga
REQUEST_CREATION_TIME: 2019-02-05 18:34:24
REQUESTER_USERNAME: NULL
1 row in set (0.00 sec)
MariaDB [experiment_catalog]> commit;
Query OK, 0 rows affected (0.04 sec)
{noformat}
* Added the *manage-users* role to the 'pga' client in Keycloak
** log into Keycloak
** Select realm *scigap*
** Select *Clients*
** Select *pga*
** Select *Service Account Roles*
** Select *realm-management* from the *Client Roles* dropdown
** Select *manage-users* under *Available Roles* and clicked *Add Selected >>*
For a newly created gateway, Airavata already does this but scigap was created
before the code was in place to add the *manage-users* role to the 'pga' client.
> Error when loging in to the scigap dev environment - user account created is
> new
> --------------------------------------------------------------------------------
>
> Key: AIRAVATA-3046
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3046
> Project: Airavata
> Issue Type: Bug
> Components: Keycloak Authentication, PGA PHP Web Gateway
> Affects Versions: 0.18
> Environment: https://dev.scigap.org/login
> Reporter: Shivam Rastogi
> Assignee: Shivam Rastogi
> Priority: Major
> Attachments: Screenshot from 2019-05-28 12-29-33.png
>
>
> Created a new user and when trying to login - following error is displayed
> but when I click on back button I am already logged into the portal.
>
> !Screenshot from 2019-05-28 12-29-33.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
