Replacing Group Membership¶
Note: admins only - on premise
This service is designed to replace Board memberships for groups in one login client with replacement groups in another login client.
For example; in order to remove login via Connections but still retain access to all your boards, you will need to replace the group based memberships with replacement groups. For example Sharepoint sites instead of Communities.
- Please be aware that the
targetID below should be set as the ID for your intended login method (ie Microsoft), and the
sourcethat of the login method being removed (ie Connections). These IDs are visible in the URL of the admin page.
- The process is run immediately on the next deployment of the boards app.
- Only run one replica to avoid conflicts, hence
- You can view the logs of the
boards-appmicroservice to see an output of changes to source/target groups
- The command is safe to run multiple times. There will be no new changes unless more group memberships have been imported into the Boards DB.
You have created replacement groups in the target system and have records of the old ID to the new ID.
Create CSV Map File
This process utilises a CSV file to define a map between the old ID and new ID, in the format:
Secret with CSV
Create a secret in the Boards namespace (ie boards) from your CSV file
kubectl create secret generic group-map-secret --from-file=./group-map.csv -n boards
Set the following environment variables to mount the secret created above at a file path in the pod.
app: replicaCount: 1 volumes: - name: group-map-volume secret: secretName: group-map-secret volumeMounts: - name: group-map-volume mountPath: /usr/share/groupmapsecret env: GROUP_MAP_CSV: groupmapsecret/group-map.csv GROUP_MAP_TARGET_CLIENT: 5fd6974dd7c5ede08711432d GROUP_MAP_SOURCE_CLIENT: 5ef2d52f6283afc12efd55a4
Redeploy the Helm chart
helm upgrade boards https://docs.huddo.com/assets/config/kubernetes/kudos-boards-5.2.1.tgz -i -f ./boards.yaml --namespace boards
Review the logs
The logs should output in this format. See that each group was mapped from a
Targetand how many
nodeswere updated with the new value.
Remove Environment variables above and redeploy the Helm chart