Cant Verify Account

[gsmcenter]

I have problem with Verify My Account

I have my Publisher Id (this the i use in Symbian Developer Certificate Request software) xxx.cer
I have key file too xxx.key
Certs are valid i buy it in january 2011 and on old web works ok

now i download symbian_signed_account_verification_sis.sis
i sign this file my publisher id cert using:
signsis symbian_signed_account_verification_sis.sis symbian_signed_account_verification_sis_SIGNED.sis xxx.cer x.key

I try upload this SIS on web:
https://www.symbiansigned.com/signedui/account/verify

but always i have:
Failed to verify Publisher ID due to certificate validation error

Country set in my profile Poland
No way to somebody other use my cert!
In profile ja have company name for example:
XXXXYYYYXXX.PL
on cert i have with space
XXXX YYYYXXX.PL that has some importance ?

Any ida what i can do ?

[Maveric]

Hi there gsmcenter and welcome to the discussion board!

At least what I know there has been some issues with the signing lately, thats all I know. If that would be the reason for this also. I have request someone to come on and check by the recent messages. This unless someone else brings more info on your case.

Best,
Marko

[jala]

We have similar problem, When We want verify account and when I am trying sign symbian_signed_account_verification_sis using option "Upload SIS File for Signing" I get email: You uploaded a SIS file to be signed with a Development Certificate. This failed because of UID is not registered for the current account., UID: 0x20042BF8, SigningOption: Testing.

[wizard_hu_]

You have to send back the Publisher-ID-signed file on the same page (behind the "[Verify Account]" link), where you have downloaded it.
See "4. Verifying the account" on http://www.developer.nokia.com/Commu...Symbian_Signed

[jala]

Yes I know, there is: Upload a SIS file signed with your Publisher ID. You can use this SIS. But I cant sign downloaded aplication, when I am trying to sign it, there is message "You uploaded a SIS file to be signed with a Development Certificate. This failed because of UID is not registered for the current account., UID: 0x20042BF8, SigningOption: Testing. " on my email. When I try to sign using other way, after upload file I have message: Failed to verify Publisher ID due to certificate validation error. I have of course valid. So it looks that only 1 solution is:

1. Download SIS from link "veryfi account"
2. Sign it using option Dev cert -> Upload SIS File for Signing The service will sign the application for you and notify by email when it is signed.
3. Upload signed app in place "veryfi account"

All looks clear and simple, but I cant sign that aplication... Problem become with new web page...

[wizard_hu_]

Verification is about verifying your identity. If you download a file from a site, then upload it for signing on the same site, then download the result from the same site, and upload it into a different page on the same site, now that does not really prove your identity, you should feel that too.

You need to have a Publisher ID (companies can buy it from TrustCenter), sign a .sis file with it, and upload that one to the Verify account page.
Step 1 in your list is just an ornament (they offer that .sis file because it is small, but you can freely prove your identity via signing HelloWorldBasic with your Publisher ID or anything else).
Step 2 in your list is the misunderstood one.
Step 3 is true.

It is not possible to verify an account without being a company or having support from a company, however unverified accounts of individual developers still allow getting developer certificates for the user grantable and system capabilities, for up to 10 devices.

[jala]

It is not possible to verify an account without being a company or having support from a company, however unverified accounts of individual developers still allow getting developer certificates for the user grantable and system capabilities, for up to 10 devices.

I have Publisher ID... ok I will contact with TC. amd BTW till that time, how can I make generate cert for 10 devices? When I add IMEI, and generate cert, I get cert and key, but still dont work, when I sign app, phone says that invalid cert...

[ltomuta]

The new devcerts are also tied to the UIDs you have reserved for your use in your account. If you try to sign an application using another protected UID, one that you don't have in your current account, the installation will fail.

[charlus]

Hi everybody,
I'm also getting an error when trying to verify my account. I've signed the .sis file that's available on the symbiansigned site using my Publisher's certificate and I'm always getting this error: "Failed to verify Publisher ID due to certificate validation error"

Here's the cert I'm using:
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
50:e5:00:01:00:02:1c:07:b6:e6:12:f7:60:d4
Signature Algorithm: sha1WithRSAEncryption
Issuer: C=DE, O=TC TrustCenter GmbH, OU=TC TrustCenter Class 2 L1 CA, CN=TC TrustCenter Class 2 L1 CA XII
Validity
Not Before: Dec 9 13:07:24 2010 GMT
Not After : Dec 9 13:07:24 2011 GMT
Subject: C=FR, ST=IDF, L=Paris, O=Maeglin Software, OU=Production, OU=Symbian Signed PublisherID, CN=Maeglin Software
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
RSA Public Key: (2048 bit)
Modulus (2048 bit):
00:bb:40:86:f9:dc:55:cf:b5:22:9a:61:ae:7d:f7:
ac:a3:eb:11:82:6e:71:7a:c1:76:c9:c3:7a:7b:5a:
cb:00:01:0a:a9:c5:43:46:50:31:d7:06:22:51:9f:
46:4a:89:49:2e:04:2b:cd:6d:14:c8:03:05:51:52:
41:ea:50:f6:85:2b:7b:81:3e:67:55:c4:ad:92:d5:
7d:8f:ab:c3:4b:ba:83:bc:98:da:c4:d9:10:c1:71:
3e:af:fb:13:ee:4a:5f:5a:98:2a:44:02:e7:d7:cc:
7c:33:5b:aa:ef:9b:79:ab:e9:3e:47:7b:00:ae:ea:
b3:9b:da:93:84:4b:f5:cd:52:2f:20:3e:fc:7e:cc:
7d:f6:61:db:46:2a:cb:fc:b9:13:54:ba:b4:37:c2:
21:1f:e9:ec:05:4a:cf:12:6f:21:39:46:f7:0a:bf:
af:3b:7b:ea:cd:77:d7:8d:9d:d9:5a:46:79:f3:14:
f8:be:2a:af:c7:90:22:47:f6:75:b2:86:f0:b8:95:
33:38:c9:0f:3a:a9:a7:ad:b4:5b:f2:1d:ea:c6:39:
31:cb:f8:73:cd:a1:2c:6d:fc:c1:ef:b6:cd:f5:94:
48:d6:c7:c2:f4:c7:e0:1c:64:6c:43:0f:6a:58:f5:
d8:88:44:bd:db:79:5f:67:37:11:33:77:cc:2a:5a:
c5:b7
Exponent: 65537 (0x10001)
X509v3 extensions:
Authority Information Access:
CA Issuers - URI:http://www.trustcenter.de/certservic..._L1_CA_XII.crt
OCSP - URI:http://ocsp.xii.tcclass2-ii.trustcenter.de

X509v3 Authority Key Identifier:
keyid:09:EF:8C:8B:73:03:81:3C:08:3F:8D:7A:B7:84:55:99:BF:70:BC:14

X509v3 Basic Constraints:
CA:FALSE
X509v3 Certificate Policies:
Policy: 1.2.276.0.44.1.1.6.14.2.1
CPS: http://www.trustcenter.de/cps

X509v3 Key Usage: critical
Digital Signature
X509v3 CRL Distribution Points:
URI:http://crl.xii.tcclass2-ii.trustcent..._L1_CA_XII.crl

X509v3 Extended Key Usage:
TLS Web Client Authentication, Code Signing
Signature Algorithm: sha1WithRSAEncryption
4d:98:d8:28:b0:cc:6f:77:8e:8a:f4:c0:df:05:97:ee:e2:0e:
a6:e8:58:e5:5e:1c:b0:9e:b6:8f:87:43:a1:84:3f:07:d6:2b:
55:bf:c2:d4:fe:7f:68:f1:2f:7b:99:8d:7d:9d:fa:2d:a4:fc:
03:7f:f4:b6:65:bd:7d:6b:a0:eb:d6:86:96:df:46:7a:8c:45:
6c:56:0b:d8:48:53:cb:1a:80:3c:b9:f8:d9:b2:41:2b:42:aa:
c4:de:c9:0f:44:23:10:05:09:03:2e:6a:52:2b:ef:78:cf:1e:
38:5f:df:88:66:9b:03:ba:52:a1:3a:f2:9d:5d:b0:da:09:e1:
f0:f7:62:a5:8a:0b:b5:38:cb:79:07:82:40:13:32:38:f3:9f:
66:23:f5:2c:a6:51:a8:cd:65:d7:f0:75:9b:ea:c4:57:10:96:
e9:d5:9b:86:73:4b:29:69:e6:50:e8:69:a5:b5:8a:29:bb:d8:
c2:fb:fd:ae:a2:16:93:97:14:a5:c5:4e:00:ce:9e:4e:ff:3e:
76:e7:5f:f3:79:04:64:17:76:9e:e4:e4:eb:b8:96:60:62:71:
dd:27:73:bd:86:c3:6c:ef:59:78:b4:3d:b6:f5:16:34:40:bf:
ac:c3:fa:42:ec:c6:18:9a:17:fb:a7:07:b2:c1:f3:26:58:b5:
ec:40:8b:2d

Any hint on how to solve this issue ?
Thanks

[jala]

sorry maybe for stupoid question, but for example I need sighn app for UID 0xE8CF6CCA, how can I add it?

[ltomuta]

You don't need to add those 0xE??????? range UIDs anywhere, they work as is with any certificate. The new certificate restriction affects only the UIDs from the protected range, 0x2???????