Return-Path: X-Original-To: apmail-incubator-syncope-user-archive@minotaur.apache.org Delivered-To: apmail-incubator-syncope-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2BA69D11D for ; Wed, 24 Oct 2012 12:36:25 +0000 (UTC) Received: (qmail 66793 invoked by uid 500); 24 Oct 2012 12:36:25 -0000 Delivered-To: apmail-incubator-syncope-user-archive@incubator.apache.org Received: (qmail 66764 invoked by uid 500); 24 Oct 2012 12:36:24 -0000 Mailing-List: contact syncope-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: syncope-user@incubator.apache.org Delivered-To: mailing list syncope-user@incubator.apache.org Received: (qmail 66739 invoked by uid 99); 24 Oct 2012 12:36:24 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Oct 2012 12:36:24 +0000 X-ASF-Spam-Status: No, hits=4.2 required=5.0 tests=HTML_MESSAGE,SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [78.134.5.44] (HELO rovere.tirasa.net) (78.134.5.44) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Oct 2012 12:36:19 +0000 Received: from localhost (localhost [127.0.0.1]) by rovere.tirasa.net (Postfix) with ESMTP id 12325186CE6 for ; Wed, 24 Oct 2012 14:35:57 +0200 (CEST) X-Virus-Scanned: amavisd-new at tirasa.net Received: from rovere.tirasa.net ([127.0.0.1]) by localhost (rovere.tirasa.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pJWQ+-s8zoi5 for ; Wed, 24 Oct 2012 14:35:54 +0200 (CEST) Received: from [192.168.0.2] (mogano.tirasa.net [192.168.0.2]) by rovere.tirasa.net (Postfix) with ESMTPSA id 509D4186CE2 for ; Wed, 24 Oct 2012 14:35:54 +0200 (CEST) Message-ID: <5087E0AA.9050100@apache.org> Date: Wed, 24 Oct 2012 14:35:54 +0200 From: =?ISO-8859-1?Q?Francesco_Chicchiricc=F2?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121017 Thunderbird/16.0.1 MIME-Version: 1.0 To: syncope-user@incubator.apache.org Subject: Re: Virtual attributes References: <70399293-A460-474D-8B0D-84A99E746F79@dds.nl> In-Reply-To: <70399293-A460-474D-8B0D-84A99E746F79@dds.nl> X-Enigmail-Version: 1.4.5 Content-Type: multipart/alternative; boundary="------------030403070609010103070707" X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. --------------030403070609010103070707 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit On 24/10/2012 14:23, Jordi Clement ha wrote: > Hi, > we're looking at virtual attributes, a concept support by Apache > Syncope. I've stumbled upon an email thread from 2011 about these > virtual attributes. I've copied the relevant part below, because I > can't find it in the new archives. Here you go at Nabble [1], the only archive for pre-ASF and new mailing list messages. There is some (very concise, though) introduction about virtual attributes at [2]. >> Hi Dino, >> >> Virtual attributes are user attributes that are not stored on the >> Syncope db. If you enter a virtual attribute in the user schema you >> can change its value through the form. >> >> When you save an user, Syncope assign the value of each virtual >> attribute to all resource accounts that define the virtual attribute >> name in their schema map. >> >> In conclusion, virtual attributes value reside only on external >> resources. >> >> Marco > > I understand that virtual attributes are not stored in Syncope, but > only exist in connected systems and that they can be viewed and > modified because of the virtue of being defined in the schema map. So > basically they're referenced and retrieved and displayed or modified > and provisioned only when needed (for instance because of an admin > viewing the users details in Syncope)? Similar to the way Sun Identity > Manager used to deal with references? Correct. Regards. [1] http://syncope-user.1051894.n5.nabble.com/syncope-users-Virtual-Attributes-td5061678.html [2] https://cwiki.apache.org/confluence/display/SYNCOPE/Schema%2C+attributes+and+mapping -- Francesco Chicchiricc� ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member http://people.apache.org/~ilgrosso/ --------------030403070609010103070707 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
On 24/10/2012 14:23, Jordi Clement ha wrote:
Hi, 
we're looking at virtual attributes, a concept support by Apache Syncope. I've stumbled upon an email thread from 2011 about these virtual attributes. I've copied the relevant part below, because I can't find it in the new archives.

Here you go at Nabble [1], the only archive for pre-ASF and new mailing list messages.

There is some (very concise, though) introduction about virtual attributes at [2].

Hi Dino,

Virtual attributes are user attributes that are not stored on the Syncope db. If you enter a virtual attribute in the user schema you can change its value through the form.

When you save an user, Syncope assign the value of each virtual attribute to all resource accounts that define the virtual attribute name in their schema map.

In conclusion, virtual attributes value reside only on external resources.

Marco

I understand that virtual attributes are not stored in Syncope, but only exist in connected systems and that they can be viewed and modified because of the virtue of being defined in the schema map. So basically they're referenced and retrieved and displayed or modified and provisioned only when needed (for instance because of an admin viewing the users details in Syncope)? Similar to the way Sun Identity Manager used to deal with references?

Correct.

Regards.

[1] http://syncope-user.1051894.n5.nabble.com/syncope-users-Virtual-Attributes-td5061678.html
[2] https://cwiki.apache.org/confluence/display/SYNCOPE/Schema%2C+attributes+and+mapping
-- 
Francesco Chicchiriccò

ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member
http://people.apache.org/~ilgrosso/
--------------030403070609010103070707--