With the old one you could send a link with your name and member ID prepopulated.
The only real downside to the acclaim solution is that you need to set it up (although that gives you control over what is displayed) and that it has the word "badge" on it, which causes discontent for a few members of our community.
Even though I use links to my Acclaim badges on my LinkedIn profile (I've made this comment before - see link below) there is something to be said about validating someone's certs directly with the cert vendor as opposed to through a third party. So being able to do that easily through a single URL which prepopulates the required fields just makes everyone's lives easier.
Yes, I just tested it too. I must say I was a bit surprised that it went smoothly --- the way things are going with the rest of the site, I was expecting an error or at least some lag when I clicked on 'Search.'
...validating someone's certs directly with the cert vendor...
Not sure what you mean by the CPE portal as you'd need to give someone your login for them to use that to validate your certs.
With regards to the Community badge system, I can tell you for certain that is not a source of truth so can't be used for validation.
I have one certificate badge (ISSAP) that should show up that doesn't, and one certificate badge (ISSMP) that does show up but shouldn't - not yet anyway!
I wonder if they have heard of
Section 508 of the Rehabilitation Act of 1973
The U.S. Department of Defense is commited to making its electronic and information technologies accessible to individuals with disabilities in accordance with Section 508 of the Rehabilitation Act (29 U.S.C § 794d), as amended in 1999.
We have to post it on the site I help support - AND we have to be compliant as well.
Section 508 applies only to sites (and any computer interfaces) of U.S. government activities.
Thus, the (ISC)2 sites are not mandated to meet Section 508 requirements.
That said, it has some excellent guidance and standards, and I believe should be used by any and all web sites and computer programs.
Lots of good information at the official support site:
I apologize for the non-clarity. I was not proposing cpe nor community be used as a source of certificate validation. I was responding to your observation that the chain of trust is missing with youracclaim.com.
Today, we ask "who is youracclaim.com and what right do they have to validate a certificate?". This is a good question that does not come up with community, cpe, webportal2 or www. We understand those all belong to (ISC)² because they all end in ".isc2.org". Fixing the lack of trust could be as simple as changing the site name to "youracclaim.isc2.org".
Ah ok, I understand your point now. Yes, pretty much all of ISC2's infrastructure is now delivered by 3rd parties, such as Lithium and Salesforce so I guess Acclaim is just another of their partners.
However, Acclaim do have more partners than just ISC2 (pretty much everyone for whom Pearson VUE proctor exams), so that may pose some issues with branding when accessing a member's Acclaim profile through the isc2.org domain that also has another vendor's certs attached.
Unless they can restrict the Acclaim profile to show just the ISC2 certs when it's accessed through the isc2.org domain of course.