- Newest
- Most votes
- Most comments
Your Credly badge is issued to a recipient at the time you received your credential. This may be different from your current re:Post email. If you know the email used at the time of your Credly credential and still have access to that email, you may temporarily update your re:Post email, then once verified within re:Post you can attempt to associate your Credly badge. Afterward, you may either keep that updated email or revert back to your preferred email address.
Also worth noting is that changing your Credly default email address will have no effect on the certificate. It seems to be hard coded into it.
If you haven't manually verified your Email on the Re:Post side, try changing your Email in Settings then changing it back to trigger the verification email. Once it's verified on the Re:Post side it will work as long as it matches the Credly Email.
I did it, verified my email on the re:post side, trigger the verification email. My Certs import are all failing.
Note that you have to specify each specific Badge URL. Specifying your general overview badges URL won't work.
How exactly shall we update the email?
Is it under "settings" --> "profile" --> "Email for notifications"?
- Replace
00000000-0000-0000-0000-000000000000
below with your badge id to find the hash:
% curl https://api.credly.com/v1/obi/v2/badge_assertions/00000000-0000-0000-0000-000000000000 | jq -r '.recipient.identity' | sed 's/^sha256\$//g' d58c1142b3073cd201a369c95c5eda296e173a04027af75f11034cf546aa6daf
- Test emails until matched:
% echo -n scott@example.com | shasum -a 256 - d58c1142b3073cd201a369c95c5eda296e173a04027af75f11034cf546aa6daf
- When matched, update re:Post Setting's Profile
Email for notifications
and verify
- Replace
Yes, although I was told this issue is fixed now, so if you try again it might work regardless.
I have updated my email on re:Post and needed to confirm the email firstly before I could add my certification.
I did exactly the same, but without success
I went the other way - I updated my Credly email from my personal account (as I had some certs prior to AWS) to my AWS email (which I use for re:Post). Waited for an overnight update, and it worked just fine today.
Click on the certification Link in your Credly account, then in the bottom right part click on Public Link button, this is the valid link to add your Certification in your profile
You can now add up to three email addresses (within the profile tab in "My Dashboard"). You can add the email address that’s associated with your Credly account, without updating the primary email address that’s associated with your re:Post profile. This should allow you to link your AWS Certification successfully.
Relevant content
- asked 2 years ago
- asked 7 months ago
- asked a year ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 months ago
Specifically, the Credly API replies with a "one-way" SHA256 of the recipient's email at the time of receiving the badge, and compares a hash of the currently verified re:Post email to test for a match. See https://www.credly.com/docs/obi_specified_endpoints#get-badge-assertion for details
The upper and lower case of the email address must be respected