Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Cryptomator tells me that when creating a new Hub device, the device needs to be authorised by the Vault owner #3246

Closed
2 tasks done
SailReal opened this issue Dec 6, 2023 · 0 comments · Fixed by #3288
Closed
2 tasks done

Cryptomator tells me that when creating a new Hub device, the device needs to be authorised by the Vault owner #3246

SailReal opened this issue Dec 6, 2023 · 0 comments · Fixed by #3288
Assignees
@infeo
Labels
misc:gui type:bug Something isn't working
Milestone
1.12.0

Comments

@SailReal
Copy link
Member

SailReal commented Dec 6, 2023

Please agree to the following

Summary

Cryptomator tells me that when creating a new Hub device, the device needs to be authorised by the Vault owner

What software is involved?

  • Operating System: Linux
  • Cryptomator: 1.11.1
  • Hub: 1.3.0

Volume Type

None

Steps to Reproduce

Register a new device in Hub

Expected Behavior

Cryptomator notifies my about its success and tells me to unlock again the vault (or directly tries it again?) but does not say anything about the vault owner.

Actual Behavior

image

Reproducibility

Always

Relevant Log Output

No response

Anything else?

A newly added device does not need to be authorized by the vault owner.
@SailReal SailReal added the type:bug Something isn't working label Dec 6, 2023
@SailReal SailReal added this to the 1.12.0 milestone Dec 6, 2023
@infeo infeo added the misc:gui label Dec 18, 2023
@infeo infeo self-assigned this Jan 17, 2024
infeo added a commit that referenced this issue Jan 17, 2024
@infeo
closes #3246
42425af 
splitting registerSuccess into two scenes, one for hub 1.3.x and one for legacy
@infeo infeo mentioned this issue Jan 17, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@infeo infeo

Labels
misc:gui type:bug Something isn't working
Projects
None yet
Milestone
1.12.0
Development

Successfully merging a pull request may close this issue.

Feature: Split device registration into "normal" and "legacy" flow cryptomator/cryptomator
2 participants
@SailReal @infeo