Skip to content
This repository has been archived by the owner on Jun 27, 2022. It is now read-only.

Web vault compatibility #1

Open
2 of 5 tasks
vvondra opened this issue Dec 31, 2017 · 0 comments
Open
2 of 5 tasks

Web vault compatibility #1

vvondra opened this issue Dec 31, 2017 · 0 comments
Labels
help wanted

Comments

@vvondra
Copy link
Owner

vvondra commented Dec 31, 2017 •
edited
Loading

There seem to be a few things needed for full compatibility with the Angular web vault:

Up-to-date list of missing features

  • verify create/update cipher works
  • profile section is missing endpoints
  • 2fa configuration is missing endpoints
  • custom domain settings is not supported at all
  • ... other thing not yet discovered
This was referenced Jan 3, 2018
Closed
Merged
vvondra added a commit that referenced this issue Aug 5, 2018
@vvondra
CLI and partial Webvault compatibility (#7)
42e9900 
PR for #1 

@Pschittt, check out my latest commit. There were some runtime errors with bad imports and I also made all the routes respond with the same OPTIONS CORS headers.

Now on login through webvault I get a successful login and when it hit the /keys endpoint, it doesn't pass any Authorization information. Checking why
This was referenced Aug 26, 2018
Merged
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vvondra