RSA ID number validation ?

[Necuno]

is there some post and get i can preform to validate it online somewhere ?

 

[Myrrdin]

http://geekswithblogs.net/willemf/archive/2005/10/30/58561.aspx

 

[Necuno]

http://geekswithblogs.net/willemf/archive/2005/10/30/58561.aspx

thanks

 

[foozball3000]

Keep in mind that it's never 100% accurate...
I tested a friend's id on our forensic software. Her official ID is not valid, but as long as its the same number that is registered in Home Affairs... its fine.

 

[Necuno]

Keep in mind that it's never 100% accurate...
I tested a friend's id on our forensic software. Her official ID is not valid, but as long as its the same number that is registered in Home Affairs... its fine.

o well at least its a start

 

[foozball3000]

o well at least its a start

In SA, you can be lucky if the first 6 digits corrospond to your Date of Birth

 

[Raithlin]

As a rule, we test the first 10 digits - this is in line with changes made some years ago. It's still not perfect, but it does give a unique number you can compare with those ID numbers that have changed in the past 14 years or so.

 

[Necuno]

As a rule, we test the first 10 digits - this is in line with changes made some years ago. It's still not perfect, but it does give a unique number you can compare with those ID numbers that have changed in the past 14 years or so.

ok and how would you test the first 10 digits ?

 

[FarligOpptreden]

Keep in mind that it's never 100% accurate...
I tested a friend's id on our forensic software. Her official ID is not valid, but as long as its the same number that is registered in Home Affairs... its fine.

Yeah - that script only works about 70% of the time. Since a lot of ID numbers get loaded onto our web-based solution (we provide a human capital management solution), we have a lot of problems with ID validation. I've tried several different versions of the same algorithm, but clients keep on complaining that some ID numbers get rejected. So we had to revert back to only checking on length (13 digits long) and first 6 digits vs. the date of birth. Sloppy, I know, but usable for now... (Plus a LOT less complain-mails from clients)

 

[foozball3000]

Yeah - that script only works about 70% of the time. Since a lot of ID numbers get loaded onto our web-based solution (we provide a human capital management solution), we have a lot of problems with ID validation. I've tried several different versions of the same algorithm, but clients keep on complaining that some ID numbers get rejected. So we had to revert back to only checking on length (13 digits long) and first 6 digits vs. the date of birth. Sloppy, I know, but usable for now... (Plus a LOT less complain-mails from clients)

Same as we do. But we do gender check as well...

 

[FarligOpptreden]

Funny thing though - most of the ID numbers even have the gender as incorrect! You won't believe how many queries we get about that... We have a report that lists all data anomalies (including the ID field mismatches) and still have those validations in, but for the front-end we just do the basic validation.

 

[foozball3000]

Funny thing though - most of the ID numbers even have the gender as incorrect! You won't believe how many queries we get about that...

lol! I wouldn't know... We only flag them with a comment, and the client goes and sorts it out.

 

[FarligOpptreden]

...and DO they actually sort it out?

 

[Raithlin]

I'll check if I can get that code, and let you know how we do it.

 

[kiepie]

In accordance with the legislation,
the control figure which is the 13th digit of all identity numbers which have 08 and 09 is
calculated as follows using ID Number 800101 5009 087 as an example:

* Add all the digits in the odd positions (excluding last digit).
8 + 0 + 0 + 5 + 0 + 0 = 13...................[1]
* Move the even positions into a field and multiply the number by 2.
011098 x 2 = 22196
* Add the digits of the result in b).
2 + 2 + 1 + 9 + 6 = 20.........................[2]
* Add the answer in [2] to the answer in [1].
13 + 20 = 33
* Subtract the second digit (i.e. 3) from 10. The number must tally with the last number in the ID Number. If the result is 2 digits, the last digit is used to compare against the last number in the ID Number. If the answer differs, the ID number is invalid.

How can the result be two digits? If you subtract 0-10=10?

 

[Necuno]

from this 13 + 20 = 33

you take the second number and minus ten by it 10 -3 = 7 which is same as the 13th number in the id number 800101 5009 087

 

[paulka007]

from this 13 + 20 = 33

you take the second number and minus ten by it 10 -3 = 7 which is same as the 13th number in the id number 800101 5009 087

Yes, but its one digit, i.e. 7 is one digit. But if the second digit is a zero, for instance, 10 + 20 = 30 hence

10 - 0 = 10 then you use the zero.

So, if you ever come across a round number in the last step, the last digit in the ID is 0.

 

[Necuno]

Yes, but its one digit, i.e. 7 is one digit. But if the second digit is a zero, for instance, 10 + 20 = 30 hence

10 - 0 = 10 then you use the zero.

So, if you ever come across a round number in the last step, the last digit in the ID is 0.

it has been noted that this method is not perfect though.... still so who as an id number that ends rounded ?

 

[Veroland]

We have used it to check the last digit some years ago, it seemed to have worked fairly well as we got very few complaints.

 

[Raithlin]

@Necuno, are you wanting to validate using js, or some server-side script?