Skip to content
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

Use federatedCloudId instead of email for user identification between servers #102

Closed
wants to merge 3 commits into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 15 additions & 12 deletions spec.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -619,23 +619,22 @@ definitions:
type: object
allOf:
- properties:
recipientProvider:
type: string
format: url
description: URL of the receiver OCM service.
example: https://receiver.org
token:
type: string
description: Token received in the invite
example: xyz
userID:
userId:
type: string
description: Unique ID to identify the user at the remote provider accepting the invite.
example: 51dc30ddc473d43a6011e9ebba6ca770
email:
federatedCloudId:
type: string
description: Email ID of the user accepting the invite.
description: Federated cloud ID of the user accepting the invite. it should be in the form of username@provider-domain.
MahdiBaghbani marked this conversation as resolved.
Show resolved Hide resolved
example: [email protected]
email:
type: string
description: Email of the user accepting the invite.
example: [email protected]
name:
type: string
description: Name of the user accepting the invite.
Expand All @@ -644,15 +643,19 @@ definitions:
type: object
allOf:
- properties:
userID:
userId:
type: string
description: Unique ID to identify the sender at the local provider.
example: 9302
email:
federatedCloudId:
type: string
description: Email ID of the user that sent the invite.
description: Federated cloud ID of the user who sent the invite. it should be in the form of username@provider-domain.
example: [email protected]
email:
type: string
description: The email of the user who sent the invite.
example: [email protected]
name:
type: string
description: Name of the user that sent the invite.
description: Name of the user who sent the invite.
example: John Doe