Grouper Users - Open Discussion List

["Black, Carey M." <>]

Chris,

 

Ah… So the Bard was correct (Well, mostly.)  after all.

                An attribute by any other name is still an attribute.  J

 

Thanks.

 

--

Carey Matthew

 

From: Hyzer, Chris [mailto:]
Sent: Monday, September 18, 2017 4:00 PM
To: Black, Carey M. <>
Cc: grouper-users <>
Subject: RE: Copy group looses Loader properties of the group. Bug or feature?

 

Ok, you want to know whats behind the curtain J  They are implemented as new attributes right now.  But still are treated differently in some circumstance… we are chipping away at it to achieve better consistency… J  but yes, in this case it will be an easy lift (probably J )

 

From: Black, Carey M. []
Sent: Monday, September 18, 2017 3:41 PM
To: Hyzer, Chris <>
Cc: grouper-users <>
Subject: RE: Copy group looses Loader properties of the group. Bug or feature?

 

Chris,

 

Hum…..  ( To mis-paraphrase The Bard )

                An attribute by the same name is not an attribute?

 

Maybe an enhancement could be requested to convert all of the “legacy attributes” into the “attribute framework”?  ( So that there is only one “attribute” in the system. )

                Maybe via a tool like the USDU? ( for conversion for systems that have “legacy attributes”)

Or is the long term road map to keep both types of attributes?

 

 

FWIW: REF: https://spaces.internet2.edu/display/Grouper/Custom+Group+Types%2C+Fields%2C+Attributes%2C+Lists

“

Custom Group Types and Fields have been deprecated. It is recommended to use the Attribute Framework capabilities instead of the Custom Group Types and Fields. As of Grouper 2.2, Custom Group Types and legacy attributes represented as Fields are no longer part of Grouper.  Although, the old APIs continue to work for now; they just call the Attribute Framework.  The upgrade procedure for Grouper 2.2 includes steps on the migration.

….

Fields come in two flavors: attributes and lists. (NOTE: As if Grouper 2.2, fields as lists are still valid.  Fields as attributes are not.  Use the Attribute Framework for attributes) 

….

“

 

My install is a clean install of 2.3. (not upgraded from some previous version)

 

--

Carey Matthew

 

From: Hyzer, Chris []
Sent: Monday, September 18, 2017 12:58 PM
To: Black, Carey M. <>; grouper-users <>
Subject: RE: Copy group looses Loader properties of the group. Bug or feature?

 

Yes, good call, the legacy attributes are used for SQL loader jobs and are copied, the LDAP loader uses new attribute framework and are not copied.

 

I opened a jira:

 

https://bugs.internet2.edu/jira/browse/GRP-1605

 

Thanks

Chris

 

From: Black, Carey M. []
Sent: Monday, September 18, 2017 12:27 PM
To: Hyzer, Chris <>; grouper-users <>
Subject: RE: Copy group looses Loader properties of the group. Bug or feature?

 

Maybe the Loader type matters?   ( I would guess that the attributes involved for the two types of jobs would be different. )

  Your example is SQL_SIMPLE.

  Mine is LDAP_GROUPS_FROM_ATTRIBUTES .

 

The only other idea I have is that you were logged in as “GrouperSysAdmin”. I am not. I am “me” with “Wheel Group”. I can see the attributes and the values in the Lite UI. But the Copy function does not work.

 

--

Carey Matthew

 

From: Hyzer, Chris []
Sent: Monday, September 18, 2017 11:04 AM
To: Black, Carey M. <>; grouper-users <>
Subject: RE: Copy group looses Loader properties of the group. Bug or feature?

 

I took a loader group and copied it with the new UI and all checkboxes checked and it copied the loader config:

 

 

-----Original Message-----
From: [] On Behalf Of Black, Carey M.
Sent: Friday, September 15, 2017 9:09 AM
To: grouper-users <>
Subject: [grouper-users] Copy group looses Loader properties of the group. Bug or feature?

 

Since I am separating my loader jobs I want to take an existing loader job ( on a group ) and clone it into a new group with a bit different, but mostly the same loader job.

 

The Copy group has a feature to:

"

Copy attributes?

If you select this option, all custom attributes will be copied to the new group. If you do not have read access to all attributes in the group, you will get a privilege error.

"

 

When I look at the group where the loader job is configured I see attributes like:

Grouper loader LDAP

Grouper loader LDAP attribute filter _expression_

Grouper loader LDAP group name _expression_

Etc...

 

But after copying the group with the "Copy attributes?" set does not yield a new group with those attributes.

 

Is there some configuration setting, or something else that is wrong in my instance, that is not copying those attributes during the group copy?

 

How is "custom attributes" defined/flagged? ( Do I need to flag those loader attributes in a way to allow them to be copied? Maybe assign an attribute to those attribute assignments? )

 

--

Carey Matthew