dex
dex copied to clipboard
Use jmespath library to support parsing multi-level userInfo when using oauth
Preflight Checklist
- [X] I agree to follow the Code of Conduct that this project adheres to.
- [X] I have searched the issue tracker for an issue that matches the one I want to file, without success.
Problem Description
If the userinfo returned by your OAuth provider does not belong to the root level, the oauth of dex cannot be parsed correctly. as follow:
{
"code": 0,
"data": {
"user_id": "zzz",
"fullname": "yyy",
"email": "xxx"
}
}
Proposed Solution
Use jmespath library to support parsing multi-level userInfo when using oauth.
Alternatives Considered
No response
Additional Information
No response