Hi Karan,

It seems this warning message is thrown from
https://github.com/SciGaP/seagrid-rich-client/blob/102c2346e5c8f34bb1226e8270ce29b18ea49eea/src/main/java/org/seagrid/desktop/ui/login/controller/LoginController.java#L232
.

Maybe you can debug that point and check what is the status and
troubleshoot from there onwards.

On Sun, Aug 5, 2018 at 10:32 PM Kotabagi, Karan <[email protected]> wrote:

> Hi All,
>
>
> I have recently up the Airavata in the VM, and I am able to connect it to
> the pga client and run the experiment successfully.
>
>
> Although, I need to connect the same airavata server to the seagrid rich
> client., to achieve this I am trying to change the configurations in the
> seagrid.properties file @ path
> <https://github.com/SciGaP/seagrid-rich-client/blob/master/src/main/resources/seagrid.properties>
> .
>
>
> <https://github.com/SciGaP/seagrid-rich-client/blob/master/src/main/resources/seagrid.properties>
>
> <https://github.com/SciGaP/seagrid-rich-client/blob/master/src/main/resources/seagrid.properties>
>
> I have modified the following configuration's as per the current set-up:
>
>
> 1> dev.airavata.host
>
> 2> dev.airavata.gateway-id
>
> 3> gateway.storage.resource.id​
>
>
> Although, I am getting the error as attached in the screenshot, although I 
> have added a user in the keycloak and
>
> I am able to login via pga client with the same user.
>
> Is there any specific documentation or the steps to connect the seagrid rich 
> client to the new instance
>
> of the Airavata server, or any inputs to solve this issue would be 
> appreciated.
>
> Regards
>
> Karan
>
>
>
>
>
>
>
>
>
>
>

Reply via email to