can't see my endpoing in web interface

[Manuel Sopena Ballesteros]

Dear Globus community,

I am new to Globus and just did my first installation in a linux server following this tutorial https://docs.globus.org/globus-connect-server/v5.4/#create-globus-endpoint-section.

So far I have installed the software, configures the endpoint and created both storage gateway and collection.

My problem is that I can't see the endpoints in the web interface when I login using my globusId (same one used to setup the endpoint as owner).

Any idea why my endpoint is not showing in the web interface www.globus.org?

thank you

[Manuel Sopena Ballesteros]

so I setup the endpoint again on the same machine (reusing the deployment-key.json file form previous installation). I get the same Endpoint domain-name as before so I guess the endpoint was successfully created.

This is how I created the endpoint

# globus-connect-server endpoint setup "CSCS TDS Endpoint" --organization "CSCS" --client-id "fc2f9e38-6c3c-492f-8dab-5666fdda237d" --owner csc...@globusid.org
--agree-to-letsencrypt-tos
Secret:
Globus Connect Server uses the Let's Encrypt service to manage
certificates for the web services it installs on your data transfer
nodes. These certificates are issued for DNS domain names operated by
the Globus Project.

Please read the Terms of Service at:
https://letsencrypt.org/repository/
Do you agree to these Terms of Service? [y/N]: y
  [#########################]  100%
Created endpoint fc2f9e38-6c3c-492f-8dab-5666fdda237d
Endpoint domain_name 0dee2.5898.data.globus.org
No subscription is set on this endpoint, so only basic features are enabled.


To enable subscription features on this endpoint, have the
Globus subscription manager for your organization assign a subscription to this endpoint at

https://app.globus.org/file-manager/collections/fc2f9e38-6c3c-492f-8dab-5666fdda237d/overview/subscription after you've set up at least one node


If you plan on using the Google Drive or Google Cloud Storage
connectors, use
     https://0dee2.5898.data.globus.org/api/v1/authcallback_google
as the Authorized redirect URI for this endpoint

I can list the endpoint

# globus-connect-server endpoint show
Display Name:    CSCS TDS Endpoint
ID:              fc2f9e38-6c3c-492f-8dab-5666fdda237d
Subscription ID: None
Public:          True
GCS Manager URL: https://0dee2.5898.data.globus.org
Network Use:     normal
Organization:    CSCS

And the role shows csc...@globusid.org is the owner

# globus-connect-server endpoint role list
Role ID                              | Role  | Principal           
------------------------------------ | ----- | --------------------
4c0a520d-76de-4df9-a244-d8da5b48b433 | owner | csc...@globusid.org

Then I go to https://app.globus.org/endpoints?scope=administered-by-me and the list of endpoints is empty

Any idea why?

thank you very much

[Stephen Rosen]

Hi Manuel,

I believe that what's happening here is that your account is an 'owner' but not an 'administrator'.

The distinction between these is best described in our documentation here:

  https://docs.globus.org/globus-connect-server/v5.4/reference/endpoint/role/#endpoint_roles

The easiest way to get the endpoint into the administered-by-me view is to just add yourself as an administrator on the endpoint, e.g.

  globus-connect-server endpoint role create administrator f...@example.org

In your case, I think that's all you need to do. In case it isn't, here are some other notes on troubleshooting these kinds of situations:

1. It's always a good idea to double- or triple-check that you're logged in to the correct account. Go to the account page to view your logged-in identities: https://app.globus.org/account

If you've already done that, tell us what you saw (e.g. when opening a support ticket). Otherwise, we're likely to ask about this as one of our first lines of investigation.

It's very frequent when users have multiple accounts that they're accidentally logged in as the wrong one. (This happens to our team, including me, all the time!)

2. You can often find and inspect an endpoint or collection by looking for it by ID. Go to https://app.globus.org/endpoints and put the endpoint ID into the search bar.

That should take you to this page (in the case of your endpoint ID):

  https://app.globus.org/endpoints?q=fc2f9e38-6c3c-492f-8dab-5666fdda237d&scope=all

3. It may help to use the Globus CLI ( https://docs.globus.org/cli/ ) to poke around

You can login to that tool and use `globus endpoint show ...`, etc. to look at the state of your endpoints and collections.

This helps you check what you're seeing in the webapp to see if it's consistent.

All that said, I hope the initial fix of adding an 'administrator' role is sufficient.

Best,

-Stephen

[Manuel Sopena Ballesteros]

Hi Stephen,

thank you for this, I can run the command but apparently I need a subscriptions for this

# globus-connect-server endpoint role create administrator csc...@globusid.org
An API Error Occurred
HTTP status: 403
code:        subscription_required
message:     This feature requires the endpoint t

o be managed with a Globus subscription

Is there a work around this? our production system run on version 4 basic account and we can manage endpoints through the web interface.

My goal is to test the integration of globus connect server v5 to our OIDC, if successful then we will consider upgrading to globus to v5

Any idea how I could manage my endpoints running on version 5 basic account?

thank you very much

[Manuel Sopena Ballesteros]

sorry to be a piss,

I have deleted/clean the endpoint/node and created a new client_id. I now followed the quick installation guide to create a new installation.

this is my endpoint:

# globus-connect-server endpoint show
Display Name:    CSCS TDS Endpoint

ID:              b4c86221-9db3-4e63-bfec-87741f33ae19

Subscription ID: None
Public:          True

GCS Manager URL: https://f3199.75bc.data.globus.org

Network Use:     normal
Organization:    CSCS

adding an administrator to the endpoint still not possible

# globus-connect-server endpoint role create administrator csc...@globusid.org
An API Error Occurred
HTTP status: 403
code:        subscription_required

message:     This feature requires the endpoint to be managed with a Globus subscription

I also tried creating a folder into the endpoint through the globus cli

# globus mkdir b4c86221-9db3-4e63-bfec-87741f33ae19:\~/cli_example_dir
Globus CLI Error: A Transfer API Error Occurred.
HTTP status:      409
request_id:       dj6dteIkm
code:             Conflict
message:          The endpoint 'b4c86221-9db3-4e63-bfec-87741f33ae19' is non_functional

Endpoint details

# globus endpoint show b4c86221-9db3-4e63-bfec-87741f33ae19

Display Name:              CSCS TDS Endpoint

ID:                        b4c86221-9db3-4e63-bfec-87741f33ae19
Owner:                     b4c86221-9db3-4e63...@clients.auth.globus.org
Activated:                 False
Shareable:                 True
Department:                None
Keywords:                  None
Endpoint Info Link:        None
Contact E-mail:            None
Organization:              CSCS
Department:                None
Other Contact Info:        None
Visibility:                True
Default Directory:         None
Force Encryption:          False
Managed Endpoint:          False
Subscription ID:           None
Legacy Name:               u_wtegeim5wnhghp7mq52b6m5ode#14984cee-2131-11ec-a0a4-6b21ca6daf73
Local User Info Available: None

My question is. How can I make my endpoint functional?

thank  you very much

[Greg Nawrocki]

Manuel,

Creating guest collections or assigning roles to a collection are subscription only features. Your endpoint needs to be managed under a subscription in order to accomplish such tasks.

If by “making your endpoint functional” you mean that you are simply looking to create Mapped Collections under the Free / Basic tier of Globus, you can do that without a subscription.

You do not need to assign roles to an endpoint. This video is an excellent guide for accomplishing that: https://www.youtube.com/watch?v=8ILtsSRiML8

— Greg

[Rachana Ananthakrishnan]

Manuel,

To add to Greg’s response here, the endpoint (in your case b4c86221-9db3-4e63-bfec-87741f33ae19) is only the servers and network configuration. If you follow sections 1.7 and .18 in the quick start guide (https://docs.globus.org/globus-connect-server/v5.4/quickstart/#create_a_mapped_collection) it adds a storage gateway (to configure specific storage type) and a mapped collection. The collection is what provides data access interfaces, and you’ll be able to do listing, mkdir and transfers from a collection. 

This is different from version 4, where was only one object the endpoint that allowed server and storage system configuration, and data access. Separating this out allowed support of multiple storage types and policies that leverage the same server pool, amongst other things. 

For example, this command will be against the collection not the endpoint. 

# globus mkdir b4c86221-9db3-4e63-bfec-87741f33ae19:\~/cli_example_dir

We’ll update that error message to clarify that. 

At this time, the steps outlined in the install guide and configuring the endpoint, storage gateway and creating collections is only supported via the command line. 

If you are looking to mimic configuration and deployment of a version 4 endpoint you already have, we can help with more specifics there as well. Please feel free to reach out to sup...@globus.org with your v4 endpoint information and/or your configuration requirements, and we can assist in the deployment.

Rachana

--
You received this message because you are subscribed to the Google Groups "Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss+u...@globus.org.