Error connecting to host with r-client dev ver

datascience · 2 May 2022 14:21

Hi,

when trying to connect to the openeo.cloud host today, I received a new error.
I used the method described in the answers to this post: Login Issues openeo R-client dev version for the dev branch of the r-client (see below), which was still working at the beginning of last week.

#devtools::install_github(repo="Open-EO/openeo-r-client",dependencies=TRUE)

library(openeo)
#> Warning: replacing previous import 'jsonlite::unbox' by 'rlang::unbox' when
#> loading 'openeo'
#> Warning: replacing previous import 'jsonlite::flatten' by 'rlang::flatten' when
#> loading 'openeo'
#> 
#> Attaching package: 'openeo'
#> The following objects are masked from 'package:base':
#> 
#>     capabilities, debug
packageVersion("openeo")
#> [1] '1.2.0'

host = "https://openeo.cloud"

# connect and login in one step
con = connect(host, provider = "egi")
#> Warning in value[[3L]](cond): argument ".req" is missing, with no default
#> Error: $ operator is invalid for atomic vectors

# connect and login seperate
con = connect(host)
#> Warning in value[[3L]](cond): argument ".req" is missing, with no default
#> Error: $ operator is invalid for atomic vectors
# login(provider="egi")

^{Created on 2022-05-02 by the reprex package (v2.0.1)}

Session info

sessioninfo::session_info()
#> ─ Session info ───────────────────────────────────────────────────────────────
#>  setting  value
#>  version  R version 4.1.3 (2022-03-10)
#>  os       Ubuntu 20.04.4 LTS
#>  system   x86_64, linux-gnu
#>  ui       X11
#>  language (EN)
#>  collate  en_US.UTF-8
#>  ctype    en_US.UTF-8
#>  tz       Europe/Berlin
#>  date     2022-05-02
#>  pandoc   2.17.1.1 @ /usr/lib/rstudio/bin/quarto/bin/ (via rmarkdown)
#> 
#> ─ Packages ───────────────────────────────────────────────────────────────────
#>  package     * version date (UTC) lib source
#>  base64enc     0.1-3   2015-07-28 [1] CRAN (R 4.1.2)
#>  cli           3.3.0   2022-04-25 [1] CRAN (R 4.1.3)
#>  curl          4.3.2   2021-06-23 [2] CRAN (R 4.1.0)
#>  digest        0.6.29  2021-12-01 [1] CRAN (R 4.1.2)
#>  evaluate      0.15    2022-02-18 [1] CRAN (R 4.1.2)
#>  fastmap       1.1.0   2021-01-25 [1] CRAN (R 4.1.1)
#>  fs            1.5.2   2021-12-08 [1] CRAN (R 4.1.3)
#>  generics      0.1.2   2022-01-31 [1] CRAN (R 4.1.2)
#>  glue          1.6.2   2022-02-24 [1] CRAN (R 4.1.3)
#>  highr         0.9     2021-04-16 [2] CRAN (R 4.1.0)
#>  htmltools     0.5.2   2021-08-25 [1] CRAN (R 4.1.1)
#>  httr2         0.2.0   2022-04-28 [1] CRAN (R 4.1.3)
#>  jsonlite      1.8.0   2022-02-22 [1] CRAN (R 4.1.3)
#>  knitr         1.39    2022-04-26 [1] CRAN (R 4.1.3)
#>  lubridate     1.8.0   2021-10-07 [1] CRAN (R 4.1.2)
#>  magrittr      2.0.3   2022-03-30 [1] CRAN (R 4.1.3)
#>  openeo      * 1.2.0   2022-05-02 [1] Github (Open-EO/openeo-r-client@eab014a)
#>  R6            2.5.1   2021-08-19 [2] CRAN (R 4.1.1)
#>  rappdirs      0.3.3   2021-01-31 [2] CRAN (R 4.1.0)
#>  reprex        2.0.1   2021-08-05 [1] CRAN (R 4.1.2)
#>  rlang         1.0.2   2022-03-04 [1] CRAN (R 4.1.3)
#>  rmarkdown     2.14    2022-04-25 [1] CRAN (R 4.1.3)
#>  rstudioapi    0.13    2020-11-12 [2] CRAN (R 4.1.0)
#>  sessioninfo   1.2.2   2021-12-06 [1] CRAN (R 4.1.2)
#>  stringi       1.7.6   2021-11-29 [1] CRAN (R 4.1.2)
#>  stringr       1.4.0   2019-02-10 [2] CRAN (R 4.1.0)
#>  withr         2.5.0   2022-03-03 [1] CRAN (R 4.1.3)
#>  xfun          0.30    2022-03-02 [1] CRAN (R 4.1.3)
#>  yaml          2.3.5   2022-02-21 [1] CRAN (R 4.1.2)
#> 
#>  [1] /home/carola/R/x86_64-pc-linux-gnu-library/4.1
#>  [2] /usr/local/lib/R/site-library
#>  [3] /usr/lib/R/site-library
#>  [4] /usr/lib/R/library
#> 
#> ──────────────────────────────────────────────────────────────────────────────

As you can see, the error occurs not during login, but already during the connection process.
Also for some reason the reprex was truncated, so I appended a screenshot in addition showing the full message as it appeared in my console.

Thanks as always for any advice!

florian.lahn · 2 May 2022 15:48

Hi there,

at the end of last week I was also preparing the package for a CRAN release. One big problem was that the httr2 package was not updated yet on CRAN. I made a PR to the httr2 package for the device_code+pkce, which was accepted on Github, but was not released on CRAN yet.

In general .req is commonly used as parameter in http requests of httr2 and when I browse through the Session Info:

It seems that they released the new version very recent. I will check the new version and report back.

Best,
Florian

florian.lahn · 5 May 2022 13:21

Hi,

I have now fixed the issues with the httr2 package (v0.2.0). There have been renamings of parameters - previously req became .req. The most recent changes are on Github on both branches (master and develop) and a CRAN release of version 1.2.0 is also following soon.

Best,
Florian

datascience · 9 May 2022 07:41

Hi,

thanks as always for the quick replies!
The login using the device code method now says it is successful, however, when trying to execute any functions we again receive an error.

It seems the account we connect to is not our own, as the error message states that we are not authorized and the activity is not recorded in our approved services in EGI.

Again see the screenshot for the error message:

Thanks again!

peterjames.zellner · 9 May 2022 08:52

Hi,
@florian.lahn can rule out a technical error from the R-Client.
@benjamin.schumacher, could you have a look at their account?

m.mohr · 9 May 2022 09:31

I’ve just installed the R client from development and can login and list jobs just fine. So I would assume it’s not the client, but rather an issue with the user account. Maybe the free tier / EA status has expired? @benjamin.schumacher

@datascience Can you log in using the Web Editor? https://editor.openeo.cloud If no, it is really the user account.

benjamin.schumacher · 9 May 2022 09:41

Can confirm that hendrik has access as an Early Adopter within the Virtual Organization.

datascience · 9 May 2022 09:49

The editor shows the same error regarding proper enrollment. Upon clicking ‘show details’ the following message was shown:

* Proper enrollment in openEO Platform virtual organization is required.
  * Code: PermissionsInsufficient
  * Data:

    * **Config**:

      * **Transitional**:

        * **Silent JSONParsing**: *✔️*
        * **Forced JSONParsing**: *✔️*
        * **Clarify Timeout Error**: *❌*

      * **Adapter**: *JavaScript Function*
      * **Transform Request**:

        1. *JavaScript Function*

      * **Transform Response**:

        1. *JavaScript Function*

      * **Timeout**: 0
      * **Xsrf Cookie Name**: XSRF-TOKEN
      * **Xsrf Header Name**: X-XSRF-TOKEN
      * **Max Content Length**: -1
      * **Max Body Length**: -1
      * **Validate Status**: *JavaScript Function*
      * **Headers**:

        * **Accept**: application/json, text/plain, */*
       
      * **Method**: get
      * **Response Type**: json
      * **Url**: /me
      * **Base URL**: https://openeocloud.vito.be/openeo/1.0.0
      * **Data**:

    * **Request**: *Empty*
    * **Response**:

      * **Data**:

        * **Code**: PermissionsInsufficient
        * **id**: b456db9e-0416-47cc-a258-e68ad45de9e3
        * **Message**: Proper enrollment in openEO Platform virtual organization is required.

m.mohr · 9 May 2022 09:53

@datascience It looks like you are authenticating with the wrong user account. From the credentials in the error message, I see that the associated account at EGI is de9…@egi.eu while your user account that has been granted access is different (f11…@egi.eu). Can you check that you are logging in with the account that is actually subscribed to openEO Platform?

benjamin.schumacher · 9 May 2022 09:53

@datascience which EGI SSO / account are you using? It seems like you try to use an account which is not connected your EGI SSO. Make sure you are using your mail address and the social/EGI account it is connected to when authenticating.

benjamin.schumacher · 9 May 2022 09:56

@datascience I deleted a part of your post due to exposure of private information. Just to let you know.

datascience · 9 May 2022 10:34

Ok, thanks for your feedback. We checked on two devices separately. On one of them indeed there was an active login to a personal github account which caused an association with the wrong account. On the second device logins were just performed ahead of connecting with the backend and we also received the same error. Anyway, looks like now everything works again.