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

Implement the device authorization endpoint #2

Merged
merged 9 commits into from
Feb 27, 2024
Merged

Implement the device authorization endpoint #2

merged 9 commits into from
Feb 27, 2024

Conversation

nsklikas
Copy link

@nsklikas nsklikas commented Feb 6, 2024

Implement the device authorization endpoint. The changes in this PR are based on the work done in ory#701 (a lot of the work is taken unchanged).

This PR is intended to implement the logic described in paragraphs RFC8628 - Section 3.1 and RFC8628 - Section 3.1.

These changes are tested using a hydra fork.

Even though this PR includes only ~half of the work needed to implement the device flow, it is still quite chunky. Perhaps I should try to break it down further.

Copy link

@alesstimec alesstimec left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good, mostly style comments..

compose/compose_rfc8628.go Outdated Show resolved Hide resolved
compose/compose_rfc8628.go Show resolved Hide resolved
compose/compose_strategy.go Show resolved Hide resolved
config.go Show resolved Hide resolved
config.go Show resolved Hide resolved
oauth2.go Show resolved Hide resolved
storage/memory.go Show resolved Hide resolved
storage/memory.go Show resolved Hide resolved
storage/memory.go Show resolved Hide resolved
token/hmac/hmacsha.go Show resolved Hide resolved
The WriteAccessError is used to construct error responses as described
in Section 5.2 of [RFC6749]. It is not limited to access token
responses.

Perhaps we should rename the function to Rfc6749TokenError.
@nsklikas nsklikas force-pushed the IAM-653 branch 4 times, most recently from cb19a90 to 93b9238 Compare February 9, 2024 12:43
@nsklikas
Copy link
Author

nsklikas commented Feb 9, 2024

I added docs to all public functions/packages and tried to fix as much as possible. I didn't make some of the style changes to keep consistency with the project style.

shipperizer
shipperizer previously approved these changes Feb 9, 2024
Copy link

@alesstimec alesstimec left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

generally looks ok.. a few remaining comments.. and you might want to change the copyright year to 2024 in all the files you've added.

audience_strategy.go Show resolved Hide resolved
fosite.go Show resolved Hide resolved
device_request_handler.go Outdated Show resolved Hide resolved
device_request_handler.go Outdated Show resolved Hide resolved
device_request_handler.go Show resolved Hide resolved
device_request_handler_test.go Outdated Show resolved Hide resolved
device_response.go Show resolved Hide resolved
device_response_writer.go Show resolved Hide resolved
handler/rfc8628/auth_handler_test.go Outdated Show resolved Hide resolved
BarcoMasile
BarcoMasile previously approved these changes Feb 12, 2024
@nsklikas nsklikas merged commit fee676b into canonical Feb 27, 2024
5 checks passed
@nsklikas nsklikas deleted the IAM-653 branch February 27, 2024 09:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants