Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 19 additions & 6 deletions docs/setup/client-registration.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,19 +44,32 @@ Both forms of each indicator are deliberate. The subject token's `aud` must hold

From the LS Login team, 2026-11-03 ([A9, A10](../testbed/assumptions.md#assumptions)): a **facility** is a client's representation in Perun IDM, and a **resource** represents the relationship between that facility and a VO.

**To get a group entitlement,** assign the group to a resource on the service's facility. Krini does this with `ECP_CLN:ADMIN`. A client that needs admin mapping only needs that one group, not the whole `ECP_CLN` structure.
**To get a group entitlement,** create a resource on the facility representing the client and ask the VO admins to assign the group to it. Krini does this with `ECP_CLN:ADMIN`. A client that needs admin mapping only needs that one group, not the whole `ECP_CLN` structure.

**To let anyone with a valid LS Login account log in,** create a second resource for the Lifescience VO and assign its members group. Users outside `ECP_CLN` must be able to log in here, so that [T3](../tests/t3-groups.md#account-b-must-not-be-locked-out) shows a 403 from the node, and not a lockout.
**To let anyone with a valid LS Login account log in,** create a second resource for the Lifescience VO and ask the VO admins to assign its members group. Users outside `ECP_CLN` must be able to log in here, so that [T3](../tests/t3-groups.md#account-b-must-not-be-locked-out) shows a 403 from the node, and not a lockout.

For the test:

1. On the facilities of `tx-test-client`, `tx-test-gateway` and `tx-test-node`, create a resource for the VO that holds the group, and assign the group.
1. On the facilities of `tx-test-client`, `tx-test-gateway` and `tx-test-node`, the maintainer creates a resource for the VO that holds the group, then asks the VO admins to assign the group to each resource.
2. Don't do this for `tx-test-orchestrator`: its missing release is what [T3](../tests/t3-groups.md#release-per-client) compares against.
3. On the facilities of the clients that log in users, `tx-test-client` and `tx-test-public`, create the second resource for the Lifescience VO and assign its members group. Whether clients that only exchange need it, too, is [a question for T3](../tests/t3-groups.md#questions-it-answers).
3. On the facilities of the clients that log in users, `tx-test-client` and `tx-test-public`, the maintainer creates the second resource for the Lifescience VO, then asks the VO admins to assign its members group to each resource. Whether clients that only exchange need it, too, is [a question for T3](../tests/t3-groups.md#questions-it-answers).

The operator's pages on this: [Create (and remove) a resource](https://perunaai.atlassian.net/wiki/spaces/PERUN/pages/670400518/Create+and+remove+a+resource), [How to assign a group(s) to a resource](https://perunaai.atlassian.net/wiki/spaces/PERUN/pages/212828196/How+to+assign+a+group+s+to+a+resource), [Entitlements](https://perunaai.atlassian.net/wiki/spaces/PERUN/pages/209813518/Entitlements), [Perun roles and their rights](https://perunaai.atlassian.net/wiki/spaces/PERUN/pages/1760100400/Perun+roles+and+their+rights).

!!! warning "Known problem: \"Assign groups\""
This project's maintainer could open a facility and create a resource, but in "Assign groups" the Next button stays greyed out and no groups can be added, possibly because of a missing permission. [Which role is needed](../tests/t3-groups.md#questions-it-answers) is a question for the event. Until that's settled, ask the LS Login team to assign the groups, and otherwise go on without: T3 then shows what happens without a release.
### Who can assign groups

Being able to open a facility and create a resource does not establish permission to assign a VO's groups. A greyed-out Next button under "Assign groups" may indicate missing permissions.

The LS AAI team confirmed that **TrustedFacilityAdmin within the relevant VO** enables a maintainer to assign that VO's groups to resources. The VO admins have chosen not to grant this role for this setup and require assignments to be delegated to them.

The VO admins perform group assignments to the resource. The client maintainer creates the resources, then sends the VO admins links to the resource and to groups he wants to assign to the resource.
Comment thread
sourcery-ai[bot] marked this conversation as resolved.
Resolved

### Assigning groups and verifying release

1. Create a resource for the relevant VO on the facility representing the client.
2. Send the VO admins links to the resource and the groups to assign. Ask them to complete the assignment and confirm it. Verify that the groups appear among the resource's assigned groups.
Comment thread
sourcery-ai[bot] marked this conversation as resolved.
Resolved
3. Log in with a test account belonging to the assigned group, and use the session's `userinfo <token-name>` command to inspect the released entitlements. Compare the exact value with `TESTBED_REQUIRED_ENTITLEMENT` in `lslogin.env`; do not assume the example value matches.
4. Repeat the release setup for each service that needs it. For this testbed, follow the facility list above, preserving the deliberate omission for the orchestrator in T3.
5. Use T3 to verify that a user outside the required group can still log in but receives 403 from the node.

**Record:** the exact entitlement in user info ([T3](../tests/t3-groups.md)). Compare it with `TESTBED_REQUIRED_ENTITLEMENT`, whose example value we derived from a known entitlement of the same form.
4 changes: 2 additions & 2 deletions docs/tests/t3-groups.md
Original file line number Diff line number Diff line change
Expand Up @@ -80,9 +80,9 @@ From the LS Login team, 2026-11-03: create a second resource for the Lifescience

This project's maintainer could open a facility and create a resource, but in "Assign groups" the Next button stays greyed out and no groups can be added, possibly because of a missing permission (seen by 2026-11-03).

The operator's roles page lists assigning groups under Trusted facility admin, Resource admin and Resource self service, and not under Facility admin (see [What public documents say](../testbed/assumptions.md#what-public-documents-say)). It doesn't say which one applies here, or who grants it for a VO's group.
The LS AAI team confirmed that **TrustedFacilityAdmin within the relevant VO** enables this assignment. The VO admins have chosen not to grant that role for this setup; maintainers create resources and ask the VO admins to assign groups, as described in [Client registration](../setup/client-registration.md#who-can-assign-groups).

**What it changes:** which role a service's operators need to ask for, and from whom. Without it, nobody can set up group release for a new service by themselves, so this goes into the operator docs of every service in the chain.
**What it changes:** operators should plan for VO-admin involvement when setting up group release, rather than trying to obtain self-service assignment permissions.

### Group entitlements or resource capabilities?

Expand Down
Loading