Services, the kernel, and other system-level components. Implementations must also implement Serializable, equals, and hashCode. While instances of Identity may be used by Services and other components to manage users or task ownership (including serializing and persisting Identitys), this interface is really a means for communicating with the accounting and management system. As such, any combinations of calls to notifyLoggedIn and notifyLoggedOut are valid. Note that an application may still enforce that its users are not allowed to login multiple times, or may only logout if they are logged in.
This class represents identities: real-world objects such as people, companies or organizations whose identities can be authenticated using their public keys. Identities may also be more abstract (or concrete) constructs, such as daemon threads or smart cards.
All Identity objects have a name and a public key. Names are immutable. Identities may also be scoped. That is, if an Identity is specified to have a particular scope, then the name and public key of the Identity are unique within that scope.
An Identity also has a set of certificates (all certifying its own public key). The Principal names specified in these certificates need not be the same, only the key.
An Identity can be subclassed, to include postal and email addresses, telephone numbers, images of faces and logos, and so on.
@see IdentityScope
@see Signer
@see Principal
@version 1.62
@author Benjamin Renaud
@deprecated This class is no longer used. Its functionality has beenreplaced by java.security.KeyStore, the java.security.cert package, and java.security.Principal.
1、在@SQL上声明注解@ReturnGeneratedKeys 2、方法返回值改为欲返回的数值类型，比如long、int等 例子： @ReturnGeneratedKeys @SQL("insert into role(id, name) values(myseq.nextal, :1)") public long save(String name); 在Jade DAO方法声明其返回类型为 {@link Identity}表示，在执行插入语句后返回数据库设置的ID（自增ID等）
@author 王志亮 [qieqie.wang@gmail.com]
@author 廖涵 [in355hz@gmail.com]
To create Identity objects it's strongly recommended to use the {@link IdentityFactory}, because in future releases of OJB the Identity constructors will be no longer reachable or forbidden to use.
NOTE: An Identity object must be unique accross extents. Means all objects with the same top-level class need unique PK values.
@see org.apache.ojb.broker.IdentityFactory @author Thomas Mahler @version $Id: Identity.java,v 1.36.2.14 2005/12/21 22:22:07 tomdz Exp $Note: This isn't exactly the identify transform because the element and attributes names may have been modified from the original document. For example, by default, NekoHTML converts element names to upper-case and attribute names to lower-case. @author Andy Clark @version $Id: Identity.java,v 1.4 2005/02/14 03:56:54 andyc Exp $
The goal of using Identity/Pubkey authentication is to remove the need for static passwords. Instead of providing a password, which could be captured by a keystroke logger or witnessed as you type it, you have a key pair on your disk that you use to authenticate. Your account on the SSH server has a list of Identities/Pubkeys that it trusts, and if you can prove you have the public and private key then you are granted access without supplying a password.
Some of the nice features of this form of authentication are:
In disco, an entity's identity is broken down into its category (server, client, gateway, directory, etc.) and its particular type within that category (IM server, phone vs. handheld client, MSN gateway vs. AIM gateway, user directory vs. chatroom directory, etc.). This information helps requesting entities to determine the group or "bucket" of services into which the entity is most appropriately placed (e.g., perhaps the entity is shown in a GUI with an appropriate icon). An entity MAY have multiple identities. When multiple identity elements are provided, the name attributes for each identity element SHOULD have the same value.
@author Christian Schudt | |
| |
| |
| |
| |
| |
| |
| |
| |
| |