On Identity-Aware Devices: Putting Users in Control across Federated Services


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News On Identity-Aware Devices: Putting Users in Control across Federated Services
# 1  
Old 04-07-2008
On Identity-Aware Devices: Putting Users in Control across Federated Services

HPL-2008-26 On Identity-Aware Devices: Putting Users in Control across Federated Services - Casassa Mont, Marco; Balacheff, Boris; Rouault, Jason; Drozdzewski, Daniel
Keyword(s): identity management, device, privacy, user control, trust, federated services
Abstract: This paper describes R&D work on "Identity-aware Devices", in the context of federated services. The aim is to put users in control of their credentials and identities and enable simple, secure, trustworthy and transparent access to federated services. Current users' experience in networked and fede ...
Full Report

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. OS X (Apple)

How to control devices (DVD) ??

Hi, I have a problem controlling devices on my iMac. The internal DVD is no longer working. Therefore I have bought a new external DVD, but some programs use the internal by default (Boot Camp for instance). Since iMac, runs UNIX beneath the Mac OS X, I hope to do some magic, by unmounting... (1 Reply)
Discussion started by: ASL123
1 Replies

2. UNIX for Dummies Questions & Answers

control permissions for Active Directory users on AIX

Hello, I've configured an user authentication against Active Directory (Windows Server 2008 R2) on AIX V6 with LDAP. It works fine. And here's my problem: How can I control ldap user permissions on the local AIX machine? E.g. an AD user should be able to write all files of local sys... (1 Reply)
Discussion started by: xia777
1 Replies

3. UNIX for Dummies Questions & Answers

passthrough devices vs. named devices

I am having trouble understanding the difference between a passthrough device and a named device and when you would use one or the other to access equipment. As an example, we have a tape library and giving the command "camcontrol devlist" gives the following output: akx# camcontrol... (1 Reply)
Discussion started by: thumper
1 Replies
Login or Register to Ask a Question
User::Identity::Archive(3pm)				User Contributed Perl Documentation			      User::Identity::Archive(3pm)

NAME
User::Identity::Archive - base class for archiving user information INHERITANCE
User::Identity::Archive is a User::Identity::Item User::Identity::Archive is extended by User::Identity::Archive::Plain SYNOPSIS
use User::Identity::Archive::Plain; my $friends = User::Identity::Archive::Plain->new('friends'); $friends->from(*FH); $friends->from('.friends'); DESCRIPTION
An archive stores collections. It depends on the type of archive how and where that is done. Some archivers may limit the kinds of selections which can be stored. OVERLOADED
METHODS
Constructors User::Identity::Archive->new([NAME], OPTIONS) Option --Defined in --Default description User::Identity::Item undef from undef name User::Identity::Item <required> parent User::Identity::Item undef . description => STRING . from => FILEHANDLE|FILENAME . name => STRING . parent => OBJECT Attributes $obj->description See "Attributes" in User::Identity::Item $obj->name([NEWNAME]) See "Attributes" in User::Identity::Item Collections $obj->add(COLLECTION, ROLE) See "Collections" in User::Identity::Item $obj->addCollection(OBJECT | ([TYPE], OPTIONS)) See "Collections" in User::Identity::Item $obj->collection(NAME) See "Collections" in User::Identity::Item $obj->find(COLLECTION, ROLE) See "Collections" in User::Identity::Item $obj->parent([PARENT]) See "Collections" in User::Identity::Item $obj->removeCollection(OBJECT|NAME) See "Collections" in User::Identity::Item $obj->type User::Identity::Archive->type See "Collections" in User::Identity::Item $obj->user See "Collections" in User::Identity::Item Access to the archive $obj->from(SOURCE, OPTIONS) Read definitions from the specified SOURCE, which usually can be a filehandle or filename. The syntax used in the information SOURCE is archiver dependent. Not all archivers implement "from()", so you may want to check with "UNIVERSAL::can()" beforehand. example: use User::Identity::Archive::Some; my $a = User::Identity::Archive::Some->new('xyz'); $a->from(*STDIN) if $a->can('from'); DIAGNOSTICS
Error: $object is not a collection. The first argument is an object, but not of a class which extends User::Identity::Collection. Error: Cannot load collection module for $type ($class). Either the specified $type does not exist, or that module named $class returns compilation errors. If the type as specified in the warning is not the name of a package, you specified a nickname which was not defined. Maybe you forgot the 'require' the package which defines the nickname. Error: Creation of a collection via $class failed. The $class did compile, but it was not possible to create an object of that class using the options you specified. Error: Don't know what type of collection you want to add. If you add a collection, it must either by a collection object or a list of options which can be used to create a collection object. In the latter case, the type of collection must be specified. Warning: No collection $name The collection with $name does not exist and can not be created. SEE ALSO
This module is part of User-Identity distribution version 0.93, built on December 24, 2009. Website: http://perl.overmeer.net/userid/ LICENSE
Copyrights 2003,2004,2007-2009 by Mark Overmeer <perl@overmeer.net>. For other contributors see Changes. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. See http://www.perl.com/perl/misc/Artistic.html perl v5.10.1 2009-12-24 User::Identity::Archive(3pm)