picture / ext_provider claim inconsistent
I use the claim
The problem is the
The problem with this comes about sometimes when I login. On occasion there is no
Ultimately, I would like to know what auth provider facilitated that login (google, facebook, etc.). That may or may not be reasonable depending upon how that's implemented in Kinde. That said, the only thing I really care about right now is have a reasonable way to retrieve the user's picture URL. The only way I see that being possible is if:
1) Kinde always provides an
2) Kinde parses the picture information from each integreated OAuth provided and normalizes this value so we can all use it in a consistent way
3) I have to explicitly look for
Right now I have some users that have broken profile images because their picture url is
Thoughts?
ext_providerThe problem is the
picturepictureext_providerpictureThe problem with this comes about sometimes when I login. On occasion there is no
ext_providerUltimately, I would like to know what auth provider facilitated that login (google, facebook, etc.). That may or may not be reasonable depending upon how that's implemented in Kinde. That said, the only thing I really care about right now is have a reasonable way to retrieve the user's picture URL. The only way I see that being possible is if:
1) Kinde always provides an
ext_provider2) Kinde parses the picture information from each integreated OAuth provided and normalizes this value so we can all use it in a consistent way
3) I have to explicitly look for
{"data": {"url": "....", "width": 200, "height": 200, "is_silhouette": false}}pictureRight now I have some users that have broken profile images because their picture url is
{"data": {"url": "....", "width": 200, "height": 200, "is_silhouette": false}}Thoughts?
