First of all, this project is really excellent. I've been using it for a long time
There is a small problem,Avatar is Non editable,When editing personal information
@gnsilence - Thanks for your feedback - this is great idea - I think @aiscrim something similar did in the branch with windows auth. I will add this feature in the future.
BTW: Avatar is currently connected to https://en.gravatar.com/ - @gnsilence
What I did was substituting the gravatar image with the picture coming from Active Directory, but I didn't give the user the option to change it. That would be a valuable new feature indeed.
@gnsilence - Do you want to upload file or post URL for image?
@TomasHubelbauer - Any idea about profile picture?
Thanks!
We can add some input for profile picture url, which is stored in claim like oidc specs says.
I think there could be a flow where if AD is used and the picture is present, take that, if not and the user uploaded a picture file, use that and if not then fallback to Gravatar. That way if you're in AD, it is authoritative, which is most likely what's intended and to change your picture you can talk to your AD admin and if you're not, you can switch between your own picture and the Gravatar one by either uploading or clearing your own picture.
We can add some input for profile picture url
In addition, we could offer file upload and set the claim value to the URL of the uploaded file. I think that might work and provide nice UX (no need to self host the picture or use a service which allows hot linking images)
@TomasHubelbauer Totally agree with you. In the AD scenario I am storing as picture claim the data URI (base64) representation of the picture, which could be an alternative too for the general picture upload. If we go for the hosted pictures instead, then it's probably a good idea to also change the AD picture saving accordingly.
@gnsilence - Do you want to upload file or post URL for image?
@TomasHubelbauer - Any idea about profile picture?
Thanks!
I have two options in mind:
Just to have my two cents. If we are allowing image uploads, there should probably be a Config option that allows you to disable them.
But regardless, I would like it if the Gravitar fallback to remained. Just to provide the option. In fact, this could even just be a Config item that lets you specify Image Upload, Gravitar or AD
Just to have my two cents. If we are allowing image uploads, there should probably be a Config option that allows you to disable them.
But regardless, I would like it if the Gravitar fallback to remained. Just to provide the option. In fact, this could even just be a Config item that lets you specify Image Upload, Gravitar or AD
That's a good idea
Hey, guys,
Thanks for you great efforts. Because I was striving to have a Identity Service instance recently, too.
And I tried to integrated a Cropper.js front end library to preview and crop the loaded picture as avatar.
A primitive demo here:
https://auth.prime-minister.pub/
You can use _Email:[email protected]_, _Password:@WSX2wsx_ to login and have a trying to edit the Avatar.
Basically, the site allow the user to upload image locally at 200KB size, then preview, crop, supress and saved locally, with a hash string to name the supressed pic, and a new identity claim keeping the hash string to connect the identity entity for occasions need to get.
Of course, older hash string and pic will be replaced when user update their new avatar.
Hope the similar function can be integrated into that.
I can share the code, too. But my coding skill really suck, hahahaha.
BTW, I prefer the solution to save user avatar in a local directory, too.

Most helpful comment
In addition, we could offer file upload and set the claim value to the URL of the uploaded file. I think that might work and provide nice UX (no need to self host the picture or use a service which allows hot linking images)