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

deviceSecret must be part of DeviceDetails for protocol 2.0 - or rethought #110

Open
ikbalkaya opened this issue Nov 8, 2022 · 3 comments
Assignees

Comments

@ikbalkaya
Copy link

Some context and discussion : ably/ably-java#842 (comment)

Ably protocol requires deviceSecret on push registrations but currently IDL defines deviceSecret as part of LocalDevice which is defined as a subclass of DeviceDetails.

@paddybyers made a comment here ably/ably-java#845 (comment)
explaining that the original intention was right and custom registrar requirement created this design flaw.

As a result,I think either the deviceSecret must be moved to DeviceDetails or the process must be rethought and spec updated.

@ikbalkaya ikbalkaya added the bug Something isn't working label Nov 8, 2022
@sync-by-unito
Copy link

sync-by-unito bot commented Nov 8, 2022

➤ Automation for Jira commented:

The link to the corresponding Jira issue is https://ably.atlassian.net/browse/SDK-2903

@sync-by-unito sync-by-unito bot removed the bug Something isn't working label May 3, 2023
@sacOO7 sacOO7 self-assigned this Dec 19, 2023
@lawrence-forooghian
Copy link
Collaborator

lawrence-forooghian commented Feb 1, 2024

Ably protocol requires deviceSecret on push registrations

This was true of the REST push device registration API when protocol version 2 was first introduced, but is no longer the case; see this internal Slack thread.

What Paddy said about custom registrars needing a way to receive the device identity credentials remains unsolved, but it does not need to be solved as part of implementing protocol v2 in the SDKs.

@sacOO7
Copy link
Collaborator

sacOO7 commented Feb 6, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants