-
Notifications
You must be signed in to change notification settings - Fork 23
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
feat: rich consents #122
Merged
ionutmanolache-okta
merged 23 commits into
auth0:master
from
cgcladeraokta:feature/rich-consents
Jan 29, 2025
Merged
feat: rich consents #122
ionutmanolache-okta
merged 23 commits into
auth0:master
from
cgcladeraokta:feature/rich-consents
Jan 29, 2025
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Implement an example of fetching rich consent record when transaction linking id is present in the notificaiton.
Fetch consent details in main activity and pass it as intent extra. If the rich consent record is not found render the standrad notification activity.
sam-muncke
reviewed
Dec 12, 2024
sam-muncke
reviewed
Dec 12, 2024
sam-muncke
reviewed
Dec 12, 2024
sam-muncke
reviewed
Dec 12, 2024
ionutmanolache-okta
approved these changes
Jan 29, 2025
fixed tests rollback build version Revert "rollback build version" This reverts commit ee67e36. Revert "fixed tests" This reverts commit d06fee5. Revert "removed base url manipulation" This reverts commit ec4d416. removed base url manipulation fixed tests rollback build version changed dependency between Guardian, GuardianAPIClient, RichConsentsAPIClient. Updated tests removed personal data updated README.md fixed shouldCreateValidRichConsentsAPI test fixed verifyBasicJWT, verifyAccessApprovalJWT tests updated documentation, resources, created tests for appendingPathComponentIfNeeded fixed tests
cgcladeraokta
force-pushed
the
feature/rich-consents
branch
from
January 29, 2025 17:24
7a22ff7
to
994aba1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By submitting a PR to this repository, you agree to the terms within the Auth0 Code of Conduct. Please see the contributing guidelines for how to create and submit a high-quality PR for this repo.
Description
Adds fetch rich consent record capability to guardian sdk.
References
Testing
Checklist