nextcloud / nextcloud/files_mindmap
InvalidSignatureException - Certificate is not valid
Open
Nobody has claimed this yet.
1. to develop
bug
- Dominant language
- JavaScript
- Stars
- 197
- Forks
- 52
- Avg merge
- 22h 14m
- Merged PRs (30d)
- 13
Description
Hi,
after a NC update to NC 30.0.5, I've got the below error message. I did deactivate Mindmap, reactivated it, and did a rescan, but the issue is still there.
Is there a way to fix this or is an update required?
I did not yet re-installed the extension.
Technical information
=====================
The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix
them.
Results
=======
- files_mindmap
- EXCEPTION
- OC\IntegrityCheck\Exceptions\InvalidSignatureException
- Certificate is not valid.
Raw output
==========
Array
(
[files_mindmap] => Array
(
[EXCEPTION] => Array
(
[class] => OC\IntegrityCheck\Exceptions\InvalidSignatureException
[message] => Certificate is not valid.
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 with the files_mindmap integrity-check result reported on Nextcloud 30.0.5 and review the existing issue discussion for reproduction details and prior findings. Determine what change is needed to eliminate InvalidSignatureException and verify that the integrity check completes without the certificate error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100