diff --git a/apps/docs/src/content/docs/en/pages/guides/account-lockout-policy/configure-account-lockout-policy.mdx b/apps/docs/src/content/docs/en/pages/guides/account-lockout-policy/configure-account-lockout-policy.mdx
index a414889bdf..14f0dc7bd5 100644
--- a/apps/docs/src/content/docs/en/pages/guides/account-lockout-policy/configure-account-lockout-policy.mdx
+++ b/apps/docs/src/content/docs/en/pages/guides/account-lockout-policy/configure-account-lockout-policy.mdx
@@ -46,8 +46,8 @@ The response is similar to this one:
{
"data": {
"active": false,
- "max_attempts": 1,
- "blocking_period": 0
+ "max_attempts": 3,
+ "blocking_period": 1440
}
}
```
@@ -75,10 +75,10 @@ curl --request PUT \
--header 'Authorization: Token [TOKEN VALUE]' \
--header 'Content-Type: application/json' \
--data '{
- "active": true,
- "max_attempts": 1,
- "blocking_period": 0
- }'
+ "active": true,
+ "max_attempts": 5,
+ "blocking_period": 60
+ }'
```
The response is similar to this one:
@@ -88,8 +88,8 @@ The response is similar to this one:
"state": "executed",
"data": {
"active": true,
- "max_attempts": 1,
- "blocking_period": 0
+ "max_attempts": 5,
+ "blocking_period": 60
}
}
```
diff --git a/apps/docs/src/content/docs/en/pages/guides/account-lockout-policy/logs-account-lockout-policy.mdx b/apps/docs/src/content/docs/en/pages/guides/account-lockout-policy/logs-account-lockout-policy.mdx
index d40502a122..c4d31bcef9 100644
--- a/apps/docs/src/content/docs/en/pages/guides/account-lockout-policy/logs-account-lockout-policy.mdx
+++ b/apps/docs/src/content/docs/en/pages/guides/account-lockout-policy/logs-account-lockout-policy.mdx
@@ -47,13 +47,13 @@ The response carries one entry per locked account:
```json
{
- "count": 2,
+ "count": 1,
"results": [
{
"id": 1,
"lockout": {
- "locked_at": "20240101T10:20:01",
- "unlock_at": "20240102T10:20:01"
+ "locked_at": "2024-01-01T10:20:01Z",
+ "unlock_at": "2024-01-02T10:20:01Z"
}
}
]
@@ -64,7 +64,7 @@ The keys the response carries:
| Key | Type | Description |
| --- | --- | --- |
-| `count` | integer | Number of blocked user accounts. Example: `2` |
+| `count` | integer | Number of blocked user accounts. Example: `1` |
| `id` | integer | Unique identifier of a user |
| `lockout` | object | Period during which the user account is blocked, with `locked_at` the timestamp the lockout starts and `unlock_at` the timestamp it ends |
diff --git a/apps/docs/src/content/docs/en/pages/guides/account-lockout-policy/unlock-user-account-lockout-policy.mdx b/apps/docs/src/content/docs/en/pages/guides/account-lockout-policy/unlock-user-account-lockout-policy.mdx
index a152d998f0..51037dbbff 100644
--- a/apps/docs/src/content/docs/en/pages/guides/account-lockout-policy/unlock-user-account-lockout-policy.mdx
+++ b/apps/docs/src/content/docs/en/pages/guides/account-lockout-policy/unlock-user-account-lockout-policy.mdx
@@ -32,7 +32,7 @@ Send a `GET` request to the `identity/users` endpoint:
```bash
curl --request GET \
- --url https://api.azion.com/v4/identity/users?locked=true \
+ --url 'https://api.azion.com/v4/identity/users?locked=true' \
--header 'Accept: application/json' \
--header 'Authorization: Token [TOKEN VALUE]'
```
@@ -41,13 +41,13 @@ The response is similar to this one:
```json
{
- "count": 2,
+ "count": 1,
"results": [
{
"id": 1,
"lockout": {
- "locked_at": "20240101T10:20:01",
- "unlock_at": "20240102T10:20:01"
+ "locked_at": "2024-01-01T10:20:01Z",
+ "unlock_at": "2024-01-02T10:20:01Z"
}
}
]
@@ -58,7 +58,7 @@ The keys to read in the response:
| Key | Description |
| ----------- | ----------- |
-| `count` | Number of blocked user accounts. Example: `2` |
+| `count` | Number of blocked user accounts. Example: `1` |
| `id` | Unique identifier of a user |
| `lockout` | Period during which the user account stays blocked. `locked_at` is the timestamp the lockout starts, and `unlock_at` is the timestamp it ends |
@@ -76,15 +76,14 @@ Send a `DELETE` request to the `identity/users/{id}/lockout` endpoint:
curl --request DELETE \
--url https://api.azion.com/v4/identity/users/{id}/lockout \
--header 'Accept: application/json' \
- --header 'Authorization: Token [TOKEN VALUE]' \
- --header 'Content-Type: application/json'
+ --header 'Authorization: Token [TOKEN VALUE]'
```
The response is similar to this one:
```json
{
- "status": "executed"
+ "state": "executed"
}
```
diff --git a/apps/docs/src/content/docs/en/pages/guides/idp/microsoft-entra-user-provisioning-v3.mdx b/apps/docs/src/content/docs/en/pages/guides/idp/microsoft-entra-user-provisioning-v3.mdx
new file mode 100644
index 0000000000..fe79664dbe
--- /dev/null
+++ b/apps/docs/src/content/docs/en/pages/guides/idp/microsoft-entra-user-provisioning-v3.mdx
@@ -0,0 +1,230 @@
+---
+title: Provision Microsoft Entra users with SCIM | v3
+description: >-
+ Turn on SCIM for a Microsoft Entra identity provider with API v3, so Entra
+ creates, updates, and deletes the users and teams of your Azion account.
+meta_tags: 'accounts, users authentication, SAML, Microsoft Entra, SCIM, automated user provisioning'
+namespace: documentation_sso_microsoft_entra_provisioning_v3
+permalink: /documentation/guides/application-security/access-and-compliance/microsoft-entra-automated-user-provisioning-v3/
+---
+import DocCardGroup from '@aziontech/webkit/doc-card-group'
+import DocCard from '@aziontech/webkit/doc-card'
+import DocSteps from '@aziontech/webkit/doc-steps'
+import DocStep from '@aziontech/webkit/doc-step'
+import VersionDeprecated from '~/includes/snippets/versionDeprecated/en/snippet.mdx'
+
+[Provision Microsoft Entra users with SCIM](/en/documentation/guides/application-security/access-and-compliance/microsoft-entra-automated-user-provisioning/)
+
+You can let Microsoft Entra ID create, update, and delete the users and teams of your Azion account through **Automated User Provisioning**, which runs on the System for Cross-domain Identity Management (SCIM) protocol. You turn on SCIM with the Azion API and then configure provisioning in the Microsoft Entra admin center. To set up Microsoft Entra as the identity provider first, refer to [Configure Microsoft Entra SAML for SSO](/en/documentation/guides/application-security/access-and-compliance/sso-microsoft-entra-saml/).
+
+---
+
+## Prerequisites
+
+- SSO enabled on the account. It is not enabled by default, and Azion enables it on request. To request it, refer to [Support guidelines](/en/documentation/support/).
+- Microsoft Entra configured as the identity provider (IdP) of the account, active and linked to the right SAML application. Refer to [Configure Microsoft Entra SAML for SSO](/en/documentation/guides/application-security/access-and-compliance/sso-microsoft-entra-saml/).
+- An Azion personal token. To create one, refer to [Manage personal tokens](/en/documentation/guides/platform/account-and-billing/personal-tokens/).
+- A terminal with `curl`, or an API client such as Postman or Swagger.
+
+---
+
+## Turn on the SCIM integration
+
+Three requests find the identifier of the IdP, read its SCIM status, and turn SCIM on. In each one, replace `[TOKEN VALUE]` with your personal token.
+
+To find the IdP identifier, send a `GET` request to the identity providers endpoint:
+
+```bash
+curl --location 'https://api.azionapi.net/iam/identity_providers' \
+--header 'Accept: application/json' \
+--header 'Authorization: Token [TOKEN VALUE]'
+```
+
+The response is similar to this:
+
+```json
+{
+ "name": "Microsoft Entra IdP",
+ "is_active": true,
+ "protocol": "SAML",
+ "uuid": "1234abc4567",
+ "login_url": "https://sso.azion.com/api/saml2v4/users/scim/1234abc4567/login",
+ "scim_integration": false,
+ "scim_url": null
+}
+```
+
+`is_active` confirms whether the IdP is active, and `uuid` is the identifier of the IdP in Azion. Copy the `uuid` for the next requests.
+
+To read the SAML details of the IdP, send a `GET` request with the `uuid` in place of ``:
+
+```bash
+curl --location 'https://api.azionapi.net/iam/identity_providers/saml2/' \
+--header 'Accept: application/json' \
+--header 'Authorization: Token [TOKEN VALUE]'
+```
+
+The response is similar to this:
+
+```json
+{
+ "uuid": "1234abc4567",
+ "name": "Microsoft Entra IdP",
+ "is_active": true,
+ "sign_in_url": "https://login.microsoftonline.com/123abc/saml2",
+ "entity_id_url": "https://sts.windows.net/123abc/saml2",
+ "login_url": "https://sso.azion.com/api/saml2v4/users/scim/1234abc4567/login",
+ "acs_url": "https://sso.azion.com/api/saml2v4/users/scim/1234abc4567/login",
+ "signature_algorithm": "sha-256",
+ "scim_integration": false,
+ "scim_url": null
+}
+```
+
+`scim_integration` holds the status of the SCIM protocol for the IdP. A `false` value means SCIM is off.
+
+To turn SCIM on, send a `PATCH` request with the `uuid` in place of ``:
+
+```bash
+curl --location --request PATCH 'https://api.azionapi.net/iam/identity_providers/saml2/' \
+--header 'Accept: application/json' \
+--header 'Authorization: Token [TOKEN VALUE]' \
+--header 'Content-Type: application/json' \
+--data '{
+ "scim_integration": true
+}'
+```
+
+The response is similar to this:
+
+```json
+{
+ "uuid": "1234abc4567",
+ "name": "Microsoft Entra IdP",
+ "is_active": true,
+ "sign_in_url": "https://login.microsoftonline.com/123abc/saml2",
+ "entity_id_url": "https://sts.windows.net/123abc/saml2",
+ "login_url": "https://sso.azion.com/api/saml2v4/users/scim/1234abc4567/login",
+ "acs_url": "https://sso.azion.com/api/saml2v4/users/scim/1234abc4567/login",
+ "signature_algorithm": "sha-256",
+ "scim_integration": true,
+ "scim_url": "https://api.azion.com/v4/users/scim/1234abc4567/Users"
+}
+```
+
+SCIM is on for the IdP. Copy the `scim_url` value for Microsoft Entra.
+
+---
+
+## Turn on provisioning in Microsoft Entra
+
+Microsoft Entra connects to Azion through the `scim_url` and a token with the right permissions.
+
+To turn on provisioning in the Microsoft Entra admin center:
+
+1. Go to the [Microsoft Entra admin center](https://entra.microsoft.com/).
+2. Select the card of the application that makes Microsoft Entra the IdP for Azion.
+3. In the menu, in the **Manage** section, select **Provisioning**.
+4. In **Provisioning mode**, select _Automatic_.
+5. In the **Admin Credentials** section, paste the `scim_url` value in **Tenant URL**.
+6. In **Secret Token**, enter a personal token of the Account owner, or of a user with SCIM integration permissions.
+7. Select **Test Connection**. A message confirms that the test succeeded.
+8. Select **Save**.
+
+Provisioning is on. Next, map the users and the groups to provision.
+
+:::note
+You can provision users alone. Each user is then created with no group, and you assign groups and permissions in Azion yourself. When you provision groups, every user in each group is provisioned, and you set the group permissions in Azion afterward.
+:::
+
+---
+
+## Map users
+
+Azion does not support the **Enterprise** schema of Microsoft Entra, so always keep the default user schema. Keep only four attributes, so the user data in Microsoft Entra and in Azion stay aligned.
+
+To map users on the Provisioning configuration page:
+
+1. Open the **Mappings** section.
+2. Select **Provision Microsoft Entra ID Users**.
+3. In **Attribute Mappings**, keep **userName**, **active**, **name.givenName**, and **name.familyName**.
+4. Delete every other attribute.
+5. Make sure the **Enable** switch is on _Yes_.
+6. Select **Save**.
+
+Microsoft Entra sends only the four mapped attributes to Azion.
+
+---
+
+## Map groups
+
+A group in Microsoft Entra becomes a team in Azion. Without group mapping, users are created with no group and no specific permissions, and they reach only unrestricted activities and features.
+
+To map groups on the Provisioning configuration page:
+
+1. Open the **Mappings** section.
+2. Select **Provision Microsoft Entra ID Groups**.
+3. Make sure the **Enable** switch is on _Yes_.
+4. Select **Save**.
+
+Microsoft Entra provisions groups as Azion teams.
+
+---
+
+## Provision users
+
+Microsoft Entra runs a provisioning cycle every *40 minutes*, a fixed interval. A user who becomes **Account owner** stops authenticating through Microsoft Entra and follows the SSO rules configured in Azion. A change in the IdP then cannot lock that user out.
+
+To check the provisioning cycle:
+
+1. Go to the [Microsoft Entra admin center](https://entra.microsoft.com/).
+2. Select the card of the application that makes Microsoft Entra the IdP for Azion.
+3. In the menu, select **Overview**.
+
+The **Overview** shows the provisioning details and the default settings of the cycle.
+
+---
+
+## Provision a user on demand
+
+To skip the wait for the next cycle, provision a user or a group by hand.
+
+To provision on demand on the Provisioning configuration page:
+
+1. In the menu, select **Provision on demand**.
+2. Select the user or group to provision.
+3. Select **Provision**.
+
+Microsoft Entra provisions the selected user or group outside the regular cycle.
+
+---
+
+## Check the users in Azion Console
+
+To check the provisioned users:
+
+
+
+
+ Access [Azion Console](https://console.azion.com/) and, in the account menu, select **Users Management**.
+
+
+
+
+ Look for the provisioned users in the **Users Management** list.
+
+
+
+
+The list shows the users that Microsoft Entra provisioned.
+
+---
+
+## Next steps
+
+
+
+
+
+
+
diff --git a/apps/docs/src/content/docs/en/pages/guides/idp/microsoft-entra-user-provisioning.mdx b/apps/docs/src/content/docs/en/pages/guides/idp/microsoft-entra-user-provisioning.mdx
index 3d5f0cb7cc..36feaca0f4 100644
--- a/apps/docs/src/content/docs/en/pages/guides/idp/microsoft-entra-user-provisioning.mdx
+++ b/apps/docs/src/content/docs/en/pages/guides/idp/microsoft-entra-user-provisioning.mdx
@@ -11,6 +11,9 @@ import DocCardGroup from '@aziontech/webkit/doc-card-group'
import DocCard from '@aziontech/webkit/doc-card'
import DocSteps from '@aziontech/webkit/doc-steps'
import DocStep from '@aziontech/webkit/doc-step'
+import VersionRollingOut from '~/includes/snippets/versionRollingOut/en/snippet.mdx'
+
+[Provision Microsoft Entra users with SCIM | v3](/en/documentation/guides/application-security/access-and-compliance/microsoft-entra-automated-user-provisioning-v3/)
You can let Microsoft Entra ID create, update, and delete the users and teams of your Azion account through **Automated User Provisioning**, which runs on the System for Cross-domain Identity Management (SCIM) protocol. You turn on SCIM with the Azion API and then configure provisioning in the Microsoft Entra admin center. To set up Microsoft Entra as the identity provider first, refer to [Configure Microsoft Entra SAML for SSO](/en/documentation/guides/application-security/access-and-compliance/sso-microsoft-entra-saml/).
@@ -27,14 +30,14 @@ You can let Microsoft Entra ID create, update, and delete the users and teams of
## Turn on the SCIM integration
-Three requests find the identifier of the IdP, read its SCIM status, and turn SCIM on. In each one, replace `[Token value]` with your personal token.
+Three requests find the identifier of the IdP, read its SCIM status, and turn SCIM on. In each one, replace `[TOKEN VALUE]` with your personal token.
To find the IdP identifier, send a `GET` request to the identity providers endpoint:
```bash
-curl --location 'https://api.azionapi.net/iam/identity_providers' \
+curl --location 'https://api.azion.com/v4/iam/identity_providers' \
--header 'Accept: application/json' \
---header 'Authorization: Token [Token value]'
+--header 'Authorization: Token [TOKEN VALUE]'
```
The response is similar to this:
@@ -45,7 +48,7 @@ The response is similar to this:
"is_active": true,
"protocol": "SAML",
"uuid": "1234abc4567",
- "login_url": "https://api.azion.com/v4/users/scim//login",
+ "login_url": "https://sso.azion.com/api/saml2v4/users/scim/1234abc4567/login",
"scim_integration": false,
"scim_url": null
}
@@ -56,9 +59,9 @@ The response is similar to this:
To read the SAML details of the IdP, send a `GET` request with the `uuid` in place of ``:
```bash
-curl --location 'https://api.azionapi.net/iam/identity_providers/saml2/' \
+curl --location 'https://api.azion.com/v4/iam/identity_providers/saml2/' \
--header 'Accept: application/json' \
---header 'Authorization: Token [Token value]'
+--header 'Authorization: Token [TOKEN VALUE]'
```
The response is similar to this:
@@ -68,10 +71,10 @@ The response is similar to this:
"uuid": "1234abc4567",
"name": "Microsoft Entra IdP",
"is_active": true,
- "sign_in_url": "https://login.microsoftonline/123abc/saml2",
+ "sign_in_url": "https://login.microsoftonline.com/123abc/saml2",
"entity_id_url": "https://sts.windows.net/123abc/saml2",
- "login_url": "https://sso.azion.com/api/saml2v4/users/scim//login",
- "acs_url": "https://sso.azion.com/api/saml2v4/users/scim//login",
+ "login_url": "https://sso.azion.com/api/saml2v4/users/scim/1234abc4567/login",
+ "acs_url": "https://sso.azion.com/api/saml2v4/users/scim/1234abc4567/login",
"signature_algorithm": "sha-256",
"scim_integration": false,
"scim_url": null
@@ -83,9 +86,10 @@ The response is similar to this:
To turn SCIM on, send a `PATCH` request with the `uuid` in place of ``:
```bash
-curl --location --request PATCH 'https://api.azionapi.net/iam/identity_providers/saml2/' \
+curl --location --request PATCH 'https://api.azion.com/v4/iam/identity_providers/saml2/' \
--header 'Accept: application/json' \
---header 'Authorization: Token [Token value]' \
+--header 'Authorization: Token [TOKEN VALUE]' \
+--header 'Content-Type: application/json' \
--data '{
"scim_integration": true
}'
@@ -98,13 +102,13 @@ The response is similar to this:
"uuid": "1234abc4567",
"name": "Microsoft Entra IdP",
"is_active": true,
- "sign_in_url": "https://login.microsoftonline/123abc/saml2",
+ "sign_in_url": "https://login.microsoftonline.com/123abc/saml2",
"entity_id_url": "https://sts.windows.net/123abc/saml2",
- "login_url": "https://sso.azion.com/api/saml2v4/users/scim//login",
- "acs_url": "https://sso.azion.com/api/saml2v4/users/scim//login",
+ "login_url": "https://sso.azion.com/api/saml2v4/users/scim/1234abc4567/login",
+ "acs_url": "https://sso.azion.com/api/saml2v4/users/scim/1234abc4567/login",
"signature_algorithm": "sha-256",
"scim_integration": true,
- "scim_url": "https://api.azion.com/v4/users/scim//Users"
+ "scim_url": "https://api.azion.com/v4/users/scim/1234abc4567/Users"
}
```
diff --git a/apps/docs/src/content/docs/pt-br/pages/guias/account-lockout-policy/configure-account-lockout-policy.mdx b/apps/docs/src/content/docs/pt-br/pages/guias/account-lockout-policy/configure-account-lockout-policy.mdx
index 4b90da1695..b5b816591b 100644
--- a/apps/docs/src/content/docs/pt-br/pages/guias/account-lockout-policy/configure-account-lockout-policy.mdx
+++ b/apps/docs/src/content/docs/pt-br/pages/guias/account-lockout-policy/configure-account-lockout-policy.mdx
@@ -3,7 +3,7 @@ title: Configure Account Lockout Policy
description: >-
Ative a Account Lockout Policy com a API da Azion e defina quantas tentativas
de login malsucedidas bloqueiam um usuário, e por quanto tempo.
-meta_tags: 'account management, security, brute force attacks, Azion Account Lockout Policy, política de bloqueio de conta'
+meta_tags: 'account management, security, brute force attacks, Azion Account Lockout Policy'
namespace: docs_guides_account_lockout_policy
permalink: /documentacao/guias/seguranca-de-aplicacoes/acesso-e-compliance/configurar-account-lockout-policy/
---
@@ -46,8 +46,8 @@ A resposta é semelhante a esta:
{
"data": {
"active": false,
- "max_attempts": 1,
- "blocking_period": 0
+ "max_attempts": 3,
+ "blocking_period": 1440
}
}
```
@@ -75,10 +75,10 @@ curl --request PUT \
--header 'Authorization: Token [TOKEN VALUE]' \
--header 'Content-Type: application/json' \
--data '{
- "active": true,
- "max_attempts": 1,
- "blocking_period": 0
- }'
+ "active": true,
+ "max_attempts": 5,
+ "blocking_period": 60
+ }'
```
A resposta é semelhante a esta:
@@ -88,8 +88,8 @@ A resposta é semelhante a esta:
"state": "executed",
"data": {
"active": true,
- "max_attempts": 1,
- "blocking_period": 0
+ "max_attempts": 5,
+ "blocking_period": 60
}
}
```
diff --git a/apps/docs/src/content/docs/pt-br/pages/guias/account-lockout-policy/logs-account-lockout-policy.mdx b/apps/docs/src/content/docs/pt-br/pages/guias/account-lockout-policy/logs-account-lockout-policy.mdx
index ff97bf43f1..ba49e40cd4 100644
--- a/apps/docs/src/content/docs/pt-br/pages/guias/account-lockout-policy/logs-account-lockout-policy.mdx
+++ b/apps/docs/src/content/docs/pt-br/pages/guias/account-lockout-policy/logs-account-lockout-policy.mdx
@@ -47,13 +47,13 @@ A resposta carrega uma entrada por conta bloqueada:
```json
{
- "count": 2,
+ "count": 1,
"results": [
{
"id": 1,
"lockout": {
- "locked_at": "20240101T10:20:01",
- "unlock_at": "20240102T10:20:01"
+ "locked_at": "2024-01-01T10:20:01Z",
+ "unlock_at": "2024-01-02T10:20:01Z"
}
}
]
@@ -64,7 +64,7 @@ As chaves que a resposta carrega:
| Chave | Tipo | Descrição |
| --- | --- | --- |
-| `count` | integer | Número de contas de usuário bloqueadas. Exemplo: `2` |
+| `count` | integer | Número de contas de usuário bloqueadas. Exemplo: `1` |
| `id` | integer | Identificador único de um usuário |
| `lockout` | object | Período durante o qual a conta de usuário fica bloqueada, com `locked_at` sendo o timestamp em que o bloqueio começa e `unlock_at` o timestamp em que ele termina |
diff --git a/apps/docs/src/content/docs/pt-br/pages/guias/account-lockout-policy/unlock-user-account-lockout-policy.mdx b/apps/docs/src/content/docs/pt-br/pages/guias/account-lockout-policy/unlock-user-account-lockout-policy.mdx
index 913446a447..941fe5746a 100644
--- a/apps/docs/src/content/docs/pt-br/pages/guias/account-lockout-policy/unlock-user-account-lockout-policy.mdx
+++ b/apps/docs/src/content/docs/pt-br/pages/guias/account-lockout-policy/unlock-user-account-lockout-policy.mdx
@@ -32,7 +32,7 @@ Envie uma requisição `GET` para o endpoint `identity/users`:
```bash
curl --request GET \
- --url https://api.azion.com/v4/identity/users?locked=true \
+ --url 'https://api.azion.com/v4/identity/users?locked=true' \
--header 'Accept: application/json' \
--header 'Authorization: Token [TOKEN VALUE]'
```
@@ -41,13 +41,13 @@ A resposta é semelhante a esta:
```json
{
- "count": 2,
+ "count": 1,
"results": [
{
"id": 1,
"lockout": {
- "locked_at": "20240101T10:20:01",
- "unlock_at": "20240102T10:20:01"
+ "locked_at": "2024-01-01T10:20:01Z",
+ "unlock_at": "2024-01-02T10:20:01Z"
}
}
]
@@ -58,7 +58,7 @@ As chaves a ler na resposta:
| Chave | Descrição |
| ----------- | ----------- |
-| `count` | Número de contas de usuário bloqueadas. Exemplo: `2` |
+| `count` | Número de contas de usuário bloqueadas. Exemplo: `1` |
| `id` | Identificador único de um usuário |
| `lockout` | Período em que a conta do usuário fica bloqueada. `locked_at` é o timestamp do início do bloqueio, e `unlock_at` é o timestamp do fim |
@@ -76,15 +76,14 @@ Envie uma requisição `DELETE` para o endpoint `identity/users/{id}/lockout`:
curl --request DELETE \
--url https://api.azion.com/v4/identity/users/{id}/lockout \
--header 'Accept: application/json' \
- --header 'Authorization: Token [TOKEN VALUE]' \
- --header 'Content-Type: application/json'
+ --header 'Authorization: Token [TOKEN VALUE]'
```
A resposta é semelhante a esta:
```json
{
- "status": "executed"
+ "state": "executed"
}
```
diff --git a/apps/docs/src/content/docs/pt-br/pages/guias/idp/provisionamento-usuarios-microsoft-entra-v3.mdx b/apps/docs/src/content/docs/pt-br/pages/guias/idp/provisionamento-usuarios-microsoft-entra-v3.mdx
new file mode 100644
index 0000000000..ca8897e959
--- /dev/null
+++ b/apps/docs/src/content/docs/pt-br/pages/guias/idp/provisionamento-usuarios-microsoft-entra-v3.mdx
@@ -0,0 +1,230 @@
+---
+title: Provisione usuários do Microsoft Entra com SCIM | v3
+description: >-
+ Ative o SCIM em um identity provider do Microsoft Entra com a API v3 para que
+ o Entra crie, atualize e exclua os usuários e as equipes da sua conta na Azion.
+meta_tags: 'accounts, users authentication, SAML, Microsoft Entra, SCIM, automated user provisioning'
+namespace: documentation_sso_microsoft_entra_provisioning_v3
+permalink: /documentacao/guias/seguranca-de-aplicacoes/acesso-e-compliance/microsoft-entra-provisionamento-automatizado-de-usuarios-v3/
+---
+import DocCardGroup from '@aziontech/webkit/doc-card-group'
+import DocCard from '@aziontech/webkit/doc-card'
+import DocSteps from '@aziontech/webkit/doc-steps'
+import DocStep from '@aziontech/webkit/doc-step'
+import VersionDeprecated from '~/includes/snippets/versionDeprecated/pt/snippet.mdx'
+
+[Provisione usuários do Microsoft Entra com SCIM](/pt-br/documentacao/guias/seguranca-de-aplicacoes/acesso-e-compliance/microsoft-entra-provisionamento-automatizado-de-usuarios/)
+
+Você pode deixar o Microsoft Entra ID criar, atualizar e excluir os usuários e as equipes da sua conta na Azion com o **Provisionamento Automatizado de Usuários**, que funciona sobre o protocolo System for Cross-domain Identity Management (SCIM). Você ativa o SCIM pela Azion API e depois configura o provisionamento no Microsoft Entra admin center. Para configurar antes o Microsoft Entra como identity provider, consulte [Configure Microsoft Entra SAML para SSO](/pt-br/documentacao/guias/seguranca-de-aplicacoes/acesso-e-compliance/sso-microsoft-entra-saml/).
+
+---
+
+## Pré-requisitos
+
+- O SSO habilitado na conta. Ele não vem habilitado por padrão, e a Azion o habilita mediante solicitação. Para solicitá-lo, consulte [Diretrizes de suporte](/pt-br/documentacao/suporte/).
+- O Microsoft Entra configurado como identity provider (IdP) da conta, ativo e vinculado à aplicação SAML correta. Consulte [Configure Microsoft Entra SAML para SSO](/pt-br/documentacao/guias/seguranca-de-aplicacoes/acesso-e-compliance/sso-microsoft-entra-saml/).
+- Um personal token da Azion. Para criar um, consulte [Gerencie personal tokens](/pt-br/documentacao/guias/plataforma/conta-e-billing/personal-tokens/).
+- Um terminal com `curl` ou um cliente de API, como Postman ou Swagger.
+
+---
+
+## Ative a integração SCIM
+
+Três requisições encontram o identificador do IdP, leem o status do SCIM e ativam o SCIM. Em cada uma, substitua `[TOKEN VALUE]` pelo seu personal token.
+
+Para encontrar o identificador do IdP, envie uma requisição `GET` ao endpoint de identity providers:
+
+```bash
+curl --location 'https://api.azionapi.net/iam/identity_providers' \
+--header 'Accept: application/json' \
+--header 'Authorization: Token [TOKEN VALUE]'
+```
+
+A resposta é semelhante a esta:
+
+```json
+{
+ "name": "Microsoft Entra IdP",
+ "is_active": true,
+ "protocol": "SAML",
+ "uuid": "1234abc4567",
+ "login_url": "https://sso.azion.com/api/saml2v4/users/scim/1234abc4567/login",
+ "scim_integration": false,
+ "scim_url": null
+}
+```
+
+`is_active` confirma se o IdP está ativo, e `uuid` é o identificador do IdP na Azion. Copie o `uuid` para as próximas requisições.
+
+Para ler os detalhes SAML do IdP, envie uma requisição `GET` com o `uuid` no lugar de ``:
+
+```bash
+curl --location 'https://api.azionapi.net/iam/identity_providers/saml2/' \
+--header 'Accept: application/json' \
+--header 'Authorization: Token [TOKEN VALUE]'
+```
+
+A resposta é semelhante a esta:
+
+```json
+{
+ "uuid": "1234abc4567",
+ "name": "Microsoft Entra IdP",
+ "is_active": true,
+ "sign_in_url": "https://login.microsoftonline.com/123abc/saml2",
+ "entity_id_url": "https://sts.windows.net/123abc/saml2",
+ "login_url": "https://sso.azion.com/api/saml2v4/users/scim/1234abc4567/login",
+ "acs_url": "https://sso.azion.com/api/saml2v4/users/scim/1234abc4567/login",
+ "signature_algorithm": "sha-256",
+ "scim_integration": false,
+ "scim_url": null
+}
+```
+
+`scim_integration` guarda o status do protocolo SCIM no IdP. O valor `false` indica que o SCIM está desativado.
+
+Para ativar o SCIM, envie uma requisição `PATCH` com o `uuid` no lugar de ``:
+
+```bash
+curl --location --request PATCH 'https://api.azionapi.net/iam/identity_providers/saml2/' \
+--header 'Accept: application/json' \
+--header 'Authorization: Token [TOKEN VALUE]' \
+--header 'Content-Type: application/json' \
+--data '{
+ "scim_integration": true
+}'
+```
+
+A resposta é semelhante a esta:
+
+```json
+{
+ "uuid": "1234abc4567",
+ "name": "Microsoft Entra IdP",
+ "is_active": true,
+ "sign_in_url": "https://login.microsoftonline.com/123abc/saml2",
+ "entity_id_url": "https://sts.windows.net/123abc/saml2",
+ "login_url": "https://sso.azion.com/api/saml2v4/users/scim/1234abc4567/login",
+ "acs_url": "https://sso.azion.com/api/saml2v4/users/scim/1234abc4567/login",
+ "signature_algorithm": "sha-256",
+ "scim_integration": true,
+ "scim_url": "https://api.azion.com/v4/users/scim/1234abc4567/Users"
+}
+```
+
+O SCIM está ativo no IdP. Copie o valor de `scim_url` para o Microsoft Entra.
+
+---
+
+## Ative o provisionamento no Microsoft Entra
+
+O Microsoft Entra se conecta à Azion pela `scim_url` e por um token com as permissões corretas.
+
+Para ativar o provisionamento no Microsoft Entra admin center:
+
+1. Vá até o [Microsoft Entra admin center](https://entra.microsoft.com/).
+2. Selecione o card da aplicação que torna o Microsoft Entra o IdP da Azion.
+3. No menu, na seção **Manage**, selecione **Provisioning**.
+4. Em **Provisioning mode**, selecione _Automatic_.
+5. Na seção **Admin Credentials**, cole o valor de `scim_url` em **Tenant URL**.
+6. Em **Secret Token**, insira um personal token do Account owner ou de um usuário com permissões de integração SCIM.
+7. Selecione **Test Connection**. Uma mensagem confirma que o teste foi bem-sucedido.
+8. Selecione **Save**.
+
+O provisionamento está ativo. Em seguida, mapeie os usuários e os grupos a provisionar.
+
+:::note[nota]
+Você pode provisionar apenas usuários. Nesse caso, cada usuário é criado sem grupo, e você atribui grupos e permissões na Azion por conta própria. Quando você provisiona grupos, todos os usuários de cada grupo são provisionados, e você define as permissões do grupo na Azion depois.
+:::
+
+---
+
+## Mapeie os usuários
+
+A Azion não suporta o esquema **Enterprise** do Microsoft Entra, então mantenha sempre o esquema de usuário padrão. Mantenha apenas quatro atributos para que os dados do usuário no Microsoft Entra e na Azion fiquem alinhados.
+
+Para mapear os usuários na página de configuração do provisionamento:
+
+1. Abra a seção **Mappings**.
+2. Selecione **Provision Microsoft Entra ID Users**.
+3. Em **Attribute Mappings**, mantenha **userName**, **active**, **name.givenName** e **name.familyName**.
+4. Exclua todos os outros atributos.
+5. Confira se a chave **Enable** está em _Yes_.
+6. Selecione **Save**.
+
+O Microsoft Entra envia à Azion apenas os quatro atributos mapeados.
+
+---
+
+## Mapeie os grupos
+
+Um grupo no Microsoft Entra vira uma equipe (team) na Azion. Sem o mapeamento de grupos, os usuários são criados sem grupo e sem permissões específicas e acessam apenas atividades e recursos sem restrição.
+
+Para mapear os grupos na página de configuração do provisionamento:
+
+1. Abra a seção **Mappings**.
+2. Selecione **Provision Microsoft Entra ID Groups**.
+3. Confira se a chave **Enable** está em _Yes_.
+4. Selecione **Save**.
+
+O Microsoft Entra provisiona os grupos como equipes da Azion.
+
+---
+
+## Provisione os usuários
+
+O Microsoft Entra executa um ciclo de provisionamento a cada *40 minutos*, um intervalo fixo. Um usuário que passa a ser **Account owner** deixa de se autenticar pelo Microsoft Entra e segue as regras de SSO configuradas na Azion. Assim, uma mudança no IdP não consegue bloquear o acesso desse usuário.
+
+Para verificar o ciclo de provisionamento:
+
+1. Vá até o [Microsoft Entra admin center](https://entra.microsoft.com/).
+2. Selecione o card da aplicação que torna o Microsoft Entra o IdP da Azion.
+3. No menu, selecione **Overview**.
+
+A página **Overview** mostra os detalhes do provisionamento e as configurações padrão do ciclo.
+
+---
+
+## Provisione um usuário sob demanda
+
+Para não esperar o próximo ciclo, provisione um usuário ou um grupo manualmente.
+
+Para provisionar sob demanda na página de configuração do provisionamento:
+
+1. No menu, selecione **Provision on demand**.
+2. Selecione o usuário ou o grupo a provisionar.
+3. Selecione **Provision**.
+
+O Microsoft Entra provisiona o usuário ou o grupo selecionado fora do ciclo regular.
+
+---
+
+## Confira os usuários no Azion Console
+
+Para conferir os usuários provisionados:
+
+
+
+
+ Acesse [Azion Console](https://console.azion.com/) e, no menu da conta, selecione **Users Management**.
+
+
+
+
+ Procure os usuários provisionados na lista **Users Management**.
+
+
+
+
+A lista mostra os usuários que o Microsoft Entra provisionou.
+
+---
+
+## Próximos passos
+
+
+
+
+
+
+
diff --git a/apps/docs/src/content/docs/pt-br/pages/guias/idp/provisionamento-usuarios-microsoft-entra.mdx b/apps/docs/src/content/docs/pt-br/pages/guias/idp/provisionamento-usuarios-microsoft-entra.mdx
index 22f5756321..d34c20f4b8 100644
--- a/apps/docs/src/content/docs/pt-br/pages/guias/idp/provisionamento-usuarios-microsoft-entra.mdx
+++ b/apps/docs/src/content/docs/pt-br/pages/guias/idp/provisionamento-usuarios-microsoft-entra.mdx
@@ -3,7 +3,7 @@ title: Provisione usuários do Microsoft Entra com SCIM
description: >-
Ative o SCIM em um identity provider do Microsoft Entra para que o Entra crie,
atualize e exclua os usuários e as equipes da sua conta na Azion.
-meta_tags: 'accounts, users authentication, SAML, Microsoft Entra, SCIM, Provisionamento Automatizado de Usuários'
+meta_tags: 'accounts, users authentication, SAML, Microsoft Entra, SCIM, automated user provisioning'
namespace: documentation_sso_microsoft_entra_provisioning
permalink: /documentacao/guias/seguranca-de-aplicacoes/acesso-e-compliance/microsoft-entra-provisionamento-automatizado-de-usuarios/
---
@@ -11,6 +11,9 @@ import DocCardGroup from '@aziontech/webkit/doc-card-group'
import DocCard from '@aziontech/webkit/doc-card'
import DocSteps from '@aziontech/webkit/doc-steps'
import DocStep from '@aziontech/webkit/doc-step'
+import VersionRollingOut from '~/includes/snippets/versionRollingOut/pt/snippet.mdx'
+
+[Provisione usuários do Microsoft Entra com SCIM | v3](/pt-br/documentacao/guias/seguranca-de-aplicacoes/acesso-e-compliance/microsoft-entra-provisionamento-automatizado-de-usuarios-v3/)
Você pode deixar o Microsoft Entra ID criar, atualizar e excluir os usuários e as equipes da sua conta na Azion com o **Provisionamento Automatizado de Usuários**, que funciona sobre o protocolo System for Cross-domain Identity Management (SCIM). Você ativa o SCIM pela Azion API e depois configura o provisionamento no Microsoft Entra admin center. Para configurar antes o Microsoft Entra como identity provider, consulte [Configure Microsoft Entra SAML para SSO](/pt-br/documentacao/guias/seguranca-de-aplicacoes/acesso-e-compliance/sso-microsoft-entra-saml/).
@@ -27,14 +30,14 @@ Você pode deixar o Microsoft Entra ID criar, atualizar e excluir os usuários e
## Ative a integração SCIM
-Três requisições encontram o identificador do IdP, leem o status do SCIM e ativam o SCIM. Em cada uma, substitua `[Token value]` pelo seu personal token.
+Três requisições encontram o identificador do IdP, leem o status do SCIM e ativam o SCIM. Em cada uma, substitua `[TOKEN VALUE]` pelo seu personal token.
Para encontrar o identificador do IdP, envie uma requisição `GET` ao endpoint de identity providers:
```bash
-curl --location 'https://api.azionapi.net/iam/identity_providers' \
+curl --location 'https://api.azion.com/v4/iam/identity_providers' \
--header 'Accept: application/json' \
---header 'Authorization: Token [Token value]'
+--header 'Authorization: Token [TOKEN VALUE]'
```
A resposta é semelhante a esta:
@@ -45,7 +48,7 @@ A resposta é semelhante a esta:
"is_active": true,
"protocol": "SAML",
"uuid": "1234abc4567",
- "login_url": "https://api.azion.com/v4/users/scim//login",
+ "login_url": "https://sso.azion.com/api/saml2v4/users/scim/1234abc4567/login",
"scim_integration": false,
"scim_url": null
}
@@ -56,9 +59,9 @@ A resposta é semelhante a esta:
Para ler os detalhes SAML do IdP, envie uma requisição `GET` com o `uuid` no lugar de ``:
```bash
-curl --location 'https://api.azionapi.net/iam/identity_providers/saml2/' \
+curl --location 'https://api.azion.com/v4/iam/identity_providers/saml2/' \
--header 'Accept: application/json' \
---header 'Authorization: Token [Token value]'
+--header 'Authorization: Token [TOKEN VALUE]'
```
A resposta é semelhante a esta:
@@ -68,10 +71,10 @@ A resposta é semelhante a esta:
"uuid": "1234abc4567",
"name": "Microsoft Entra IdP",
"is_active": true,
- "sign_in_url": "https://login.microsoftonline/123abc/saml2",
+ "sign_in_url": "https://login.microsoftonline.com/123abc/saml2",
"entity_id_url": "https://sts.windows.net/123abc/saml2",
- "login_url": "https://sso.azion.com/api/saml2v4/users/scim//login",
- "acs_url": "https://sso.azion.com/api/saml2v4/users/scim//login",
+ "login_url": "https://sso.azion.com/api/saml2v4/users/scim/1234abc4567/login",
+ "acs_url": "https://sso.azion.com/api/saml2v4/users/scim/1234abc4567/login",
"signature_algorithm": "sha-256",
"scim_integration": false,
"scim_url": null
@@ -83,9 +86,10 @@ A resposta é semelhante a esta:
Para ativar o SCIM, envie uma requisição `PATCH` com o `uuid` no lugar de ``:
```bash
-curl --location --request PATCH 'https://api.azionapi.net/iam/identity_providers/saml2/' \
+curl --location --request PATCH 'https://api.azion.com/v4/iam/identity_providers/saml2/' \
--header 'Accept: application/json' \
---header 'Authorization: Token [Token value]' \
+--header 'Authorization: Token [TOKEN VALUE]' \
+--header 'Content-Type: application/json' \
--data '{
"scim_integration": true
}'
@@ -98,13 +102,13 @@ A resposta é semelhante a esta:
"uuid": "1234abc4567",
"name": "Microsoft Entra IdP",
"is_active": true,
- "sign_in_url": "https://login.microsoftonline/123abc/saml2",
+ "sign_in_url": "https://login.microsoftonline.com/123abc/saml2",
"entity_id_url": "https://sts.windows.net/123abc/saml2",
- "login_url": "https://sso.azion.com/api/saml2v4/users/scim//login",
- "acs_url": "https://sso.azion.com/api/saml2v4/users/scim//login",
+ "login_url": "https://sso.azion.com/api/saml2v4/users/scim/1234abc4567/login",
+ "acs_url": "https://sso.azion.com/api/saml2v4/users/scim/1234abc4567/login",
"signature_algorithm": "sha-256",
"scim_integration": true,
- "scim_url": "https://api.azion.com/v4/users/scim//Users"
+ "scim_url": "https://api.azion.com/v4/users/scim/1234abc4567/Users"
}
```
diff --git a/apps/docs/src/nav/trees/guides.json b/apps/docs/src/nav/trees/guides.json
index 340372df6c..5f14db1ec4 100644
--- a/apps/docs/src/nav/trees/guides.json
+++ b/apps/docs/src/nav/trees/guides.json
@@ -1723,6 +1723,15 @@
"page": "documentation_sso_microsoft_entra_provisioning",
"products": ["fundamentals"]
},
+ {
+ "page": "documentation_sso_microsoft_entra_provisioning_v3",
+ "products": ["fundamentals"],
+ "hidden": true,
+ "slug": {
+ "en": "microsoft-entra-automated-user-provisioning-v3",
+ "pt-br": "microsoft-entra-provisionamento-automatizado-de-usuarios-v3"
+ }
+ },
{
"page": "docs_guides_account_lockout_policy_logs",
"kind": "how-to-guide",