1 / 6

Client Registration Summary

Client Registration Summary. Update 6/21/2011 Denis Pochuev. List of the open issues. Registration universe What does the Entity Object look like? Proxy Registration/Authentication Open questions regarding ownership. Registration parameters. Explicit vs. Implicit

emory
Download Presentation

Client Registration Summary

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Client Registration Summary Update 6/21/2011 Denis Pochuev

  2. List of the open issues • Registration universe • What does the Entity Object look like? • Proxy Registration/Authentication • Open questions regarding ownership

  3. Registration parameters • Explicit vs. Implicit • Certificate and/or Username/Password (and/or other credential types) • Self vs. Other • Pending vs. Synchronous • There are restrictions on the combinations • Implicit can only be Certificate and Self • Pending can only be Explicit • All other combinations are permitted

  4. What does the Entity object look like? • Entity has to contain UUID, Owner, Credential, may contain more Register Object Type=Entity Template-Attribute Attribute Attribute Name: “Credential” Attribute Value: Credential Type: Transport Certificate Credential Value: <empty> Entity UUID: ABCD-1234 <- required Owner: DCBA-4321 <- required (0 = self or actual self UUID?) Attribute <- required (at least one) Attribute Name: “Credential” Attribute Value: … Attribute Attribute Name: “Name” <- not required, really an alias Attribute Value: user1

  5. Proxy Use-cases

  6. Ownership questions • Settled questions: • Does every crypto object have an Entity owner? (Yes) • Does every owner have access to all of its crypto objects and only them? (By default yes, controlled by server policy) • At F2F it was suggested that it should be controlled by profile • Implies that server needs to enforce non-impersonation • Open questions: • Does every Entity have an Entity owner? • Do we allow two levels of ownership hierarchy or infinite? • Does the owning Entity own the Objects of its subordinates (possibly multiple levels)? Does it have access to them? Is it controlled by the policy, profile or else? • Do pre-generated objects from the Group proposal have owners? • Is ownership attribute modifiable by server or by client (Crypto Object or Entity)?

More Related