Cliosoft SOS Define User Groups, Permission Groups, Assign Default Groups

When using Cliosoft SOS, we usually define permissions in terms of user groups.

When the permissions are crossed, the MEMBER in the job needs to be defined multiple times.

Is there a way similar to SVN to define a user group, and then add this user group to the MEMBER of the workgroup for quick management! ! ! !

Of course the answer is yes. .

1. User group

——————————————————————————

Open sosd.cfg and set a user group

set group1 {user1 user2 user3}
set group2 {user1 user3 user4}
set group3 {user1 user2 user4}

Use the set command, followed by the user group name, add members using {}, and separate members with spaces.

Working Group MEMBER Citation

GROUP design {
    MEMBER testuser1;
    MEMBER $group1;
    MEMBER $group2;
}
GROUP test {
    MEMBER testuser3;
    MEMBER $group1;
    MEMBER $group3;
}

Define two workgroups, design and test. When defining a user, you can directly add the user name or user group information after MEMBER.

User group information needs to use the $ symbol to make it clear that it is a user group, and multiple MEMBER are separated by semicolon;.

1. Authority group

——————————————————————————

Define a group named: TAGGER, which can perform snapshot, tag, cancel tag and other permissions

ROLE TAGGER {
COMMAND snapshot, tag, tag-B, modattr;
}

The above writing means that TAGGER can execute commands (COMMAND). The executable commands are snapshot, tagging (tag), canceling tag (tag-B), modifying attributes (modattr), and separating commands with commas.

The permissions of the permission group are divided into global permissions and local permissions.

1. Global permissions

If you want to configure a user group with global TAGGER permissions, define it directly in the sosd.cfg file.

TAGGER zhangsan,lisi;

On behalf of zhangsan, lisi has permission to have snapshots, tags, and modification permissions for all files in the world

2. Local authority

If you define local permissions, you need to write TAGGER into the group to achieve

GROUP design {
    MEMBER testuser1;
    MEMBER $group1;
    MEMBER $group2;
    TAGGER zhangsan,lisi;
}
GROUP test {
    MEMBER testuser3;
    MEMBER $group1;
    MEMBER $group3;
}

Here I have defined TAGGER information in design, then zhangsan and lisi only have permission to perform snapshot, tag and other operations on all files of the design work group.

3. Assign the default group

——————————————————————————

When a user has multiple groups, a default group needs to be assigned to the user, otherwise the user will use the first defined work group as the default group (sosd.cfg file from top to bottom)

How to assign a default group to:

USER user1 {
    DEFAULT_GROUP test;
}

Here, we assign user1's default user group as test.

The premise of this operation: The workgroup GROUP must be defined first, and the user belongs to this workgroup.

{{o.name}}
{{m.name}}

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=324130835&siteId=291194637