I'm using Fabric's Beta "Manage Groups" feature.
I created a group project-android and the alias project-android was offered. After that, I decided to delete the group. Now if I try to create the same group name again, the alias offered is project-android-1.
If I keep creating and deleting the group with the same name, the alias number will keep incrementing. It seems that the alias is not deleted together with the group. Is there a way to get back the original alias?
Beta groups are soft deleted in case they need to be restored at a user's request. Because of this, the alias ID gets incremented if you create a group that uses the same name.
Related
I'm looking for a way to migrate data from LDAP-hosted groups to Google Groups.
With GCDS only the users are migrated, but I would like to migrate the data, do you know any way?
Thanks team
I've migrate groups between different directories using custom-written scripts. This requires some type of mapping between IDs. That is I know the fully qualified DN of each member within the LDAP-hosted group, I can match that up to a record in the new directory -- e.g. cn=lisa,ou=users,o=example has uid lisaj, and there's a corresponding account with the logon id lisaj in the new directory. I've had to do migrations where there was no direct correlation available within the two directories, and successfully linked the two systems using a text file with cross-reference info. A line in the file might say "lisaj 019485-B9184A-9284C-1949" to map my user id in the old system to a record identifier in the new one.
Basic process:
Connect to source LDAP
Find all in-scope groups For each in-scope group, get member list
Find the corresponding group in the new directory (if none exists,
create it)
For each member, find corresponding account in new
directory
Add member to group in new directory
(https://developers.google.com/admin-sdk/directory/v1/reference/members/insert
for Google Groups,
https://github.com/alfasin/Google-Admin-Directory-API has some Python
examples)
As a one-off process, it's pretty simple. If you need the two directories to remain in sync for some time, the script becomes a little more complicated. Assuming the old directory is "authoritative" (the one with the 'right' data -- and you can only make changes in one of the directories, otherwise it's impossible to tell which members actually should be in the group), you need to check the new directory group for any members that aren't a member of the old directory group and remove them as well as add any old directory group members that aren't in the new directory group yet. I generally add a "last modified" constraint to the filter used to locate groups in the old directory -- e.g. find all group objects where the lastModified timestamp is in the past 24 hrs -- to avoid continually reprocessing data for groups that haven't changed.
I am retrieving users for Active directory in Jira 7 by using LDAP. I am trying to reduce the number of users brought from LDAP to a particular group that we have created. So in order to do that i put (objectCategory=group)(cn=WebAgileDevs) in the group object filter along with the default settings. The only thing i change is the Base DN and credentials required. When i save and test it does show me that it is testing 1 group and 15 users which is what i want!(See the screenshot). BUT, when i go and sync it, it brings in 43000 users!! What am i missing???
Test Remote Directory Screenshot
The group filter is used to filter the list of groups that are imported to JIRA, and the user filter is used to filter the list of users that are imported to JIRA. The two need not necessarily correspond. Your group filter would be instructing JIRA to bring in only that one group (into the list of groups), but without further refinement, your user filter will still be pulling in all users, as you noticed. This means that you need to adjust the user filter too.
From your question, you want to import only those users who are a member of a specific group. Atlassian provides some general guidance here.
The last example on that page is particularly relevant for you:
(&(objectCategory=Person)(sAMAccountName=*)(memberOf=cn=CaptainPlanet,ou=users,dc=company,dc=com))
This tells JIRA to pull in only those user objects that are a member of the group cn=CaptainPlanet,ou=users,dc=company,dc=com. You would want to replace this with your cn=WebAgileDevs (plus whatever trailing qualifiers you need to fully qualify the group name).
Documentation is very poor concerning anything but the basic example and I cannot find how to retreive group notification_key or, alternatevly, delete a group using its notification_key_name and then create it again so that I could store its notification_key.
The reason I need this is that I forgot to store the notification_key the first time I created a group for a notification_key_name, for which I used a combination of app name and username. When I try to create a group with the same notification_key_name, I get a response that group already exists. I could probably change the key_name into something else (and in retrospect I should have used something like test-johndoe while testing), but it would be much better to somehow retreive the group key or just delete the entire group and create it again. How do I do that?
I am new to openLDAP.
When I create a new user (generic user), there is a field GID number.
Can somebody explain what this field means?
Does this number needs to be unique? I can select between my posixGroups.
I have the same posixgroups in each country (OU): users, admin, linux.
When I have the list of posixGroups in the GIDnumber, there I cannot see which group from which ou I need to select? How can I solve this?
When you select a posixsgroup for a new user. When I go to that selected group, how can I see that the new user is a member of that group?
Kr,
Joeri
With the gidNumber-attribute you can set the primary group of a user. That group will be used for instance when the user creates a file in a unix-like filesystem in that the file will belong to that group. And it doesn't need to be unique.
As you created the same group names under different subtrees there is no easy way to differentiate between those equally named groups. Easiest solution would be to rename those groups to include a hint to the subtree. But to be honest Personally I'd see whether it is necessary to have the same group in different subtrees and try to consilidate that to only three groups.
In my Bugzilla 3.4.4 (maybe others too) it seems that newly created user without any rights assigned can search thru all bugs. Is it possible to block it so that users can only see them when they are assigned to the right groups?
Yes , this is possible.
Administration/Products/choose the product you want to hide/press "Edit Group Access Controls"
If you set the options of the product group to Mandatory/Mandatory without marking any of the check-boxes ,
any user that is not part of that group , will not see the bugs related to it at all.
This will work in case of new users , due to the fact that new users don't get that permission automatically (by default).
TIP: instead of manually creating group for each product , you can set Administration/Parameters/Group Security/makeproductgroups to ON
NOTE: this is true for Bugzilla 4.2.1