inrupt / inrupt/solid-client-authn-js
Migrate to oidc-client-ts (successor project of oidc-client-js)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 77
- Forks
- 49
- Avg merge
- 18h 20m
- Merged PRs (30d)
- 32
Description
Search terms you've used
- oidc-client-js
- oidc-client-ts
Impacted environment
In which environment would the proposed feature apply ?
- The browser
- Node.js
- Other (please specify): ...
- I'm not sure.
Feature suggestion
Since oidc-client-js is no longer maintained and further development is instead going on in oidc-client-ts I would like to see this library use that maintained dependency.
Expected functionality/enhancement
This is part of my endeavour to support Solid Login within browser extensions and specififally migrating my extension to chrome manifest v3.
I am willing to adjust oidc-client-ts to support service workers, if solid-client-authn-js will then actually make use of it.
Actual functionality/enhancement
Currently solid-client-authn-js depends on a fork of oidc-client-js
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 tracing where solid-client-authn-js depends on the inrupt fork of oidc-client-js, then compare that integration with oidc-client-ts and its browser service-worker support. Done means the maintained dependency is used and the existing browser authentication behavior remains functional, including the extension use case described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100