Hartti Suomela's Forum Nokia Blog
Cingular and Java Security Domains - take 2
hartti | 10 January, 2007 20:38
A couple of month's back I wrote about Cingular's approach to MIDP security domain thinking, and stated "as the document has not changed for almost a year now, I think I can summarize the main points of the doc (without needing to update this entry right away)."
Boy, was my timing bad...
Few weeks later Cingular updated the document in question (you need to register to the Cingular developer site to read this document - registration is free). According to this new police the MIDlets in untrusted and trusted 3rd party domain are pretty powerless.
There is no access to socket connections, PIM, file system, SMS messaging, MMS messaging, Bluetooth, or location information from untrusted domain. Also HTTP-access has only "ask always" option available.
But the new policy really cripples the 3rd party trusted domain. There is no access to socket connections, PIM, file system, Bluetooth, or location information from this domain either. Also messaging has only "ask always" option available, and network connectivity has no "blanket" option available.
What comes to the location information, there is no access to that info from the semi-trusted operator domain either (called Cingular preferred).
Java, Testing |
Next | 
Previous |
Comments (9) | 
Trackbacks (1)
Comments
Re: Cingular and Java Security Domains - take 2
Digitale | 12/01/2007, 16:50
I wonder how the vision of mobile internet can become true when in the same time tools are given to operators to keep their walled gardens up.
I doubt that we will see a boom of location aware services until everything that is needed is a permission from the user. Also S60 Browser should have user grantable way to determine location, JavaScript extension for example so that it could be easily used by web 2.0 apps.
Re: Cingular and Java Security Domains - take 2
hartti | 16/01/2007, 09:32
My timing just seems to be off...Less than week after the second blog post on this issue, Cingular seems to be no disappearing as a brand name. The brand will be phased out, giving way to AT&T.
http://news.com.com/ATT+to+phase+out+Cingular+brand/2100-1039_3-6149743.html
Hartti
Re: Cingular and Java Security Domains - take 2
binduramarao | 15/02/2007, 02:33
I have tried to transfer the test software (EventSharing.jad, EventSharing.jar) provided by Nokia with its:
MIDP_PIM_API_Developers_Guide_v2_0_en.zip
When I try to install it afer a transfer using Nokia's PC Suite over Bluetooth, the installation
stops with the progressbar at about 70%. An error is displayed that says: Authorization Failed!
Does look like PIM access or file system access is completely blocked. Must be Nokia doing it,
which would be a bummer, or Cingular tryng to block it - which is a shame.
Any Solution/ work around?
Bindu Rama Rao
Bitfone Corp.
Re: Cingular and Java Security Domains - take 2
hartti | 15/02/2007, 22:41
I am assuing that the phone you are trying to transfer this file to is a Cingular-branded phone. The limitation is a requirement from Cingular (as you probably noticed in the write-up above). The solution is that you either use generic (non-branded phone) or try to get Cingular to sign your MIDlet (requires partnering). More information about Cingular's security domain policy is available on Cingular's developer Web sitedeveloper.cingular.com
Hartti
www.movy.tv
Mark Krebs | 07/11/2007, 19:21
I am wondering if this Cingular policy will affect our midlet...found in the How-to document link on the main www.movy.tv page.
Movy.tv is a mobilizing video/audio UGC site.
Normally we run very well on Nokia handsets and we haven't had problems with Cingular in the past
Re: Cingular and Java Security Domains - take 2
hartti | 08/11/2007, 22:05
Mark, depends what your MIDlet tries to do. In case you get into some problems, you could try to contact AT&T to find out if they could sign your MIDlet
streaming video to AT&T Cingular Nokia handsets
mskrebs | 16/04/2008, 23:32
It's working. We are streaming multimedia, live and archived to Nokia handsets. Our client midlet
either uses the embedded 3gp player or we use our own mpeg4 j2me video decoder. Aside from movy.tv, our other applications work as well -
http://www.logovisionwireless.com/LogovisionMovidityBrochure.doc
We are neither using rtsp or progressive downloading.
streaming video to AT&T Nokia handsets
vijaypatidar | 24/06/2008, 14:38
hi,
i am doing video recording from nokia 6500 and 6126
but after some sec of video recording my application on these handsets stop responding so what should i do to make a right video recording.
Re: Cingular and Java Security Domains - take 2
coultonp | 11/01/2007, 15:19
As a European developer I find it difficult to envision how people can innovate and experiment under such conditions and it seems opportunites will be lost under such a stifiling regeme.