Subject: Grouper Users - Open Discussion List
- From: Shilen Patel <>
- To: Earl Lewis <>
- Cc: "<>" <>
- Subject: Re: [grouper-users] Attributes
- Date: Fri, 31 May 2013 11:59:44 +0000
- Accept-language: en-US
- Authentication-results: sfpop-ironport01.merit.edu; dkim=neutral (message not signed) header.i=none
You can mark attributes as "internal" to prevent them from being retrieved when making subject api calls (e.g. subject.getAttributes() ), unless you explicitly ask for them. This prevents those attributes from being visible in the Grouper UI for instance. Virtual attributes are usually based on other attributes and you can use _expression_ language to dynamically create them.
This entire video is based on virtual attributes and internal attributes:
Also, part 4 in that series talks about member sorting and searching, which is a use case for using both of these.
I'm trying to figure out the context in which you're using "external attribute." If you're thinking of external users, then these would be attributes of external subjects. This doc goes into detail on that (and there's also a video):
From: Earl Lewis <>
Date: Thursday, May 30, 2013 10:12 AM
To: "<>" <>
Subject: [grouper-users] Attributes
- [grouper-users] Attributes, Earl Lewis, 05/30/2013
Archive powered by MHonArc 2.6.16.