You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/admin/sso/ldap.md
+59-1Lines changed: 59 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,4 +69,62 @@ option in the SOO configuration.
69
69
70
70
When creating the user, the platform will use information provided by the LDAP provider
71
71
to create the username. The user will be directed to their settings page where they
72
-
can modify their user details to their preferred values.
72
+
can modify their user details to their preferred values.
73
+
74
+
## Managing Team Membership with LDAP Groups
75
+
76
+
LDAP implementations can also be used to group users
77
+
78
+
To enable this option, select the `Manage roles using group assertions` in the SSO configuration.
79
+
80
+
The following configuration options should then be set:
81
+
82
+
-`Group DN` - this is the base DN to be used to search for group membership.
83
+
-`Team Scope` - this determines what teams can be managed using this configuration. There are two options:
84
+
-`Apply to all teams` - this will allow the SAML groups to manage all teams on the platform. This is
85
+
suitable for a self-hosted installation of FlowFuse with a single SSO configuration for all users on
86
+
the platform.
87
+
-`Apply to selected teams` - this will restrict what teams can be managed to the provided list. This
88
+
is suitable for shared-tenancy platforms with multiple SSO configurations for different groups of users,
89
+
such as FlowFuse Cloud.
90
+
When this option is selected, an additional option is available - `Allow users to be in other teams`. This
91
+
will allow users who sign-in via this SSO configuration to be members of teams not in the list above.
92
+
Their membership of those teams will not be managed by the SSO groups.
93
+
If that option is disabled, then the user will be removed from any teams not in the list above.
94
+
95
+
### LDAP Groups configuration
96
+
97
+
A user's team membership is managed by what groups they are in. When the user logs in, the LDAP provider
98
+
will be queried for a list of groups they are a member of. This can be either as a `member` or `uniqueMember` of a `groupOfNames` or `groupOfUniqueNames` respectively.
99
+
100
+
The group name is used to identify a team, using its slug property, and the user's role in the team.
101
+
The name must take the form `ff-<team>-<role>`. For example, the group `ff-development-owner` will
102
+
container the owners of the team `development`.
103
+
104
+
The valid roles for a user in a team are:
105
+
-`owner`
106
+
-`member`
107
+
-`viewer`
108
+
-`dashboard`
109
+
110
+
*Note*: this uses the team slug property to identify the team. This has been chosen to simplify managing
111
+
the groups in the LDAP Provider - rather than using the team's id. However, a team's slug can be changed
112
+
by a team owner. Doing so will break the link between the group and the team membership - so should only
113
+
be done with care.
114
+
115
+
## Managing Admin users
116
+
117
+
The SSO Configuration can be configured to manage the admin users of the platform by enabling the
118
+
`Manage Admin roles using group assertions` option. Once enabled, the name of a group can be provided
119
+
that will be used to identify whether a user is an admin or not.
120
+
121
+
**Note:* the platform will refuse to remove the admin flag from a user if they are the only admin
122
+
on the platform. It is *strongly* recommended to have an admin user on the system that is not
123
+
managed via SSO to ensure continued access in case of any issues with the SSO provider.
124
+
125
+
126
+
## Providers
127
+
128
+
The following is the node-exhaustive list of the providers that are known to work with FlowFuse LDAP SSO.
If enabled, users can be members of any teams not listed above and their membership/roles are not managed
123
+
by this SSO configuration.
124
+
</template>
125
+
</FormRow>
126
+
<FormRowv-model="input.options.groupAdmin"type="checkbox">Manage Admin roles using group assertions</FormRow>
127
+
<FormRowv-if="input.options.groupAdmin"v-model="input.options.groupAdminName":error="groupAdminNameError"class="pl-4">Admin Users SAML Group name</FormRow>
128
+
</div>
97
129
<FormRowv-model="input.options.provisionNewUsers"type="checkbox">Allow Provisioning of New Users on first login</FormRow>
0 commit comments