[feat]: Allow the use of UserPermissionAuthProvider

Open
#91 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
api, authentication

Research direction

Start at the strapi function and trace how ApiTokenAuthProvider is selected and exposed. Compare that path with UserPermissionAuthProvider and determine what client configuration must accept the alternative credentials; done means the provider can be used to instantiate the client and the existing behavior remains intact.

Written by the indexing model from the issue text.

Description

issue: enhancement
A clear and concise description of what the feature is

Currently, the 'strapi' function defaults to ApiTokenAuthProvider and it's not possible to use UserPermissionAuthProvider as it's not expose in the library.

Why should this feature be included?

Allowing to instantiate the client with UserPermission credentials would make this client a great option to adopt it from many frontend frameworks.

Please provide an example for how this would work

No response

Dominant language
TypeScript
Stars
83
Forks
18
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from strapi/client

All issues in strapi/client

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.