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.

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

Simplify domain/app/user tuple #1077

Open
jtoohill opened this Issue Oct 23, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@jtoohill
Collaborator

jtoohill commented Oct 23, 2018

In real deployments the domain name can be the "domain", and each domain can host multiple trees.

The AppID+UserID path structure should be application-defined rather than baked into KT, since some apps might need more or less hierarchy.

@jtoohill jtoohill added this to the Simplify APIs milestone Oct 23, 2018

jtoohill pushed a commit to jtoohill/keytransparency that referenced this issue Oct 23, 2018

jtoohill pushed a commit to jtoohill/keytransparency that referenced this issue Oct 23, 2018

Jon Toohill
Rename "domain" to "directory" (google#1077)
"Domain" can be conflated with the domain name of the KT server. "Directory" is meaningful as a namespace over user identifiers, e.g. a telephone directory.

jtoohill pushed a commit to jtoohill/keytransparency that referenced this issue Oct 23, 2018

Jon Toohill
Rename "domain" to "directory" (google#1077)
"Domain" can be conflated with the domain name of the KT server. "Directory" is meaningful as a namespace over user identifiers, e.g. a telephone directory.

jtoohill pushed a commit to jtoohill/keytransparency that referenced this issue Oct 24, 2018

Jon Toohill
Rename "domain" to "directory" (google#1077)
"Domain" can be conflated with the domain name of the KT server. "Directory" is meaningful as a namespace over user identifiers, e.g. a telephone directory.

gdbelvin added a commit that referenced this issue Oct 24, 2018

Rename "domain" to "directory" (#1077) (#1079)
* Rename "domain" to "directory" (#1077)

"Domain" can be conflated with the domain name of the KT server. "Directory" is meaningful as a namespace over user identifiers, e.g. a telephone directory.

* Fix indentation inside SQL commands.

* Fix erroneous replacement in README.md

* Fix long lines and error messages

* Fix monitor_test build

* Make use of opts in setupHistory

gdbelvin added a commit to gdbelvin/keytransparency that referenced this issue Oct 24, 2018

Merge branch 'master' into batch_size
* master:
  Rename "domain" to "directory" (google#1077) (google#1079)

gdbelvin added a commit to gdbelvin/keytransparency that referenced this issue Oct 24, 2018

Merge branch 'master' into write_batch
* master:
  Rename "domain" to "directory" (google#1077) (google#1079)
  Remove unused UpdateEntryRequest.first_tree_size (google#1080)
  Add package to readtoken (google#1078)
  Descriptions for list history test (google#1071)
  Rename smr to `map_root` (google#1075)
  Update the comment on EntryUpdate.committed field (google#1076)
  Update readme (google#1074)
  Remove unused poll-period flag
  Upgrade to latest golang in docker

jtoohill pushed a commit to jtoohill/keytransparency that referenced this issue Oct 25, 2018

Jon Toohill
Remove AppID from Key Transparency (google#1077)
Applications can define their own structure for UserID if needed.

Changes authz policies to be per-domain only; supporting finer-grained authz per UserID prefix can be added later if needed.

Also removes all PGP-specific logic for the "pgp" AppID. The application or frontend app server that uses Key Transparency can enforce its own constraints on key formats and serialization.

jtoohill pushed a commit to jtoohill/keytransparency that referenced this issue Oct 29, 2018

Jon Toohill
Remove AppID from Key Transparency (google#1077)
Applications can define their own structure for UserID if needed.

Changes authz policies to be per-domain only; supporting finer-grained authz per UserID prefix can be added later if needed.

Also removes all PGP-specific logic for the "pgp" AppID. The application or frontend app server that uses Key Transparency can enforce its own constraints on key formats and serialization.

jtoohill added a commit that referenced this issue Oct 30, 2018

Remove AppID from Key Transparency (#1077) (#1082)
* Remove AppID from Key Transparency (#1077)

Applications can define their own structure for UserID if needed.

Changes authz policies to be per-domain only; supporting finer-grained authz per UserID prefix can be added later if needed.

Also removes all PGP-specific logic for the "pgp" AppID. The application or frontend app server that uses Key Transparency can enforce its own constraints on key formats and serialization.

* Fix long lines

gdbelvin added a commit to gdbelvin/keytransparency that referenced this issue Oct 30, 2018

Merge branch 'page_batch' of github.com:gdbelvin/keytransparency into…
… page_batch

* 'page_batch' of github.com:gdbelvin/keytransparency:
  Remove AppID from Key Transparency (google#1077) (google#1082)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment