![]() ![]() ![]() The user belongs to multiple groups, and separate rules exist for each group. You intentionally create multiple rules that include the same user by username. ![]() Sometimes, more than one rule can apply to the same user. You will need to manually revoke any such licenses from the user after creating the rule. If your rule has the effect you're aiming for, click Finish & Save Rule to save it.Ĭreating a rule that restricts a user's access to licenses does not automatically revoke any licenses this user has already obtained, even if they are no longer permitted to use these licenses. On the Related Rules tab, you'll see which rules affect their current permissions. On the Result tab, you'll see whether the user or group you selected is allowed to use this product. To do so, select the user or group and a product from their respective dropdown lists and click Check effective permissions. In this step, you can check the effective permissions that will be granted to users based on your current set of rules, including the one that you're creating. This will take you to the Test rule tab of the rule settings. The list will only display products for which you have at least one license in your License Vault.Ĭlick Next. This will take you to the Specify products tab of the rule settings.įrom the dropdown list, select the products you want these users to have access to. ![]() If the name you're looking for is not on the list, check the existing users and groups in JetBrains Hub to make sure that you're typing the name correctly.Ĭlick Next. Simply start typing to see all available user and group names on the suggestion list. In the same window, under Username or group from JetBrains Hub, enter the name of the user or group to which this rule will apply. In the dialog that pops up, enter the name of your rule. Before you begin, make sure that you have configured user authentication in JetBrains Hub. This section walks you through the process of creating an access rule. To restrict global accessĪt the top of the page, clear the Allow users that are not mentioned in the rules to get licenses checkbox.Ĭonfirm your action in the dialog that pops up. Otherwise, none of your users will be able to obtain licenses. If User A requests a CLion license, their request will still be denied.īut if User B requests a CLion or P圜harm license, their request will now also be denied because there are no rules that grant this user access to licenses.īefore restricting global access, make sure to create rules that confugure user access licenses. If User A requests a P圜harm license, they'll still successfully obtain one. Going back to the example with a single rule that grants User A access to P圜harm, here's what will change: To grant them access, you need to create a rule. These users and groups don't have access to any licenses. (No change here.) If there are no rules for a specific user or group: These users and groups only have access to the licenses specified in the rule. If you create a rule for a specific user or group: If you do this, the semantics of your rules will change from restricting access to granting it. You can enforce a stricter license distribution policy so that access is only granted to the users and groups that are explicitly mentioned in your access rules. If User B requests a CLion or P圜harm license, they successfully obtain one because there aren't any rules that restrict their access. If User A requests a CLion license, their request is denied because, according to your rule set, they are only allowed to use P圜harm. If User A requests a P圜harm license, they successfully obtain one. License distribution exampleįor example, let's say you have a single rule that grants User A access to P圜harm licenses. To restrict their access, you need to create a rule. These users and groups have access to any available licenses. If there are no rules for a specific user or group: Here's how it works: If you create a rule for a specific user or group: Rules help you restrict and fine-tune user access. Default license distribution policyīy default, before any rules are created, all users authorized by JetBrains Hub have access to all licenses. In this section, you'll learn how licenses are distributed before any rules are created and how rules change user access. To restrict and fine-tune access to licenses within your organization, configure access rules and priorities. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |