Skip to content

Commit 7725892

Browse files
committed
Feedbacks from Mark
1 parent e7a2c34 commit 7725892

1 file changed

Lines changed: 15 additions & 9 deletions

File tree

content/en/docs/howto/monitoring-troubleshooting/populate-user-type.md

Lines changed: 15 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -24,25 +24,31 @@ The *Mendix Metering* module relies on this attribute to ascertain the end-user
2424

2525
{{< figure src="/attachments/howto/monitoring-troubleshooting/populate-user-type/user-type-enumeration.png" class="no-border" >}}
2626

27-
## Approach
27+
## Assigning UserType for Existing Users of IAM Modules
2828

29-
{{% alert color="info" %}}
30-
This approach is for end-users who are already set up in your app. For new end-users who onboard into your app, you can implement a similar logic to set the UserType attribute during initial end-user creation.
31-
{{% /alert %}}
29+
The simplest method to set the user type is by using the Identity and Access Management (IAM) modules, which require only configuration without the need to develop a microflow. Mendix offers you the following IAM modules:
3230

33-
Outlined below is an example of a module that can be used to update UserType attribute. You will need to adapt the module logic for classifying your own internal and external end-users.
31+
* [OIDC](https://docs.mendix.com/appstore/modules/oidc/)
32+
* [SCIM](https://docs.mendix.com/appstore/modules/scim/)
33+
* [SAML](https://docs.mendix.com/appstore/modules/saml/)
3434

35-
### Assigning UserType for Existing Users of IAM Modules
36-
37-
The simplest method to set the user type is by using the IAM modules, which require only configuration without the need to develop a microflow. Alternatively, you can build a custom microflow as described in the [Populating UserType for Existing Users of an App](#using-microflow) section below.
35+
Alternatively, you can build a custom microflow as described in the [Populating UserType for Existing Users of an App](#using-microflow) section below.
3836

3937
When connecting your app with an IdP, set up the user type through the capabilities of the OIDC SSO, SCIM, or SAML module. The user type is now configured in the User Provisioning, which is integrated into the OIDC SSO, SCIM, and SAML modules. This means you can directly configure end-users of your application as `internal` or `external` in the **User Provisioning** tab of your app. Based on this configuration, users are updated each time they log in. These modules allow you to set the user type per IdP as the source of your end-users, assuming that separate IdPs are used for `internal` and `external` users.
4038

4139
For more information, refer to the User Provisioning section of the following modules:
4240

4341
* [OIDC SSO](/appstore/modules/oidc/#custom-provisioning-rt)
44-
* [SAML](/appstore/modules/saml/#custom-provisioning-rt)
4542
* [SCIM](/appstore/modules/scim/#user-provisioning)
43+
* [SAML](/appstore/modules/saml/#custom-provisioning-rt)
44+
45+
## Assigning UserType Using a Microflow
46+
47+
{{% alert color="info" %}}
48+
This approach is for end-users who are already set up in your app. For new end-users who onboard into your app, you can implement a similar logic to set the UserType attribute during initial end-user creation.
49+
{{% /alert %}}
50+
51+
Outlined below is an example of a module that can be used to update UserType attribute. You will need to adapt the module logic for classifying your own internal and external end-users.
4652

4753
### Domain model
4854

0 commit comments

Comments
 (0)