nextcloud / nextcloud/richdocuments
Implement token refresh or renewal to avoid expiration
Open
Nobody has claimed this yet.
1. to develop
enhancement
feature: wopi host
- Dominant language
- JavaScript
- Stars
- 453
- Forks
- 147
- Avg merge
- 14h 54m
- Merged PRs (30d)
- 83
Description
- Check if there is anything within the WOPI protocol to extend the token TTL or renew the token
- Option A: Extend the token TTL on checkFileInfo calls or other WOPI operations
- Would need regular calls of some endpoint
- However this has the benefit that we could actively detect if permissions to the document have changed, e.g. if a user was removed from a share
- Option B: On COOL
- Show a message on expired token and let the user reload manually
- A post message could be emitted and then richdocuments could generate a new WOPI token
- We could also extend the token through an API call on the richdocuments side
- If tokens should be renewed, COOL needs a way to replace the existing token while keeping the session active
- Show a message on expired token and let the user reload manually
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 checking the WOPI protocol for token TTL extension or renewal, then trace how COOL and richdocuments currently exchange and use WOPI tokens. Compare the listed renewal options and define how an expired token is reported or replaced while keeping the session active; the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100