Symbian Signed renewal

[enstedt]

As you may already know, we are renewing Symbian Signed service during June 2011. Here you can find a list things that will change. Also feel free to ask more detailed questions in this thread.

- The user interface is totally different from the old and much easier to use
- One account / Publisher ID, we recommend merging multiple accounts to one
- No need for a separate tools on your PC
- IMEIs and UIDs needs to be in your Symbian Signed account in order to get Development Certificates and submit applications
- No need to define capabilities for the development certificates
- To submit applications for testing, the account needs to be verified with a Publisher ID

We will use the 21st of June 2011 to transfer over to the new system. This means Symbian Signed will be closed during the 21st of June.

Regards,
Symbian Signed team

[toby_gray]

Will it still be possible to use the separate tools on the PC to generate requests for development certificates?

[localizationer]

"One account / Publisher ID, we recommend merging multiple accounts to one" what's details?
I have several account,what would happend after 21st of June 2011 ?

And i have an account on nokia.symbiansigned.com, what would happend about this account?

thanks.

[lithgow]

Do we still need a Publisher Id to get a dev cert?

[wizard_hu_]

Do we still need a Publisher Id to get a dev cert?

Obviously yes. Which part of this thread appears to suggest otherwise?
However in the likely case you are not familiar with the Ovi Publisher programme (registration costs 1 EUR), note that it grants devcert for 5 devices with user and system capabilities.

[lithgow]

Obviously yes. Which part of this thread appears to suggest otherwise?

Nothing explicitly suggested that, but there are clearly major changes to the infrastructure, so I was hopeful that common sense had prevailed.

However in the likely case you are not familiar with the Ovi Publisher programme (registration costs 1 EUR), note that it grants devcert for 5 devices with user and system capabilities.

Yes, I've already done that, thanks. It is incredibly inconvenient though -- and how do you run a beta program with only five devices?

Compared to UIQ 3, Nokia's insistence on every app being signed and preventing easy access to developer certs without paying US$200 per year for a Publisher Id is a real barrier for casual developers, you know. And, since UIQ 3 seemed to be accepted by operators, it's not a restriction that can be blamed on them -- I'm not really sure why Nokia enforces such a restrictive practice on devices.

Just some feedback.

Regards,
Malcolm.

[farewellwish]

What would happen to the current account? Will it be move to the new service or do we have to apply for a new account ; since the new one need to tie Publisher ID.

[Mark15021]

We have two symbian signed accounts and one publisher id.How to do with it?

[qqengineer]

1. We have 3 accounts, two of which are for normal SymbianSigned, the other is for SymbianSigned for Nokia. Is is possible to merge them into one?
2. Will UIDs in different accounts be merged after the accounts are merged?
3. In case we don't merge, what happened if an app containing UIDs that are registered in account A is submitted to ExpressSigned in account B, although they are of the same Publisher ID?
4. These accounts are of the same Publisher ID and have been logined many times to successfully submit apps to Express Signed/Certificated Signed. Does it mean they are already verified with that Publisher ID? If not, how do I know if any of them is verified and how to make them verified?
5. Will the new dev certs requested contain ALL capabilities?
6. We often get apps Express Signed and then submitted to OVI store. Can we just ignore this step? Will it take longer time before the app become available in the market if we ignore this step?

[rippe]

The only tool which will be needed is the TC Trustcenter's tool used to transfer the Publisher ID from a P12 package to KEY and CER files. It will not be possible to use any other tools.

[rippe]

localizationer,

1. All your accounts will remain.
2. We are checking the details with Ixonos if we could merge all accounts to one or how this should be done.

Stay tuned.

[rippe]

If "13" capabilities and maximum of 10IMEIs is enough, then you do not need a Publisher ID to get a development certificate. The system will create a key and cer for you.

If you need more capabilities or IMEIs then you need to Verify your account. This is done by signing a SIS with your Publisher ID, uploading that to the system and if everything goes OK, the account is verified. The Verified status remains as long as you Publisher ID is valid. With Verified status you can get "17" capabilities and up to 1000IMEIs to the development certificate and the system will create the key and cer for you.

[rippe]

We tried to use an alternative way to authenticate users than the Publishe ID. Naturally the requirements are quite high, the what ever would have needed to be available globally with a very low cost.

We found one option, but it was good for authenticating persons, but not for companies. Actually there was no way to tie the company name to the account in any reliable way. And using that would have opened a way for anyone to pretend to be creating an appalication for any company without a way to knowing which application came from the company and which didn't.

I'm not loosing hope, but for now this is the case unfortunately.

[rippe]

Your current account will remain. You can then verify it with your Publisher ID and keep on using it.

[rippe]

1-4. We will be back
5. Unverified account will get "13" capabilities (not NetworkControl, MultimediaDD, CommDD, DiskAdmin, AllFiles, DRM or TCB). Verified account will get all except AllFiles, DRM or TCB.
6. Ovi Store has the possibility to test your applications and signing them. So you can use their option.