Group membership for wf participants.

georgeMcKinney

We are investigating workarounds for the group membership limits for Solaris/TS 5.5.2

(Our systems folks tell us that the map_secondary_to_primary_gid fix doesn't work in our situation; I've asked them to explain WHY)

Our internal editor type users need to be able to have access to any of the > 20 groups that we currently use, and we are building a tool that will (we hope) allow them to manipulate their own group memberships as they need.

We have (roughly) a separate group for each of the sites we are managing, to keep a site's content inaccessible to other sites' people.

HOWEVER, some of our primary workflow definitions include jobs to be performed by internal administrative users, and it appears that we cannot create a workflow for files in a branch those users aren't currently members of.

In other words, it appears that if a workflow for branch "site1" may at some point require a user "foo" to do a task, the workflow cannot be created (it gives an invalid workflow error) unless "site1" is one of the first 16 groups that "foo" currently belongs to.

I'm in the process of investigating what happens to an existing wf when a possible participant is removed from the "site1" group, but would appreciate a pointer to any info/docs about the group membership requirements for workflow participants.

Thanks,
George McKinney