Security and Trust Services API for J2ME: Difference between revisions

Revision as of 19:57, 25 May 2007

Latest revision as of 09:32, 30 July 2025

(18 intermediate revisions by 17 users not shown)

Line 1:

{{Expand section|more information about API possibilities and implementation examples|date=August 2007}}

The '''Security and Trust Services API for J2ME (SATSA)''' is a collection of [[Java ME]]-based [[Application programming interface|API]]s that provides compliant devices with additional [[Cryptography|cryptographic]] security features. It permits the communication of a Java ME application with a [[smartcard]] through the [[smart card application protocol data unit|APDU]] and [[JCJava RMICard]] RMI protocols. SATSA was developed under the [[Java Community Process]] as [http://www.jcp.org/en/jsr/detail?id=177 JSR 177].

It covers the following features, not natively supported by the original Java ME platform:

Line 6 ⟶ 7:

* User identification and authentication during the exchange of data with third parties.

===Implementation of SATSA===

The SATSA API is considered an optional feature by [[Sun Microsystems]], and is currently not a partmandated ofin theall Java ME APIphones. However, device manufacturers may include it, if required. Several device manufacturers have already chosen to include SATSA in some products. Among them are several mobile phone manufacturers:

* [[Motorola]]

* [[Nokia]] (from [[Series 40]] onwards, on a selective basis)

* [[Samsung]]

* [[Sony Ericsson]] (from [[Sony Ericsson Java Platform|JP-8]] onwards)

== See Also also==

{{Portal|Computer programming}}

* [https://www.daniptechnologies.com/ Standard for Advanced Encryption]

* [[AES]]

* [[Advanced Encryption Standard]]

{{DEFAULTSORT:Security And Trust Services Api For J2me}}

[[Category:Java device platform]]

[[Category:Java specification requests]]