Originally created by @Ryonez on GitHub (Jul 1, 2018).
Been testing things out as I get ready to use this, and found that while sharing a password to an organization, it wouldn't show the TOTP code generated by the key.
After further testing:
You can make entries with authenticator key's. Only the code won't show.
The desktop app and the browser extension do show the codes generated.
My assumption is that while the apps do see the organization as a higher tier than free, the web vault doesn't.
Originally created by @Ryonez on GitHub (Jul 1, 2018).
Been testing things out as I get ready to use this, and found that while sharing a password to an organization, it wouldn't show the TOTP code generated by the key.
After further testing:
You can make entries with authenticator key's. Only the code won't show.
The desktop app and the browser extension do show the codes generated.
My assumption is that while the apps do see the organization as a higher tier than free, the web vault doesn't.
@Ryonez commented on GitHub (Jul 1, 2018):
Err... what?
This is a valid issue:

It should be solved in the latest commit, GitHub closed the issue automatically. Sorry for the confusion!
@dani-garcia commented on GitHub (Jul 1, 2018):
It should be solved in the latest commit, GitHub closed the issue automatically. Sorry for the confusion!
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 @Ryonez on GitHub (Jul 1, 2018).
Been testing things out as I get ready to use this, and found that while sharing a password to an organization, it wouldn't show the TOTP code generated by the key.
After further testing:
You can make entries with authenticator key's. Only the code won't show.
The desktop app and the browser extension do show the codes generated.
My assumption is that while the apps do see the organization as a higher tier than free, the web vault doesn't.
@Ryonez commented on GitHub (Jul 1, 2018):
Err... what?

This is a valid issue:
@dani-garcia commented on GitHub (Jul 1, 2018):
It should be solved in the latest commit, GitHub closed the issue automatically. Sorry for the confusion!
@Ryonez commented on GitHub (Jul 1, 2018):
Ahh, I understand. Thank you.