cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Influencer I

Verification bug

The various verification issues previously reported are still with us.  (In some sense.)  We've been trying to verify someone, and his dates or issue and expiry are both listed as Jan. 1, 0001.


............
This message may or may not be governed by the terms of
http://www.noticebored.com/html/cisspforumfaq.html#Friday or
https://blogs.securiteam.com/index.php/archives/1468
3 Replies
Highlighted
Community Manager

Re: Verification bug

Thank you. I have passed this information along. 




(ISC)² Community Manager
Highlighted
Community Champion

Re: Verification bug


@rslade wrote:

The various verification issues previously reported are still with us.  (In some sense.)  We've been trying to verify someone, and his dates or issue and expiry are both listed as Jan. 1, 0001.


My "verification verification" system did identify some connectivity issues the day before, but these could easily be on my side - no issues were reported yesterday when you reported your issue.

 

The check I run just looks at what certifications are returned when checking my own credentials, it doesn't look at the dates so I will add that functionality in to make it more comprehensive!

 

Prior to me deploying my checking system, the only time I've seen issues with the dates being returned in a member lookup was during the payment system updates where my certification expiry dates were all set to 9999!

 

This was apparently some kind of database issue, and apparently localised to me and a handful of others - so this points to a similar issue in this case.

 

Highlighted
(ISC)² Team

Re: Verification bug

Thank you for reporting this issue.  We are looking into this further.

 

(ISC)² Member Services