search

rubin-dp0 / Support

Submit Github Issues related to DP0
MIT License
1 stars 3 forks source link

Problem trying to acces to the Rubin Science platform API #28

Closed lauramarroo closed 2 years ago

lauramarroo commented 2 years ago

Describe the bug I'm trying to access to the Rubin science platform using TAP through TOPCAT. I use the https://data.lsst.cloud/api/tap as the TAP endpoint. When TOCPCAT tries to connect to the server, it requires username and password. According to the https://lsst-lsp-stable.ncsa.illinois.edu/api-aspect the username is x-oauth-basic and the password is the token. However, it keeps telling that the authentication failed. I also tried with my username without luck

To Reproduce Steps to reproduce the behavior:

  1. Open TOPCAT
  2. Click on Query remote database button
  3. Enter the TAP URL: https://data.lsst.cloud/api/tap
  4. Enter username (x-oauth-basic) and password (token)
  5. See error: https://data.lsst.cloud/api/tap/tables error: java.io.IOException: Table resource access failure (401 Unauthorized)

Expected behavior Access to the platform

Screenshots image image image

URL

Desktop (please complete the following information):

Additional context TOPCAT version image

ktlim commented 2 years ago

If I'm counting the symbols correctly, your token does not look long enough at 22 characters. That looks like the "public" part of the token without the three character "gt-" prefix nor the "secret" part that comes after a "." character, which is another 22 characters (for a total of 48).

If you did not copy the full token after generating it, you'll have to generate a new one; there's no way for anyone to recover the full token.

lauramarroo commented 2 years ago

Yes, i used it also, i copied the token with 48 character and it didn't work

[image: image.png]

[image: image.png]

El mar, 21 jun 2022 a la(s) 17:50, Kian-Tat Lim @.***) escribió:

If I'm counting the symbols correctly, your token does not look long enough at 22 characters. That looks like the "public" part of the token without the three character "gt-" prefix nor the "secret" part that comes after a "." character, which is another 22 characters (for a total of 48).

If you did not copy the full token after generating it, you'll have to generate a new one; there's no way for anyone to recover the full token.

— Reply to this email directly, view it on GitHub https://github.com/rubin-dp0/Support/issues/28#issuecomment-1162438296, or unsubscribe https://github.com/notifications/unsubscribe-auth/AZUIA7HDYG223YJ4573T6Z3VQJBJZANCNFSM5ZN6QRYA . You are receiving this because you modified the open/close state.Message ID: @.***>

SimonKrughoff commented 2 years ago

I believe the real issue is that a token generated at the NCSA instance of the RSP is being used to access the API aspect at data.lsst.cloud. Authentication tokens are not meant to be used across deployments, so I believe this issue actually describes intended behavior. Since things are behaving as expected, I'm closing this ticket.