Rest Sources Authorization 401 error

[ThomasKassiotis]

Hello ! I am trying to access the rest-sources/authorizer service.

When I give my cred (MP credentials) i get a 401 error.

Shall I change any config from **ManagementPortal > OauthClients ** ?

Thanks !

[keyvaann]

You can check the logs for both apps, maybe there is a clue in there. Also make sure Oauth Client secret is same in both apps. There should also be documents and issue reports for those apps that you can check out.
@blootsvoets should also be able to help you better.

[ThomasKassiotis]

Hello ! These are the logs for radar-rest-sources-authorizer and radar-rest-sources-backend.
radar-rest-sources-backendauthorizer.yml.txt
radar-rest-sources-authorizer.txt

[ThomasKassiotis]

At the loggs radar-rest-sources-backenauthorizer.yml i found at first lines

[2021-12-07 13:45:03,955] INFO  - Reading configuration from /etc/radar-rest-sources-backend/authorizer.yml (ConfigLoader.kt:50)
[2021-12-07 13:45:06,637] INFO  - RADAR_IS_CONFIG_LOCATION environment variable not set, looking for it on the classpath (TokenVerifierPublicKeyConfig.java:59)
[2021-12-07 13:45:06,638] INFO  - Token public key endpoints set to [http://management-portal:8080/managementportal//oauth/token_key] (TokenVerifierPublicKeyConfig.java:85)
[2021-12-07 13:45:06,652] INFO  - Getting the JWT public key at http://management-portal:8080/managementportal//oauth/token_key (TokenValidator.java:231)
[2021-12-07 13:45:36,738] ERROR - Failed to immediately initialize token validator, will try again later: org.radarbase.auth.exception.TokenValidationException: java.net.SocketTimeoutException: connect timed out (ManagementPortalTokenValidator.kt:29)
[2021-12-07 13:45:37,290] INFO  - Initializing EntityManagerFactory with config: RadarPersistenceInfo(managedClasses=[org.radarbase.authorizer.doa.entity.RestSourceUser], properties={hibernate.connection.provider_class=org.hibernate.connection.C3P0ConnectionProvider, hibernate.c3p0.max_size=50, hibernate.c3p0.idle_test_period=300, hibernate.c3p0.max_statements=0, hibernate.dialect=org.hibernate.dialect.PostgreSQLDialect, hibernate.c3p0.min_size=0, javax.persistence.schema-generation.database.action=none, hibernate.c3p0.acquireRetryAttempts=3, hibernate.c3p0.breakAfterAcquireFailure=false, hibernate.c3p0.timeout=100, hibernate.c3p0.checkoutTimeout=5000, javax.persistence.jdbc.url=jdbc:postgresql://postgresql:5432/restsourceauthorizer, javax.persistence.jdbc.user=postgres, org.hibernate.flushMode=COMMIT, hibernate.c3p0.acquire_increment=1, javax.persistence.jdbc.driver=org.postgresql.Driver, javax.persistence.jdbc.password=password}) (RadarEntityManagerFactoryFactory.kt:24)
[2021-12-07 13:45:37,342] INFO  - HHH000204: Processing PersistenceUnitInfo [name: org.radarbase.jersey.hibernate] (LogHelper.java:31)

at the url http://management-portal:8080/managementportal//oauth/token_key -> there is a double / .Maybe is this the error ?

[afolarin]

I cant' see where the extra / is coming from. perhaps @K1Hyve or @yatharthranjan have better knowledge of the rest authorizer

radar-helm-charts/charts/radar-rest-sources-backend/templates/deployment.yaml:            value: "http://{{ .Values.managementportal_host }}:8080/managementportal/oauth/token_key"

[yatharthranjan]

Hi, Management portal's callback URL is different from fitbit's. Since both use OAuth 2.0 standard the terminology is same. So you don't need to change the AUTH_CALLBACK_URL value as it is for management portal auth (not for fitbit).
The Rest-sources-auth-backend should creates the callback url value for fitbit from the base URL of advertisedBaseUri property -- https://github.com/RADAR-base/radar-helm-charts/blob/4c13a54f596ac7e8fe387ff2a4f61e7bd979a802/charts/radar-rest-sources-backend/templates/configmap.yaml#L15

To configure that you just need to set the serverName value correctly, but there was an error where the serverName was not added to values.yaml file and hence it was not configurable. This is now being fixed by the PR RADAR-base/radar-helm-charts#9

[ThomasKassiotis]

Hi and thanks for the reply ! The fix is ready ? Can I try ?
cause i am getting

h-backend:3.2.2: not found
  Warning  Failed     5m5s (x4 over 6m45s)   kubelet            Error: ErrImagePull
  Warning  Failed     4m52s (x6 over 6m44s)  kubelet            Error: ImagePullBackOff
  Normal   BackOff    100s (x19 over 6m44s)  kubelet            Back-off pulling image "radarbase/radar-rest-source-auth-backend:3.2.2"

[yatharthranjan]

hi, i think there is some issue with automatic publish of docker images to docker hub and hence there is no tag for 3.2.2 https://hub.docker.com/r/radarbase/radar-rest-source-auth-backend/tags

@mpgxvii was looking into it and should be able to help.

[mpgxvii]

Hi, yes there were issues with the auto publish because of the workflow config. The tag 3.2.2 should now be there.

[ThomasKassiotis]

Happy new year guys ! Hope everything good !
I tried again today with radar-rest-sources-backend v 0.2.2 but Error: release radar-rest-sources-backend failed, and has been uninstalled due to atomic being set: timed out waiting for the condition. Only if I change 20-fitbit.yaml > radar-rest-sources-backend to v.0.2.0 I can move on. After the installation I can edit the deployments to the requested versions and images

But I am still having the above errors when I am trying to authorize a fitbit client.
Any ideas ? Thanks a lot.

[ThomasKassiotis]

Thanks it's working now.