Originally created by @mprasil on GitHub (Jul 21, 2018).
New vault (#93) calls PUT on /api/ciphers/share to "Share selected" ciphers. This functionality wasn't present in the previous vault so implementation will be a bit more involved, but should be pretty similar to "move selected".
(also woohoo! 100th issue 😄)
Originally created by @mprasil on GitHub (Jul 21, 2018).
New vault (#93) calls `PUT` on `/api/ciphers/share` to "Share selected" ciphers. This functionality wasn't present in the previous vault so implementation will be a bit more involved, but should be pretty similar to "move selected".
(also woohoo! 100th issue :smile:)
I guess we need to add an organization in order to test the "Share" functionality, but I am not able to figure out how to add an organization? I tried uploading a random JSON file as the license file but I am getting a 401 error. Can someone please guide me on this?
@krankur commented on GitHub (Aug 1, 2018):
I guess we need to add an organization in order to test the "Share" functionality, but I am not able to figure out how to add an organization? I tried uploading a random JSON file as the license file but I am getting a 401 error. Can someone please guide me on this?
Hi, there's no licence required - just create free organization (the first option) and it should have all features after that.
@mprasil commented on GitHub (Aug 1, 2018):
Hi, there's no licence required - just create free organization (the first option) and it should have all features after that.
I think that happens in the self hosted version (when you build with npm run dist:selfhost)
It should work if you build the normal version (with npm run dist)
@dani-garcia commented on GitHub (Aug 1, 2018):
I think that happens in the self hosted version (when you build with npm run dist:selfhost)
It should work if you build the normal version (with npm run dist)
@dani-garcia I submitted #109 to merge recent changes from master. We should do this before @krankur touches the sharing API as there were some major changes and will be pain to merge later.
@mprasil commented on GitHub (Aug 1, 2018):
@dani-garcia I submitted #109 to merge recent changes from master. We should do this before @krankur touches the sharing API as there were some major changes and will be pain to merge later.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @mprasil on GitHub (Jul 21, 2018).
New vault (#93) calls
PUTon/api/ciphers/shareto "Share selected" ciphers. This functionality wasn't present in the previous vault so implementation will be a bit more involved, but should be pretty similar to "move selected".(also woohoo! 100th issue 😄)
@tgturner commented on GitHub (Jul 26, 2018):
I would love to take a look at this one!
@mprasil commented on GitHub (Jul 26, 2018):
Go for it and don't hesitate to ask for help.
@tgturner commented on GitHub (Jul 26, 2018):
Thanks! I'll take a look at it this evening.
@krankur commented on GitHub (Aug 1, 2018):
I guess we need to add an organization in order to test the "Share" functionality, but I am not able to figure out how to add an organization? I tried uploading a random JSON file as the license file but I am getting a 401 error. Can someone please guide me on this?
@mprasil commented on GitHub (Aug 1, 2018):
Hi, there's no licence required - just create free organization (the first option) and it should have all features after that.
@dani-garcia commented on GitHub (Aug 1, 2018):
I think that happens in the self hosted version (when you build with npm run dist:selfhost)
It should work if you build the normal version (with npm run dist)
@mprasil commented on GitHub (Aug 1, 2018):
@dani-garcia I submitted #109 to merge recent changes from master. We should do this before @krankur touches the sharing API as there were some major changes and will be pain to merge later.
@mprasil commented on GitHub (Aug 1, 2018):
Thanks for merging it. @krankur make sure you're working with latest beta code.
@krankur commented on GitHub (Aug 1, 2018):
@mprasil Will do. Thanks for the heads up.
@mprasil commented on GitHub (Aug 9, 2018):
I think this was resolved in #116