Skip to content

Conversation

@tung2744
Copy link
Contributor

No description provided.

@tung2744 tung2744 force-pushed the spec-biometric-disabled-user branch from fcca90e to 2cafdf7 Compare April 15, 2025 07:54
@tung2744
Copy link
Contributor Author

  1. We will first handle disabled user in biometric login according to this spec.
  2. We will then revisit the current user statuses to separate "Scheduled deletion/anonymization" from disabled.

list_enabled: false
```
## Errors
Copy link
Contributor

Choose a reason for hiding this comment

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

Given that the OAuth error shape is quite limited, I am thinking if we want to introduce a way to include our API error into a OAuth response.

https://datatracker.ietf.org/doc/html/rfc6749#section-8.5 specifies how to add additional error codes.

We can add a new error code authgear_error. When error=authgear_error, the response will have an extra field authgear_error, where the value is a Authgear API error JSON object.

Then the new SDKs be taught to decode error=authgear_error, throw an instance ServerError to handle this.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

As oauth error could appear in the url, I am not sure if it is appropriate to add field to store the api error json object which could be long.

@tung2744 tung2744 changed the title Specify behavior of disabled user login with biometric [WIP] Specify behavior of disabled user login with biometric Apr 22, 2025
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.

2 participants