nextcloud / nextcloud/user_oidc
Implement user provisioning on bearer token request with access token (userinfo validator)
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 181
- Forks
- 60
- Avg merge
- 7h 34m
- Merged PRs (30d)
- 26
Description
closes #1255
When using an access token as a bearer token to make API requests, the user can't currently be properly provisioned. The authentication works but the userinfo validator does not have a provisioning strategy.
We could use the attributes we get from the userinfo endpoint to provision the user.
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 in lib/User/Validator/UserInfoValidator.php at the referenced validator code and review how bearer access-token requests reach it. Use the attributes returned by the userinfo endpoint to provide a provisioning strategy, then verify that the user is properly provisioned when making an API request with an access token.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100