testeiya 0.2.0 → 0.3.1-0.1

package/skills/testeiya/testomatio-docs/docs/integrations/report-notifications/slack.md

@@ -1,82 +0,0 @@
----
-title: Slack Notifications
-description: Learn to configure Slack notifications in Testomat.io to receive test run updates directly in a Slack channel. The guide explains creating a Slack app, enabling webhooks, generating a Webhook URL, and linking it to Testomat.io for seamless updates.
-type: article
-url: https://docs.testomat.io/integrations/report-notifications/slack
-head:
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Testomat.io, notifications, Slack notifications, notification rules, automated alerts, CI notifications, QA tools, notification channels, Report Notification, Basic rules, Advanced rules engine, Run Group Notifications, test management, test automation, software testing, Slack channel, incoming webhook 
----
-
-Testomat.io can send Notifications to a specific **Slack channel**. Prepare a channel inside Slack workspace to which notifications will be sent:
-
-![Testomat.io - Notification Slack](./images/Slack_1.png)
-
-To enable Slack notification [create an incoming webhook by opening this link](https://api.slack.com/messaging/webhooks) and following the instructions:
-
-1. Click on 'Create your Slack App' button.
-
-![Testomat.io - Notification Slack](./images/Slack_2.png)
-
-2. Select **'From scratch'** option.
-
-![Testomat.io - Notification Slack](./images/Slack_3.png)
-
-3. Add App title.
-4. Pick a workspace to develop your app in from the dropdown list.
-5. Click on 'Create App' button
-
-![Testomat.io - Notification Slack](./images/Slack_4.png)
-
-6. Activate Incoming Webhooks for this app -> toggle on.
-7. Add a new Webhook for app -> Click on **'Add New Webhook'** button
-
-![Testomat.io - Notification Slack](./images/Slack_5.png)
-
-8. Select a channel to which notification will be sent.
-
-![Testomat.io - Notification Slack](./images/Slack_6.png)
-
-9. Copy Webhook URL.
-
-![Testomat.io - Notification Slack](./images/Slack_7.png)
-
-After Slack is Set up, open your Project in Testomat.io and go to the **Settings (1) -> Report Notifications(2)** and click on **Add Notification Rule (3)**.
-
-![Testomat.io - Notification](./images/Notification.png)
-
-Create a new Notification Rule for Slack following next steps:
-
-1. Add a title for Notification Rule.
-2. Choose **Slack** from the dropdown list.
-
-![Testomat.io - Notification Slack](./images/Slack_8.png)
-
-3. Paste Slack Webhook URL.
-4. Select **'Publish a report and use public link in report notification'** option, if you need it.
-5. Configure rules to define on which conditions this notification should be sent in **BASIC RULES** section
-
-OR
-
-use **ADVANCED RULES ENGINE** to enter your rule expression.
-
-6. Click on **Save** button.
-
-| **Basic Rules**             | **Advanced Rules Engine**             |
-| --------------------------- | ------------------------------------- |
-| ![Testomat.io - Basic rule](./images/Slack_9.png) | ![Testomat.io - Advanced Rules Engine](./images/Slack_10.png) |
-
-**How does it work?**
-Each time Testomat.io creates Run Report, which corresponds to your Slack Notification Rule, it will be sent to selected Slack channel.
-
-![Testomat.io - Notification Slack](./images/Slack_11.png)
-
-:::note
-
-When **'Publish a report and use public link in report notification'** option is enabled, the public report will be generated and everyone who has this link will be able to see it.
-
-![Testomat.io - Notification](./images/Public_Report.png)
-
-:::

package/skills/testeiya/testomatio-docs/docs/integrations/report-notifications/telegram.md

@@ -1,73 +0,0 @@
----
-title: Telegram Notifications
-description: Configure Telegram notifications in Testomat.io to receive test updates. This guide provides detailed steps for creating a Telegram bot, generating a Bot Token, retrieving a Chat ID, and linking it with Testomat.io for seamless test result notifications.
-type: article
-url: https://docs.testomat.io/integrations/report-notifications/telegram
-head:
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Telegram integration, Testomat.io, failed test runs, Notification rules, Report Notifications, Add Notification Rule, publish report, public link, basic rules, advanced rules engine, detailed test run results, test management, test automation, software testing
----
-
-Testomat.io provides integration with **Telegram** to deliver real-time notifications about your test results directly into your chat. This integration allows you to keep the entire team updated about failed test runs, published reports, or other key QA events without leaving Telegram.
-
-Before creating a **New Notification Rule** in Testomat.io, you need to have:
-
-- **Telegram bot token** — if you don’t have one yet, follow the official Telegram instructions to [create a new bot](https://core.telegram.org/bots#creating-a-new-bot).
-
-## How to get a Chat/Channel/Group ID
-
-To send notifications from Testomat.io to Telegram, you need a unique identifier (ID) for the destination:
-
-- **Chat ID** is used for sending notifications to a personal/individual chat
-- **Channel/Group ID** is used for sending notifications to a shared channel or group
-
-### Individual Chat Notifications
-
-1. Open a chat with your bot in Telegram
-2. Send any message to the bot
-3. Forward this message to [@username_to_id_bot](https://t.me/username_to_id_bot) to get the **Chat ID**
-4. Paste the returned ID into the **Telegram bot chat/channel/group ID** field in Testomat.io
-
-### Channel/Group Notifications
-
-1. Create a channel (or group) in Telegram
-2. Add your bot as an **administrator**
-3. In the channel/group, send any message
-4. Forward this message to [@username_to_id_bot](https://t.me/username_to_id_bot) to get the **Channel/Group ID**
-5. Paste the returned ID into the **Telegram bot chat/channel/group ID** field in Testomat.io
-
-## How to Create a New Notification Rule for Telegram
-
-1. Navigate to **Settings** in the left sidebar
-2. Open the **Report notifications** page
-3. Click on the **Add Notification Rule** button
-
-![Add Notification Rule](./images/att1_telegram.png)
-
-Once the page opens, fill in the following fields:
-
-4. **Title** — Notification rule name (required)
-5. **Notification Type** — select **Telegram** from the dropdown (required)
-6. **Telegram bot token** (required)
-7. **Telegram bot chat/channel/group ID** (required)
-
-:::note
-
-Add the bot as an **administrator** of the channel/group. Without admin rights, Testomat.io cannot deliver notifications, even with the correct Channel/Group ID.
-
-:::
-
-8. Enable **Publish a report and use public link in report notification** (optional)
-9. Configure Rules: choose [Basic Rules](https://docs.testomat.io/integrations/report-notifications/rules/#basic-rules) or [Advanced Rules Engine](https://docs.testomat.io/integrations/report-notifications/rules/#advanced-rules)
-10. Click **Save** button to create the new Notification Rule
-
-![Save new notification rule](./images/att2_telegram.png)
-
-After saving your rule:
-
-- Use the **Test webhook** button to send a sample notification and confirm that everything is working correctly
-- Run a test in Testomat.io and check that a notification with test results appears in your Telegram chat/channel/group
-
-![Telegram notification](./images/att3_telegram.png)

package/skills/testeiya/testomatio-docs/docs/integrations/scim-provisioning/index.mdx

@@ -1,207 +0,0 @@
----
-title: SCIM provisioning overview
-description: Automate user provisioning and de-provisioning in Testomat.io using SCIM (System for Cross-domain Identity Management) with identity providers like Okta, Microsoft Entra ID, and OneLogin. This guide explains SCIM features, prerequisites, and how to enable SCIM provisioning for your organization.
-type: article
-url: https://docs.testomat.io/integrations/scim-provisioning
-head:
-  - tag: meta
-    attrs:
-      name: og:image
-      content: https://docs.testomat.io/_astro/image-5.BnCL7fbZ_gH0Bt.webp # change_me
-
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Testomat.io, SCIM, System for Cross-domain Identity Management, user provisioning, user management, Okta, Microsoft Entra ID (Azure AD), OneLogin, identity provider, enterprise security, automation
----
-
-Testomat.io supports [SCIM](https://datatracker.ietf.org/doc/html/rfc7642) (System for Cross-domain Identity Management), which allows you to automate your team's provisioning and de-provisioning. You can use Testomat.io at scale across your organization and control access to it with your identity provider.
-
-:::note
-
-SCIM provisioning is only available with a Testomat.io **enterprise** plan.
-
-:::
-
-This guide shows how to set up user management via SCIM provisioning for various identity providers.
-
-## What is SCIM provisioning?
-
-[SCIM](https://datatracker.ietf.org/doc/html/rfc7642) (System for Cross-domain Identity Management) is an open standard that facilitates the automation of user provisioning and de-provisioning between identity providers (IdPs) and service providers. By implementing SCIM, Testomat.io enables seamless integration with various IdPs, allowing for efficient user management.
-
-## SCIM features
-
-Testomat.io's SCIM implementation supports the following provisioning features:
-
-### User provisioning
-
-- **Create User**: Automates the creation of new user accounts in Testomat.io when users are assigned in your identity provider. New users are automatically added to your company and can be assigned to default projects.
-
-:::tip
-
-The newly added user will have the QA role in Testomat.io by default. You can later [update account roles in Testomat.io](https://docs.testomat.io/management/company/users-and-permissions/#_top).
-
-:::
-
-- **Update User Information**:
-  - *Update User Attributes*: Modifies user details such as name and email address.
-  - *Activate User*: Creates and activates a new user account if one does not already exist.
-  - *Deactivate User*: Removes a user from the system and deactivates their account, preventing authentication. This is a soft delete operation that preserves the user record. **Please note:** User accounts and the data corresponding to them won’t be deleted.
-
-  - *Reactivate User*: Reactivates a previously deactivated user account, restoring authentication capabilities.
-
-- **Set User Roles**: Assigns roles to users using the Testomat extension schema. Supported roles include:
-  - `qa` - Quality assurance role (default)
-  - `manager` - Manager role
-  - `billing` - Billing administrator role
-  - `read` - Read-only access status
-
-### Group provisioning
-
-- **Create Group**: Establishes new user groups (teams) within Testomat.io based on group assignments in your identity provider.
-
-- **Delete Group**: Removes user groups from the system.
-
-- **Update Group Information**:
-  - *Update Group Attributes*: Changes group names and other attributes.
-  - *Update Group Members*: Adds or removes users from groups as needed.
-
-## Prerequisites
-
-Before enabling SCIM provisioning, ensure the following:
-
-* You have a company in Testomat.io, and you are [**owner of this company**](https://docs.testomat.io/management/company/users-and-permissions/#roles-within-a-company).
-* Company is on an **Enterprise plan**.
-* You have configured [Single Sign-On (SSO)](https://docs.testomat.io/integrations/single-sign-on/) in Testomat.io. SSO must be configured before you can enable SCIM.
-* Your identity provider supports SCIM 2.0 protocol (e.g., Okta, Microsoft Entra ID, OneLogin).
-* You have administrative privileges in both Testomat.io and your identity provider.
-
-## Enabling SCIM provisioning
-
-You must [configure SSO](https://docs.testomat.io/integrations/single-sign-on/) in Testomat.io before you can enable SCIM for your Testomat.io team.
-
-### Enabling SCIM in Testomat.io
-
-1. Open Testomat.io and navigate to [Companies](https://app.testomat.io/companies) > in the Testomat.io header.
-
-2. Click on the company where you want to enable SCIM provisioning.
-
-3. Click **Authentication** in the right sidebar.
-
-4. Select the **Enable SCIM** toggle to turn it on.
-
-![Testomatio - Enable SCIM](./images/testomat/step_01_enable_scim.png)
-
-### Generating SCIM API credentials
-
-After enabling SCIM provisioning, you need to generate SCIM API credentials:
-
-1. Under **SCIM Provisioning**, choose **Identity Provider** (Okta f.e.) and click on **Generate SCIM token** button to generate SCIM token.
-
-![Testomatio - Enable SCIM](./images/testomat/step_02_choose_provider.png)
-
-2. Copy and securely store the following information:
-   - **SCIM Base URL**: This is your company-specific SCIM endpoint URL (format: `https://app.testomat.io/scim/v2`)
-   - **SCIM Bearer Token**: This token is used for authentication in SCIM API requests
-
-![Testomatio - Enable SCIM](./images/testomat/step_03_generated_token_and_url.png)
-
-:::caution
-
-**Important**: Keep the SCIM Bearer Token secret and secure. You'll need both the Base URL and Bearer Token to configure SCIM in your identity provider. If you need to rotate the token, you can disable SCIM and re-enable it to generate a new token.
-
-:::
-
-### Configuring your identity provider
-
-After generating your SCIM credentials, configure SCIM provisioning in your identity provider:
-
-- [Configure SCIM with Okta](/integrations/scim-provisioning/okta)
-
-## SCIM API endpoints
-
-Testomat.io implements SCIM 2.0 endpoints for user and group management:
-
-### Users endpoints
-
-- `GET /scim/v2/Users` - List users (supports pagination and filtering)
-- `GET /scim/v2/Users/{id}` - Get user details
-- `POST /scim/v2/Users` - Create a new user
-- `PUT /scim/v2/Users/{id}` - Replace user information
-- `PATCH /scim/v2/Users/{id}` - Partially update user information
-- `DELETE /scim/v2/Users/{id}` - Deactivate a user (soft delete)
-
-### Groups endpoints
-
-- `GET /scim/v2/Groups` - List groups
-- `GET /scim/v2/Groups/{id}` - Get group details
-- `POST /scim/v2/Groups` - Create a new group
-- `PUT /scim/v2/Groups/{id}` - Replace group information
-- `PATCH /scim/v2/Groups/{id}` - Partially update group information
-- `DELETE /scim/v2/Groups/{id}` - Delete a group
-
-### Discovery endpoint
-
-- `GET /.well-known/scim-configuration` - Returns ServiceProviderConfig with server capabilities
-
-All SCIM requests use `application/scim+json` content type and require Bearer token authentication in the `Authorization` header.
-
-## Supported attributes
-
-### User attributes
-
-**Core attributes:**
-- `id` - User ID (read-only)
-- `userName` - Maps to user email address
-- `name.formatted` - Full name of the user
-- `active` - Boolean indicating if user is active (false deactivates user and removes access)
-- `emails[0].value` - Primary email address
-- `meta.created` / `meta.lastModified` - Timestamps (read-only)
-
-**Testomat extension schema:**
-- Schema: `urn:ietf:params:scim:schemas:extension:testomat:2.0:User`
-- `testomat_roles` - Multi-valued array of roles: `qa`, `manager`, `billing`, `read`
-
-### Group attributes
-
-- `id` - Group ID (read-only)
-- `displayName` - Group/team name
-- `members[]` - Array of users in the group (contains `value`: user ID, `display`: user name)
-- `meta.created` / `meta.lastModified` - Timestamps (read-only)
-
-## Limitations
-
-While SCIM simplifies user management, be aware of the following limitations:
-
-- **Attribute Mapping**: Not all user attributes may be supported or mapped between Testomat.io and your IdP. Review attribute mappings to ensure accuracy.
-
-- **Group Management**: Group provisioning is supported; however, nested groups or complex group hierarchies may not be fully replicated. Group deletion is currently a destructive operation.
-
-- **Filtering**: Only the `eq` (equals) operator is supported for filtering on `userName` (Users) and `displayName` (Groups). Other filter operators return a 501 Not Implemented error.
-
-- **Real-Time Sync**: There may be a delay between changes in the IdP and their reflection in Testomat.io, depending on synchronization schedules configured in your identity provider.
-
-- **Password Management**: SCIM does not support password synchronization or password updates.
-
-- **Bidirectional Sync**: Testomat.io does not push user or group changes back to the identity provider.
-
-## Troubleshooting
-
-If you encounter issues with SCIM provisioning:
-
-- Verify that SSO is properly configured before enabling SCIM
-- Ensure the SCIM Bearer Token is correctly configured in your identity provider
-- Check that the SCIM Base URL matches the value provided in Company Settings
-- Verify user email addresses match between your IdP and Testomat.io
-- Review synchronization logs in your identity provider for error messages
-
-:::tip
-
-For more information or help with configuring SCIM, [contact Testomat.io support](/support).
-
-:::
-
-import DirectoryLinks from '/src/components/DirectoryLinks.astro';
-import { Steps } from '@astrojs/starlight/components';
-
-<DirectoryLinks directory="integrations/scim-provisioning" />

package/skills/testeiya/testomatio-docs/docs/integrations/scim-provisioning/okta.md

@@ -1,204 +0,0 @@
----
-title: Configure SCIM with Okta
-description: Learn how to configure SCIM (System for Cross-domain Identity Management) provisioning with Okta for Testomat.io. This guide explains setting up SCIM provisioning in Okta, configuring user and group synchronization, and managing automated user lifecycle in Testomat.io.
-type: article
-url: https://docs.testomat.io/integrations/scim-provisioning/okta
-head:
-  - tag: meta
-    attrs:
-      name: og:image
-      content: https://docs.testomat.io/_astro/194427516-2a6336b7-f419-4390-a1a4-30ce528045ba.9RNoCLUD_DRdDW.webp
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Testomat.io, Okta, SCIM, System for Cross-domain Identity Management, user provisioning, user management, identity provider, automation, Okta SCIM
----
-
-This guide walks you through configuring SCIM provisioning with Okta for Testomat.io. With SCIM enabled, Okta will automatically provision and de-provision users and groups in Testomat.io based on assignments in your Okta organization.
-
-## Prerequisites
-
-Before configuring SCIM with Okta, ensure you have:
-
-- A Testomat.io company on an **enterprise plan**
-- [SSO configured](https://docs.testomat.io/integrations/single-sign-on/okta) in Testomat.io with Okta
-- SCIM provisioning enabled in Testomat.io (see [SCIM provisioning overview](/integrations/scim-provisioning))
-- SCIM Base URL and Bearer Token from Testomat.io (available in Company Settings → Domains after enabling SCIM)
-- Administrator access to your Okta organization
-
-## Configure SCIM in Okta
-
-This section shows how to connect Okta to Testomat.io using SCIM 2.0 so that users can be created and updated from Okta.
-
-### Step 1: Create a SCIM 2.0 Test Application
-
-1. Log in to Okta as an Administrator.
-
-2. Navigate to **Applications** > **Applications** in the Okta admin console.
-
-3. Click **Browse App Catalog**.
-
-4. Search for "SCIM 2.0 Test App (OAuth Bearer Token)".
-
-![Testomatio - Okta SCIM Integration](./images/okta/step_01_okta_scim_app_preview_from_search.png)
-
-5. Click **Add Integration** to add the application to your Okta organization.
-
-![Testomatio - Okta SCIM Integration](./images/okta/step_02_okta_scim_app_add_integration.png)
-
-6. Configure the application settings:
-   - **Application label**: Enter "Testomat.io" or a descriptive name
-   - **Application visibility**: Choose whether to show the app icon to users
-   - Click **Next** to proceed to next tab **Sign-In Options**
-
-7. In **Sign-In Options** scroll to the section **Credentials Details** and set **Application username format** to: "Email". Everything else leave as on the screen, after that you can proceed further ans click **Done**.
-
-7. In **Sign-In Options**, scroll to **Credentials Details** and set **Application username format** to **Email**.
-Leave the other settings as shown on the screenshot (password reveal stays disabled because the app uses SAML).
-Click **Done**.
-
-![Testomatio - Okta SCIM Integration](./images/okta/step_04_okta_scim_app_sign_in_options.png)
-
-### Step 2: Configure API Integration Settings
-
-1. In the application configuration page, click the **Provisioning** tab.
-
-![Testomatio - Okta SCIM Integration](./images/okta/step_05_okta_added_scim_app_provisioning.png)
-
-2. Click **Configure API Integration** button.
-
-![Testomatio - Okta SCIM Integration](./images/okta/step_05_okta_added_scim_app_provisioning.png)
-
-3. Click **Enable API Integration** checkbox.
-
-![Testomatio - Okta SCIM Integration](./images/okta/step_06_okta_added_scim_app_enable_api_integration_checkbox.png)
-![Testomatio - Okta SCIM Integration](./images/okta/step_07_okta_added_scim_app_enabled_api_integration_checkbox.png)
-
-4. Configure the SCIM API Integration settings:
-   - **SCIM 2.0 base URL**: Enter the SCIM Base URL from Testomat.io (format: `https://app.testomat.io/scim/v2`)
-   - **OAuth Bearer Token**: Enter the SCIM Bearer Token from Testomat.io
-   - **Import Groups** Leave it as shown on the screenshot (checked)
-5. Click **Test API Credentials** to test the Testomat SCIM credentials entered above.
-
-![Testomatio - Okta SCIM Integration](./images/okta/step_08_okta_added_scim_app_enabled_api_integration_test.png)
-
-6. Click **Save** to save the authentication settings.
-
-### Step 3: Configure Provisioning Options
-
-1. Still in the **Provisioning** tab, click on **Edit** and configure the provisioning options:
-
-   ![Testomatio - Okta SCIM Integration](./images/okta/step_09_okta_added_scim_app_provisioned.png)
-
-   **To App** section:
-   - ✓ Enable **Create Users**
-   - ✓ Enable **Update User Attributes**
-   - ✓ Enable **Deactivate Users**
-   - Optionally enable **Sync Okta Password** (if supported). **Sync Password** settings are left to your own.
-
-   ![Testomatio - Okta SCIM Integration](./images/okta/step_10_okta_added_scim_app_provisioned_enable_all_part_1.png)
-   ![Testomatio - Okta SCIM Integration](./images/okta/step_11_okta_added_scim_app_provisioned_enable_all_part_2.png)
-
-   **To Okta** section (optional):
-   - Enable **Import Users** if you want to import existing Testomat.io users into Okta
-   - Enable **Import New Users** to automatically import new users
-   - Enable **Import Profile Updates** to sync profile changes
-
-2. Click **Save** to save the provisioning options.
-
-### Step 4: Configure Attribute Mappings
-
-1. In the application configuration page, click the **Attribute Mappings** tab.
-
-2. Configure the attribute mappings for users:
-
-   **User attributes:**
-   - `userName` → `user.email` (this maps Okta email to SCIM userName)
-   - `name.formatted` → `user.firstName + " " + user.lastName` or `user.displayName`
-   - `active` → `user.status` (maps Okta user status to SCIM active status)
-   - `emails[0].value` → `user.email`
-
-   **Testomat extension attributes** (if supported in your Okta configuration):
-   - `urn:ietf:params:scim:schemas:extension:testomat:2.0:User.testomat_roles` → Map to Okta group memberships or custom attributes
-     - You can map Okta groups to Testomat roles:
-       - Groups containing "manager" → `["manager"]`
-       - Groups containing "billing" → `["billing"]`
-       - Groups containing "read-only" → `["read"]`
-       - Default → `["qa"]`
-
-3. Click **Save** to save the attribute mappings.
-
-### Step 5: Configure Group Mappings (Optional)
-
-If you want to provision groups (teams) from Okta to Testomat.io:
-
-1. In the application configuration page, click the **Push Groups** tab.
-
-2. Select the Okta groups you want to push to Testomat.io.
-
-3. Configure group attribute mappings:
-   - `displayName` → Group name in Okta
-   - `members` → Automatically mapped from Okta group membership
-
-4. Click **Save** to save the group mappings.
-
-### Step 6: Assign Users and Groups
-
-1. In the application configuration page, click the **Assignments** tab.
-
-2. Click **Assign** to assign users or groups to the application.
-
-3. Select users or groups you want to provision to Testomat.io.
-
-4. Click **Assign** to complete the assignment.
-
-5. Optionally, configure assignment-specific settings:
-   - **User name format**: Choose how usernames are formatted
-   - **Application username**: Override if needed
-
-:::note
-
-Now Okta will start provisioning users and groups to Testomat.io according to your configuration.
-
-:::
-
-## Verify SCIM Provisioning
-
-After activating SCIM provisioning, verify that it's working correctly:
-
-1. **Check user provisioning:**
-   - Assign a new user to the Testomat.io application in Okta
-   - Wait a few minutes for synchronization
-   - Verify the user appears in Testomat.io under Company Settings → Users
-
-2. **Check user updates:**
-   - Update a user's name or email in Okta
-   - Wait for synchronization
-   - Verify the changes are reflected in Testomat.io
-
-3. **Check user deactivation:**
-   - Deactivate a user in Okta or remove them from the application assignment
-   - Wait for synchronization
-   - Verify the user is deactivated in Testomat.io
-
-4. **Check group provisioning** (if enabled):
-   - Create or update a group in Okta that's assigned to the application
-   - Wait for synchronization
-   - Verify the group (team) appears in Testomat.io
-
-## Troubleshooting
-
-If SCIM provisioning is not working correctly:
-
-- **Verify authentication**: Test the API connection in the Provisioning tab
-- **Check Okta logs**: Review the System Log in Okta for SCIM-related errors
-- **Verify SCIM credentials**: Ensure the SCIM Base URL and Bearer Token are correct in Okta
-- **Check attribute mappings**: Verify that attribute mappings are correctly configured
-- **Review synchronization schedule**: Okta may have a delay between changes and synchronization
-- **Verify SSO configuration**: Ensure SSO is properly configured before SCIM provisioning
-
-:::tip
-
-For more information or help with configuring SCIM with Okta, [contact Testomat.io support](/support).
-
-:::

package/skills/testeiya/testomatio-docs/docs/integrations/single-sign-on/azure.md

@@ -1,95 +0,0 @@
----
-title: Microsoft Entra ID (formerly Azure AD)
-description: Learn how to set up Single Sign-On (SSO) for Testomat.io with Microsoft Entra ID (formerly Azure AD) using SAML authentication. This guide explains configuring the Azure portal, mapping user attributes, assigning users, and setting up the SSO connection in Testomat.io to enable secure and seamless user access.
-type: article
-url: https://docs.testomat.io/integrations/single-sign-on/azure
-head:
-  - tag: meta
-    attrs:
-      name: og:image
-      content: https://docs.testomat.io/_astro/image-14.D25uAC23_ZByl9V.webp
-      
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Azure AD, Microsoft Entra ID, Testomat.io, SSO, Single Sign-On, SAML, user authentication, identity provider, attribute mapping, company domain, integration setup, test management, security
----
-
-Open Azure portal and search for Entra ID service:
-
-![EntraID](./images/image-14.png)
-
-Add new Enterprise application
-
-![Alt text](./images/image-16.png)
-
-On the next screen create a new Application
-
-![Create Application](./images/image-15.png)
-
-Enter the "Testomat" as the name of integration, select Integrate any other application you don't find in the gallery (Non-gallery) and click Create. 
-
-Select **Single Sign On** on the left and click "SAML" to configure connection settings.
-
-On the **Basic SAML Configuration** fill in following values
-
-* `Identifier (Entity ID)` → `https://app.testomat.io/users/saml/metadata`
-* `Reply URL (ACS URL)` → `https://app.testomat.io/users/saml/auth`
-* `Sign on URL` → `https://app.testomat.io/users/sso`
-
-
-Save this form. Now edit **Attributes & Claims**.
-
-Remove default attributes.
-
-Add the following attributes that will be sent to Testomat.io:
-
-* `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress` → `email`
-* `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name`         → `name`
-* `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname`    → `first_name`
-* `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname`      → `last_name`
-
-
-Close the dialog. 
-
-On **SAML Signing Certificate** card download **Certificate (Base 64)**.
-
-On **Set up Testomat** card copy following values
-
-* **Login URL** 
-* **Azure ID Idenitifier** 
-
-Add Users to application on the **Users and Groups** section in sidebar. This users will be able to log in to Testomat.io via SAML.
-
-Now, open Company page in [Testomat.io](https://app.testomat.io/companies) and select Single Sign On options
-
-> If you don't see Single Sign On option, check that you are an owner of this company
-
-Fill in the form:
-
-1. **Company domain**. This is required to identify SSO connection by user's email. Example: `mycompany.com`.
-2. **Default Projects**. Select projects to new users will be added to (optional).
-3. Enable SAML:
-
-![Alt text](./images/image-6.png)
-
-4. Set **Azure ID Idenitifier** (or Azure Entra ID) from Microsoft Entra ID (formerly Azure AD) as **IdP Entity ID**. Should be like `https://sts.windows.net/.../` (ensure it ends with `/`)
-5. Set **Login URL** from Microsoft Entra ID as **Sign In URL**
-6. Upload certificate.
-
-![Alt text](./images/image-5.png)
-
-7. Set `Authn Context` by selecting "Password Protected Transport". The actual value should become:
-
-```
-urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport
-```
-
-![alt text](./images/image-17.png)
-
-And save the form.
-
-
-Now, use any assigned user from Microsoft Entra ID (formerly Azure AD) to Log In into Testomat.io. Select "SSO" on the Sign In page, enter the email, and if everything is correct user will get inside Testomat.io, assigned to your company and added to default projects.
-
-> In case user sees 404 page on Microsoft Entra ID (formerly Azure AD), check that Single Sign-On URL was correctly set.