[Badges] Credly integration doesn't support token refresh
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 25
- Forks
- 83
- Avg merge
- 11h 51m
- Merged PRs (30d)
- 1
Description
Description
The current Credly integration only has the static configuration for the authorization token.
In practice, Credly authorization tokens expire after 180 days.
The Credentials service does not record when the token was created or last refreshed, and it does not refresh the token through the Credly API.
As a result, once the token expires, Credly-related operations such as badge issuance and badge template sync can fail until an operator manually updates the configuration.
Supporting Info
docs.credly.com/browse/docs/authentication-methods
Expected Result
The Credentials service should refresh the token through the Credly API before the token expires.
Contributor guide
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 tracing the Credentials service's Credly integration and the token configuration described in the issue, then review Credly's authentication-methods documentation. Determine where token creation or refresh state must be handled and how the Credly API is called. Done means tokens refresh before expiry so badge issuance and badge template sync continue without manual configuration updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100