Add support for KxoId #74
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
You'll also need to change the data/users/content.json file.
Btw, KxoId uses a two-level system where id's can be signed with two different keys. The first key (12F5SvxoPR128aiudte78h8pY7mobroG6V) is what my own servers sign with and this is always preferred first for all KxoId registrations - this is level1. The second key is used by "Trusted Peers" to sign ids, and is only done if my own servers happen to be down for some reason.
You can read more about how this works here: http://127.0.0.1:43110/1GTVetvjTEriCMzKzWSP9FahYoMPy6BG1P/?/kxoid
I've added both keys to the data-default/users/content.json - but you can change this to just the first key if you only want to support level-1 (keys signed only with my own servers).
I also didn't make any changes to show the cert-provider on the zite like you did with ZeroTalk.