Home >> All >> org >> osgi >> service >> [ useradmin Javadoc ]

• org.osgi.service.useradmin: Javadoc index of package org.osgi.service.useradmin.


Package Samples:

• org.osgi.service.useradmin

Classes:

• UserAdminPermission: Permission to configure and access the Role objects managed by a User Admin service. This class represents access to the Role objects managed by a User Admin service and their properties and credentials (in the case of User objects). The permission name is the name (or name prefix) of a property or credential. The naming convention follows the hierarchical property naming convention. Also, an asterisk may appear at the end of the name, following a ".", or by itself, to signify a wildcard match. For example: "org.osgi.security.protocol.*" or "*" is valid, but "*protocol" ...
• Group: A named grouping of roles ( Role objects). Whether or not a given Authorization context implies a Group object depends on the members of that Group object. A Group object can have two kinds of members: basic and required . A Group object is implied by an Authorization context if all of its required members are implied and at least one of its basic members is implied. A Group object must contain at least one basic member in order to be implied. In other words, a Group object without any basic member roles is never implied by any Authorization context. A User object always implies itself. No loop ...
• Authorization: The Authorization interface encapsulates an authorization context on which bundles can base authorization decisions, where appropriate. Bundles associate the privilege to access restricted resources or operations with roles. Before granting access to a restricted resource or operation, a bundle will check if the Authorization object passed to it possess the required role, by calling its hasRole method. Authorization contexts are instantiated by calling the UserAdmin.getAuthorization(org.osgi.service.useradmin.User) 55 method. Trusting Authorization objects There are no restrictions regarding the ...
• Role: The base interface for Role objects managed by the User Admin service. This interface exposes the characteristics shared by all Role classes: a name, a type, and a set of properties. Properties represent public information about the Role object that can be read by anyone. Specific UserAdminPermission objects are required to change a Role object's properties. Role object properties are Dictionary objects. Changes to these objects are propagated to the User Admin service and made persistent. Every User Admin service contains a set of predefined Role objects that are always present and cannot be removed. ...
• UserAdmin: This interface is used to manage a database of named Role objects, which can be used for authentication and authorization purposes. This version of the User Admin service defines two types of Role objects: "User" and "Group". Each type of role is represented by an int constant and an interface. The range of positive integers is reserved for new types of roles that may be added in the future. When defining proprietary role types, negative constant values must be used. Every role has a name and a type. A User object can be configured with credentials (e.g., a password) and properties (e.g., a street ...
• User: A User role managed by a User Admin service. In this context, the term "user" is not limited to just human beings. Instead, it refers to any entity that may have any number of credentials associated with it that it may use to authenticate itself. In general, User objects are associated with a specific User Admin service (namely the one that created them), and cannot be used with other User Admin services. A User object may have credentials (and properties, inherited from the Role class) associated with it. Specific UserAdminPermission objects are required to read or change a User object's ...
• UserAdminEvent: Role change event. UserAdminEvent objects are delivered asynchronously to any UserAdminListener objects when a change occurs in any of the Role objects managed by a User Admin service. A type code is used to identify the event. The following event types are defined: ROLE_CREATED 55 type, ROLE_CHANGED 55 type, and ROLE_REMOVED 55 type. Additional event types may be defined in the future.
• UserAdminListener: Listener for UserAdminEvents. UserAdminListener objects are registered with the Framework service registry and notified with a UserAdminEvent object when a Role object has been created, removed, or modified. UserAdminListener objects can further inspect the received UserAdminEvent object to determine its type, the Role object it occurred on, and the User Admin service that generated it.
• UserAdminPermissionCollection: A UserAdminPermissionCollection stores a set of UserAdminPermission permissions.

Home | Contact Us | Privacy Policy | Terms of Service