You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order for a user to log in to a DataHUB instance using ARC Commander, he/she needs to put the application ID in the Config using for example this command: $ arc config set -l -n general.authclientid -v <Application_ID>. I think, (if possible) it would be better if the application ID can be put in the Config for all users by the ARC Commander developer, so that each user does not have to put the ID themselves (,like it works in ARCitect). Thanks.
The text was updated successfully, but these errors were encountered:
Just for context: As I understood it, when registering a new application into a GitLab instance, a random ID is generated which has to be used by the tool to make the OpenID call. Therefore the ARC Commander can't just authenticate itself by a fixed handle (a.k.a "arc-commander"). Because of this, currently, this GitLab-specific ID has to be set in the ARC Commander config when accessing a GitHub other than the central PlantDATAhub.
I will take a look into how to circumvent, maybe also check out ARCitect. Because if I remember correctly, in the ARCitect you can just select a GitLab without any further input.
In order for a user to log in to a DataHUB instance using ARC Commander, he/she needs to put the application ID in the Config using for example this command: $ arc config set -l -n general.authclientid -v <Application_ID>. I think, (if possible) it would be better if the application ID can be put in the Config for all users by the ARC Commander developer, so that each user does not have to put the ID themselves (,like it works in ARCitect). Thanks.
The text was updated successfully, but these errors were encountered: