RADAR-base / RADAR-base/RADAR-Rest-Source-Auth
Do not try to deregister the garmin user when no access token secret is available.
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
According to support, signing a request with just the access token without an access token secret will not work, hence we should not try to deregister such users. Instead, the application should show an ERROR log to say to contact garmin support to remove such user's subscription on garmin.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Garmin deregistration flow and the code that handles users without an access token secret. Read the surrounding OAuth authorization logic and existing logging conventions; done means such users are not deregistered and an ERROR log directs support to remove the Garmin subscription.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin, spring
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100