- Back Channel logout
- Front Channel HTTP Redirect @@ -4529,7 +4529,7 @@ components: enableSignatureValidation: type: boolean default: true - description: Specifies whether Asgardeo must validate the signature of the SAML authentication request and the SAML logout request that are sent by the application. + description: Specifies whether WSO2 Identity Platform must validate the signature of the SAML authentication request and the SAML logout request that are sent by the application. signatureValidationCertAlias: type: string description: Specifies the alias of the certificate that will be used to validate the signature of the SAML assertions. @@ -4568,7 +4568,7 @@ components: - 'http://localhost:8080/travelocity_460.com/home.jsp' - 'http://localhost:8080/travelocity_460.com/home1.jsp' minItems: 1 - description: The Assertion Consumer Service (ACS) URL determines where Asgardeo will send the SAML response. + description: The Assertion Consumer Service (ACS) URL determines where WSO2 Identity Platform will send the SAML response. defaultAssertionConsumerUrl: type: string description: If not provided, the first assertion consumer URL on the `assertionConsumerUrls` will be picked as the default assertion consumer URL. @@ -4626,7 +4626,7 @@ components: items: type: string minItems: 1 - description: "The This will determine how the application communicates with the token service. Asgardeo supports following grant types: + description: "The This will determine how the application communicates with the token service. WSO2 Identity Platform supports following grant types:
- authorization_code
- client_credentials @@ -4798,7 +4798,7 @@ components: example: https://wstrust.endpoint.com certificateAlias: type: string - example: "Asgardeo" + example: "WSO2 Identity Platform" CustomInboundProtocolConfiguration: type: object required: diff --git a/en/asgardeo/docs/apis/restapis/approvals.yaml b/en/asgardeo/docs/apis/restapis/approvals.yaml index 7bcc34865d..67f007f3e4 100644 --- a/en/asgardeo/docs/apis/restapis/approvals.yaml +++ b/en/asgardeo/docs/apis/restapis/approvals.yaml @@ -1,8 +1,8 @@ openapi: 3.0.0 info: - title: Asgardeo - Workflow Approval API + title: WSO2 Identity Platform - Workflow Approval API description: | - This is the RESTful API for a user to manage pending approvals in Asgardeo. This API can be used to retrieve pending approvals and update the status of the approval tasks for the authenticated user. + This is the RESTful API for a user to manage pending approvals in WSO2 Identity Platform. This API can be used to retrieve pending approvals and update the status of the approval tasks for the authenticated user. version: v2 servers: - url: 'https://api.asgardeo.io/t/{organization-name}/api/users/v2' diff --git a/en/asgardeo/docs/apis/restapis/association-management-by-admin.yaml b/en/asgardeo/docs/apis/restapis/association-management-by-admin.yaml index c5ad60ccc2..8805fe015e 100644 --- a/en/asgardeo/docs/apis/restapis/association-management-by-admin.yaml +++ b/en/asgardeo/docs/apis/restapis/association-management-by-admin.yaml @@ -2,7 +2,7 @@ openapi: 3.0.1 info: title: User Account Association API description: | - This document specifies a **User Account Association Management RESTful API** for Asgardeo. + This document specifies a **User Account Association Management RESTful API** for WSO2 Identity Platform. The APIs provide the capability for privileged users to retrieve/delete associated local/federated accounts of other users. version: v1 servers: diff --git a/en/asgardeo/docs/apis/restapis/association-management-by-user.yaml b/en/asgardeo/docs/apis/restapis/association-management-by-user.yaml index 5bdb122a89..5a9b51b7c0 100644 --- a/en/asgardeo/docs/apis/restapis/association-management-by-user.yaml +++ b/en/asgardeo/docs/apis/restapis/association-management-by-user.yaml @@ -2,7 +2,7 @@ openapi: 3.0.1 info: title: User Account Associations API description: | - This document specifies a **User Account Association Management RESTful API** for Asgardeo. + This document specifies a **User Account Association Management RESTful API** for WSO2 Identity Platform. The APIs provide the capability to `add`/`retrieve`/`delete` associated local/federated accounts of an authenticated user. version: v1 servers: diff --git a/en/asgardeo/docs/apis/restapis/attribute-management.yaml b/en/asgardeo/docs/apis/restapis/attribute-management.yaml index d0592682e1..5c0eb85ae5 100644 --- a/en/asgardeo/docs/apis/restapis/attribute-management.yaml +++ b/en/asgardeo/docs/apis/restapis/attribute-management.yaml @@ -1,8 +1,8 @@ openapi: 3.0.1 info: - title: Asgardeo Attribute Management API + title: WSO2 Identity Platform Attribute Management API description: This is the RESTful API for attribute (claim) management related operations in - Asgardeo. This API allows adding, retrieving, updating, and deleting + WSO2 Identity Platform. This API allows adding, retrieving, updating, and deleting local/external claims and claim dialects. version: v1 servers: diff --git a/en/asgardeo/docs/apis/restapis/authenticators.yaml b/en/asgardeo/docs/apis/restapis/authenticators.yaml index 601dc6eabe..dea0b6d7ca 100644 --- a/en/asgardeo/docs/apis/restapis/authenticators.yaml +++ b/en/asgardeo/docs/apis/restapis/authenticators.yaml @@ -2,7 +2,7 @@ openapi: 3.0.0 info: version: "v1" title: 'Authenticators API' - description: 'This document specifies a **Authenticators RESTful API** for Asgardeo' + description: 'This document specifies a **Authenticators RESTful API** for WSO2 Identity Platform' servers: - url: 'https://api.asgardeo.io/t/{organization-name}/api/server/v1' diff --git a/en/asgardeo/docs/apis/restapis/backup-code.yaml b/en/asgardeo/docs/apis/restapis/backup-code.yaml index 3367993c32..caca97027c 100644 --- a/en/asgardeo/docs/apis/restapis/backup-code.yaml +++ b/en/asgardeo/docs/apis/restapis/backup-code.yaml @@ -2,9 +2,9 @@ openapi: 3.0.0 info: description: | - This is the RESTful API for a user to manage backup codes in Asgardeo. + This is the RESTful API for a user to manage backup codes in WSO2 Identity Platform. version: "v1" - title: "Asgardeo - Backup Code API Definition" + title: "WSO2 Identity Platform - Backup Code API Definition" servers: - url: https://api.asgardeo.io/t/{organization-name}/api/users/v1 diff --git a/en/asgardeo/docs/apis/restapis/branding-preference.yaml b/en/asgardeo/docs/apis/restapis/branding-preference.yaml index eb53930b86..0e7a738b4e 100644 --- a/en/asgardeo/docs/apis/restapis/branding-preference.yaml +++ b/en/asgardeo/docs/apis/restapis/branding-preference.yaml @@ -1,8 +1,8 @@ openapi: 3.0.0 info: - title: Asgardeo - Branding Preferences API + title: WSO2 Identity Platform - Branding Preferences API description: >- - This is the RESTful API to manage Branding Preferences of root organizations in Asgardeo. + This is the RESTful API to manage Branding Preferences of root organizations in WSO2 Identity Platform. version: v1 servers: - url: 'https://api.asgardeo.io/t/{organization-name}/api/server/v1' diff --git a/en/asgardeo/docs/apis/restapis/consent-management.yaml b/en/asgardeo/docs/apis/restapis/consent-management.yaml index 2e2e5da4bb..05aece8cdf 100644 --- a/en/asgardeo/docs/apis/restapis/consent-management.yaml +++ b/en/asgardeo/docs/apis/restapis/consent-management.yaml @@ -1,8 +1,8 @@ openapi: 3.0.1 info: - title: 'Asgardeo Consent Management Rest API ' + title: 'WSO2 Identity Platform Consent Management Rest API ' description: | - This document specifies a **Consent Management RESTfulAPI** for Asgardeo. + This document specifies a **Consent Management RESTfulAPI** for WSO2 Identity Platform. version: 1.0.0 servers: - url: https://api.asgardeo.io/t/{organization-name}/api/identity/consent-mgt/v1.0 diff --git a/en/asgardeo/docs/apis/restapis/email-template.yaml b/en/asgardeo/docs/apis/restapis/email-template.yaml index 344fe21b78..6ab533be13 100644 --- a/en/asgardeo/docs/apis/restapis/email-template.yaml +++ b/en/asgardeo/docs/apis/restapis/email-template.yaml @@ -1,11 +1,11 @@ openapi: 3.0.0 info: version: "v1" - title: Asgardeo - Email Templates API + title: WSO2 Identity Platform - Email Templates API description: - "This is the RESTful API for managing email templates in WSO2 Asgardeo. This API allows adding, retrieving, replacing, and removing email + "This is the RESTful API for managing email templates in WSO2 WSO2 Identity Platform. This API allows adding, retrieving, replacing, and removing email templates and template types. - \n To access the email template APIs in Asgardeo, you need to first [get an access token](https://wso2.com/asgardeo/docs/apis/authentication/#get-an-access-token) from your organization." + \n To access the email template APIs in WSO2 Identity Platform, you need to first [get an access token](https://wso2.com/asgardeo/docs/apis/authentication/#get-an-access-token) from your organization." tags: - name: Email template types description: An email template type can have multiple email templates for different languages. @@ -108,7 +108,7 @@ paths: "contentType": "text/html", "subject": "WSO2 - Account Confirmation", "body": "HTML Body", - "footer": "WSO2 Asgardeo Team", + "footer": "WSO2 WSO2 Identity Platform Team", "id": "en_US" } ] @@ -238,7 +238,7 @@ paths: "contentType": "text/html", "subject": "WSO2 - Account Confirmation", "body": "HTML Body", - "footer": "WSO2 Asgardeo Team", + "footer": "WSO2 WSO2 Identity Platform Team", "id": "en_US" }' put: @@ -287,7 +287,7 @@ paths: "contentType": "text/html", "subject": "WSO2 - Account Confirmation", "body": "HTML Body", - "footer": "WSO2 Asgardeo Team", + "footer": "WSO2 WSO2 Identity Platform Team", "id": "en_US" } ]' @@ -419,7 +419,7 @@ paths: "contentType": "text/html", "subject": "WSO2 - Account Confirmation", "body": "HTML Body", - "footer": "WSO2 Asgardeo Team", + "footer": "WSO2 WSO2 Identity Platform Team", "id": "en_US" }' delete: @@ -643,7 +643,7 @@ components: description: The body (HTML) of the email. footer: type: string - example: WSO2 Asgardeo Team + example: WSO2 WSO2 Identity Platform Team description: The footer of the email. EmailTemplateWithID: allOf: diff --git a/en/asgardeo/docs/apis/restapis/event-configuration.yaml b/en/asgardeo/docs/apis/restapis/event-configuration.yaml index e0d10781ef..04587c5438 100644 --- a/en/asgardeo/docs/apis/restapis/event-configuration.yaml +++ b/en/asgardeo/docs/apis/restapis/event-configuration.yaml @@ -1,8 +1,8 @@ openapi: 3.0.0 info: version: "v1" - title: Asgardeo - Event Configuration Management API - description: "This document specifies a RESTful API for managing event publisher configurations in Asgardeo." + title: WSO2 Identity Platform - Event Configuration Management API + description: "This document specifies a RESTful API for managing event publisher configurations in WSO2 Identity Platform." servers: - url: 'https://api.asgardeo.io/t/{organization-name}/api/event-configurations/v1' security: @@ -14,7 +14,7 @@ paths: - Events Configurations summary: Retrieve all events. description: | - This API provides capability to retrieve all events of the Asgardeo event publisher.
- Session identifier as a request parameter: This method is ideal in cases where third-party cookies have been blocked. This can be obtained from the ID token. @@ -15,7 +15,7 @@ paths: /identity/extend-session: get: summary: Extend user sessions - description: "This API is used to extend the Asgardeo session of a user. To identify the session that needs to be extended, this API requires one of the following: \n + description: "This API is used to extend the WSO2 Identity Platform session of a user. To identify the session that needs to be extended, this API requires one of the following: \n
- Session identifier as a request parameter: If you are using this method, you need to include the session identifier as a query parameter in the request. You can obtain the session identifier from the ID token.
- Session identifier as a cookie: If you are using this method, you need to include the session identifier as a cookie. This is the commonAuthId cookie. diff --git a/en/asgardeo/docs/apis/restapis/identity-governance.yaml b/en/asgardeo/docs/apis/restapis/identity-governance.yaml index 3383d5edb4..9d25e8f339 100644 --- a/en/asgardeo/docs/apis/restapis/identity-governance.yaml +++ b/en/asgardeo/docs/apis/restapis/identity-governance.yaml @@ -1,9 +1,9 @@ openapi: 3.0.0 info: description: >- - This is the RESTful API for identity governance configurations in Asgardeo. + This is the RESTful API for identity governance configurations in WSO2 Identity Platform. version: "v1" - title: Asgardeo - Governance Connectors Admin API + title: WSO2 Identity Platform - Governance Connectors Admin API tags: - name: Management description: Secured Admin-only calls diff --git a/en/asgardeo/docs/apis/restapis/identity-verification-providers.yaml b/en/asgardeo/docs/apis/restapis/identity-verification-providers.yaml index feb8409858..10c22b2af4 100644 --- a/en/asgardeo/docs/apis/restapis/identity-verification-providers.yaml +++ b/en/asgardeo/docs/apis/restapis/identity-verification-providers.yaml @@ -2,7 +2,7 @@ openapi: 3.0.3 info: title: Identity Verification Provider Management API description: |- - This document specifies an **Identity Verification Provider Management RESTful API** for **Asgardeo**. The APIs provide the capability to add/update/delete/update identity verification providers. + This document specifies an **Identity Verification Provider Management RESTful API** for **WSO2 Identity Platform**. The APIs provide the capability to add/update/delete/update identity verification providers. version: "v1" servers: - url: 'https://api.asgardeo.io/t/{organization-name}/api/server/v1' diff --git a/en/asgardeo/docs/apis/restapis/idle-account-identification.yaml b/en/asgardeo/docs/apis/restapis/idle-account-identification.yaml index c9ef159bbb..46d2597c96 100644 --- a/en/asgardeo/docs/apis/restapis/idle-account-identification.yaml +++ b/en/asgardeo/docs/apis/restapis/idle-account-identification.yaml @@ -1,9 +1,9 @@ openapi: 3.0.0 info: description: > - This document specifies a RESTful API for identifying idle business user accounts in Asgardeo. The API provides the capability to retrieve a list of inactive users after a specified date. + This document specifies a RESTful API for identifying idle business user accounts in WSO2 Identity Platform. The API provides the capability to retrieve a list of inactive users after a specified date. version: "v1" - title: Asgardeo - Idle Account Identification Rest API + title: WSO2 Identity Platform - Idle Account Identification Rest API security: - OAuth2: [] servers: diff --git a/en/asgardeo/docs/apis/restapis/idp.yaml b/en/asgardeo/docs/apis/restapis/idp.yaml index 4149d8a53a..c3b8d6aa8c 100644 --- a/en/asgardeo/docs/apis/restapis/idp.yaml +++ b/en/asgardeo/docs/apis/restapis/idp.yaml @@ -1,9 +1,9 @@ openapi: 3.0.0 info: description: > - This document specifies a RESTful API for managing identity providers in Asgardeo. The APIs provide the capability to `add`, `update`, `delete`, and `patch` identity providers. + This document specifies a RESTful API for managing identity providers in WSO2 Identity Platform. The APIs provide the capability to `add`, `update`, `delete`, and `patch` identity providers. version: "v1" - title: Asgardeo - Identity Provider Management API definition + title: WSO2 Identity Platform - Identity Provider Management API definition security: - OAuth2: [] servers: @@ -257,7 +257,7 @@ paths: - Metadata summary: | List supported federated authenticators of IdPs - description: "This API provides the list of supported federated authenticators for an identity provider in Asgardeo. \n\nScope(Permission) required:
OVERRIDE_ALL: All attributes of the local user account will be overridden by the attributes received from the external identity provider.NONE: None of the attributes received from the identity provider will be synced with the local user account.
diff --git a/en/asgardeo/docs/apis/restapis/notification-senders-v2.yaml b/en/asgardeo/docs/apis/restapis/notification-senders-v2.yaml
index 64e20cdf53..e175cecfcb 100644
--- a/en/asgardeo/docs/apis/restapis/notification-senders-v2.yaml
+++ b/en/asgardeo/docs/apis/restapis/notification-senders-v2.yaml
@@ -1,7 +1,7 @@
openapi: 3.0.0
info:
title: Notification Senders v2 API
- description: This document specifies **Email, SMS and Push notification sender RESTful API** for **Asgardeo**
+ description: This document specifies **Email, SMS and Push notification sender RESTful API** for **WSO2 Identity Platform**
version: "v2"
servers:
- url: 'https://api.asgardeo.io/t/{organization-name}/api/server/v2'
diff --git a/en/asgardeo/docs/apis/restapis/notification-senders.yaml b/en/asgardeo/docs/apis/restapis/notification-senders.yaml
index 456a7d793c..15801ee3b1 100644
--- a/en/asgardeo/docs/apis/restapis/notification-senders.yaml
+++ b/en/asgardeo/docs/apis/restapis/notification-senders.yaml
@@ -1,7 +1,7 @@
openapi: 3.0.0
info:
title: Notification Senders API
- description: This document specifies **Email, SMS and Push notification sender RESTful API** for **Asgardeo**
+ description: This document specifies **Email, SMS and Push notification sender RESTful API** for **WSO2 Identity Platform**
version: "v1"
servers:
- url: https://{serverUrl}/t/{tenantDomain}/api/server/v1
diff --git a/en/asgardeo/docs/apis/restapis/notification-templates.yml b/en/asgardeo/docs/apis/restapis/notification-templates.yml
index 4b5f670172..710c67c12a 100644
--- a/en/asgardeo/docs/apis/restapis/notification-templates.yml
+++ b/en/asgardeo/docs/apis/restapis/notification-templates.yml
@@ -1,6 +1,6 @@
openapi: 3.0.0
info:
- title: "Asgardeo - Notification Templates API"
+ title: "WSO2 Identity Platform - Notification Templates API"
version: 1.0.0
description: >-
This is the RESTful API for managing notification templates in the WSO2 Identity
diff --git a/en/asgardeo/docs/apis/restapis/oauth-dcr.yaml b/en/asgardeo/docs/apis/restapis/oauth-dcr.yaml
index 86d1082cd7..c644d95d11 100644
--- a/en/asgardeo/docs/apis/restapis/oauth-dcr.yaml
+++ b/en/asgardeo/docs/apis/restapis/oauth-dcr.yaml
@@ -1,8 +1,8 @@
openapi: 3.0.1
info:
- title: Asgardeo - OAuth2 Dynamic Client Registration API
+ title: WSO2 Identity Platform - OAuth2 Dynamic Client Registration API
description: |
- This document specifies an OAuth2 Dynamic Client Registration endpoint for Asgardeo.
+ This document specifies an OAuth2 Dynamic Client Registration endpoint for WSO2 Identity Platform.
- authorization_code
- client_credentials @@ -381,7 +381,7 @@ components: - password items: type: string - description: "The This will determine how the application communicates with the token service. Asgardeo supports following grant types: + description: "The This will determine how the application communicates with the token service. WSO2 Identity Platform supports following grant types:
- authorization_code
- client_credentials @@ -419,7 +419,7 @@ components: - password items: type: string - description: "The This will determine how the application communicates with the token service. Asgardeo supports following grant types: + description: "The This will determine how the application communicates with the token service. WSO2 Identity Platform supports following grant types:
- authorization_code
- client_credentials diff --git a/en/asgardeo/docs/apis/restapis/offline-user-onboard.yaml b/en/asgardeo/docs/apis/restapis/offline-user-onboard.yaml index 8b54f14ba6..60af37d9b9 100644 --- a/en/asgardeo/docs/apis/restapis/offline-user-onboard.yaml +++ b/en/asgardeo/docs/apis/restapis/offline-user-onboard.yaml @@ -4,7 +4,7 @@ info: title: Offline User Onboard Management API description: >- This document specifies an **Offline user onboard management RESTFull API** for - Asgardeo. + WSO2 Identity Platform. paths: '/offline-invite-link': diff --git a/en/asgardeo/docs/apis/restapis/org-management.yaml b/en/asgardeo/docs/apis/restapis/org-management.yaml index 26d5f1bd1b..55c5cb738e 100644 --- a/en/asgardeo/docs/apis/restapis/org-management.yaml +++ b/en/asgardeo/docs/apis/restapis/org-management.yaml @@ -1,9 +1,9 @@ openapi: 3.0.0 info: version: "v1" - title: 'Asgardeo - Organization Management API Definition' + title: 'WSO2 Identity Platform - Organization Management API Definition' description: | - 'This is the RESTful API for organization management in Asgardeo. + 'This is the RESTful API for organization management in WSO2 Identity Platform. This API allows users to create, update, retrieve and delete organizations. Other than that the API supports to share the application from the root organization to given organization, get the list of organizations that the application is shared to and delete the shared application from the organizations.' diff --git a/en/asgardeo/docs/apis/restapis/organization-discovery-config-mgt.yaml b/en/asgardeo/docs/apis/restapis/organization-discovery-config-mgt.yaml index 0e756d78a4..f5da647020 100644 --- a/en/asgardeo/docs/apis/restapis/organization-discovery-config-mgt.yaml +++ b/en/asgardeo/docs/apis/restapis/organization-discovery-config-mgt.yaml @@ -1,7 +1,7 @@ openapi: 3.0.0 info: - title: Asgardeo - Organization Discovery Configuration Management API Definition - description: This document specifies a **RESTful API** for Organization Discovery Configuration Management in Asgardeo. + title: WSO2 Identity Platform - Organization Discovery Configuration Management API Definition + description: This document specifies a **RESTful API** for Organization Discovery Configuration Management in WSO2 Identity Platform. version: "v1" servers: - url: 'https://api.asgardeo.io/t/{organization-name}/api/server/v1' diff --git a/en/asgardeo/docs/apis/restapis/organization-discovery.yaml b/en/asgardeo/docs/apis/restapis/organization-discovery.yaml index 22323842b4..f12c2b1b90 100644 --- a/en/asgardeo/docs/apis/restapis/organization-discovery.yaml +++ b/en/asgardeo/docs/apis/restapis/organization-discovery.yaml @@ -3,7 +3,7 @@ info: version: "v1" title: 'Organization Discovery API' description: | - This document specifies an **Organization Discovery RESTful API** for Asgardeo. + This document specifies an **Organization Discovery RESTful API** for WSO2 Identity Platform. servers: - url: 'https://api.asgardeo.io/t/{organization-name}/api/server/v1' diff --git a/en/asgardeo/docs/apis/restapis/organization-user-share-v2.yaml b/en/asgardeo/docs/apis/restapis/organization-user-share-v2.yaml index 88edb4f6c0..e065385f3e 100644 --- a/en/asgardeo/docs/apis/restapis/organization-user-share-v2.yaml +++ b/en/asgardeo/docs/apis/restapis/organization-user-share-v2.yaml @@ -3,7 +3,7 @@ info: version: 1.0.0 title: "User Sharing API (v2)" description: |- - This document defines the **User Sharing REST API (v2)** for organizations in **Asgardeo**. + This document defines the **User Sharing REST API (v2)** for organizations in **WSO2 Identity Platform**. It enables organization administrators to: - Share users across child organizations. - Configure per-organization user role assignments. diff --git a/en/asgardeo/docs/apis/restapis/organization-user-share.yaml b/en/asgardeo/docs/apis/restapis/organization-user-share.yaml index e563bbd821..09285a5aa8 100644 --- a/en/asgardeo/docs/apis/restapis/organization-user-share.yaml +++ b/en/asgardeo/docs/apis/restapis/organization-user-share.yaml @@ -3,7 +3,7 @@ info: version: "v1" title: 'User Sharing API (deprecated)' description: |- - This document defines the **User Sharing REST API for organizations** in **Asgardeo**. This enables organization administrators to share users across child organizations, manage and revoke shared access, and retrieve users' shared organizations and roles. + This document defines the **User Sharing REST API for organizations** in **WSO2 Identity Platform**. This enables organization administrators to share users across child organizations, manage and revoke shared access, and retrieve users' shared organizations and roles. **Shared scopes with User Sharing API v2:** The OAuth2 scopes `internal_user_share`, `internal_user_unshare`, and `internal_user_shared_access_view` are shared between this API (v1) and the User Sharing v2 API. Authorizing either API automatically grants access to the equivalent endpoints in the other that use the same scopes. diff --git a/en/asgardeo/docs/apis/restapis/password-recovery.yaml b/en/asgardeo/docs/apis/restapis/password-recovery.yaml index 2632889543..d657037189 100644 --- a/en/asgardeo/docs/apis/restapis/password-recovery.yaml +++ b/en/asgardeo/docs/apis/restapis/password-recovery.yaml @@ -1,10 +1,10 @@ openapi: 3.0.0 info: version: "v1-oas3" - title: Asgardeo - Password Recovery API + title: WSO2 Identity Platform - Password Recovery API description: | This is the RESTful API for password recovery initiated by the user. -
- API Resource:
/api/users/v1/me/change-password - Authorization Policy: Set to
No Authorization Policy
diff --git a/en/asgardeo/docs/apis/restapis/user-store.yaml b/en/asgardeo/docs/apis/restapis/user-store.yaml
index 6cdcb9db5f..f76a88f3d6 100644
--- a/en/asgardeo/docs/apis/restapis/user-store.yaml
+++ b/en/asgardeo/docs/apis/restapis/user-store.yaml
@@ -1,7 +1,7 @@
openapi: 3.0.0
info:
description: >
- This document specifies the **Userstore Management RESTful API** for Asgardeo.
+ This document specifies the **Userstore Management RESTful API** for WSO2 Identity Platform.
version: "v1"
title: UserStore Management Rest API
diff --git a/en/asgardeo/docs/apis/restapis/validation.yaml b/en/asgardeo/docs/apis/restapis/validation.yaml
index 68c916364d..f6a8deed4d 100644
--- a/en/asgardeo/docs/apis/restapis/validation.yaml
+++ b/en/asgardeo/docs/apis/restapis/validation.yaml
@@ -1,9 +1,9 @@
openapi: 3.0.0
info:
version: "v1"
- title: Asgardeo - Validation API
+ title: WSO2 Identity Platform - Validation API
description:
- "This is the RESTful API for managing input validation configuration for an organization in WSO2 Asgardeo.
+ "This is the RESTful API for managing input validation configuration for an organization in WSO2 WSO2 Identity Platform.
This API allows retrieving and updating the input validation configurations."
servers:
- url: 'https://api.asgardeo.io/t/{organization-name}/api/server/v1'
diff --git a/en/asgardeo/docs/apis/restapis/vc-templates.yaml b/en/asgardeo/docs/apis/restapis/vc-templates.yaml
index 0a761ddc14..525b3d0de9 100644
--- a/en/asgardeo/docs/apis/restapis/vc-templates.yaml
+++ b/en/asgardeo/docs/apis/restapis/vc-templates.yaml
@@ -1,8 +1,8 @@
openapi: 3.0.0
info:
- title: "Asgardeo Verifiable Credential Template Management API"
+ title: "WSO2 Identity Platform Verifiable Credential Template Management API"
version: "v1"
- description: "Admin API for managing verifiable credential templates in Asgardeo."
+ description: "Admin API for managing verifiable credential templates in WSO2 Identity Platform."
contact:
name: WSO2
url: 'https://wso2.com/asgardeo/'
diff --git a/en/asgardeo/docs/apis/restapis/webhook-management.yaml b/en/asgardeo/docs/apis/restapis/webhook-management.yaml
index f25570d5f4..c7fa0265ab 100644
--- a/en/asgardeo/docs/apis/restapis/webhook-management.yaml
+++ b/en/asgardeo/docs/apis/restapis/webhook-management.yaml
@@ -1,9 +1,9 @@
openapi: 3.0.0
info:
version: v1
- title: Asgardeo - Webhook Management Rest API
+ title: WSO2 Identity Platform - Webhook Management Rest API
description: >
- The Webhook Management REST API provides a standardized interface to manage webhooks within Asgardeo. Webhooks allow external systems to receive real-time notifications for various events, such as login successes or failures, enabling seamless integration and automation across external applications and services.
+ The Webhook Management REST API provides a standardized interface to manage webhooks within WSO2 Identity Platform. Webhooks allow external systems to receive real-time notifications for various events, such as login successes or failures, enabling seamless integration and automation across external applications and services.
This API empowers developers and administrators to create, update, delete, and retrieve webhook configurations tailored to their specific business needs and event-driven workflows.
servers:
- url: 'https://api.asgardeo.io/t/{organization-name}/api/server/v1'
diff --git a/en/asgardeo/docs/apis/restapis/webhook-metadata.yaml b/en/asgardeo/docs/apis/restapis/webhook-metadata.yaml
index e9776721fc..3b8885670a 100644
--- a/en/asgardeo/docs/apis/restapis/webhook-metadata.yaml
+++ b/en/asgardeo/docs/apis/restapis/webhook-metadata.yaml
@@ -1,10 +1,10 @@
openapi: 3.0.0
info:
version: v1
- title: Asgardeo - Webhook Metadata Rest API
+ title: WSO2 Identity Platform - Webhook Metadata Rest API
description: >
The Webhook Metadata REST API provides a standardized interface to retrieve
- supported event profiles and the associated events within Asgardeo. This API
+ supported event profiles and the associated events within WSO2 Identity Platform. This API
enables clients to dynamically fetch available events for webhook subscription based on the
selected event profile, improving flexibility and profile-awareness in integrations.
servers:
@@ -16,7 +16,7 @@ paths:
/webhooks/metadata:
get:
summary: List Event Profiles
- description: "This API returns the list of event profiles supported by Asgardeo.\n\n Scope(Permission) required: `internal_webhook_meta_view` \n\n"
+ description: "This API returns the list of event profiles supported by WSO2 Identity Platform.\n\n Scope(Permission) required: `internal_webhook_meta_view` \n\n"
operationId: getEventProfiles
tags:
- Webhook Metadata
diff --git a/en/asgardeo/docs/apis/restapis/workflow.yaml b/en/asgardeo/docs/apis/restapis/workflow.yaml
index 3d9ee3332c..25cb1fa7f0 100644
--- a/en/asgardeo/docs/apis/restapis/workflow.yaml
+++ b/en/asgardeo/docs/apis/restapis/workflow.yaml
@@ -1,9 +1,9 @@
openapi: 3.0.0
info:
description: >
- This is the RESTful API for managing workflows in Asgardeo.
+ This is the RESTful API for managing workflows in WSO2 Identity Platform.
version: v1
- title: Asgardeo - Workflow Management Rest API
+ title: WSO2 Identity Platform - Workflow Management Rest API
servers:
- url: 'https://api.asgardeo.io/t/{organization-name}/api/server/v1'
security:
diff --git a/en/asgardeo/docs/complete-guides/angular/install-asgardeo-sdk.md b/en/asgardeo/docs/complete-guides/angular/install-asgardeo-sdk.md
index 64fea50587..03055bf9b6 100644
--- a/en/asgardeo/docs/complete-guides/angular/install-asgardeo-sdk.md
+++ b/en/asgardeo/docs/complete-guides/angular/install-asgardeo-sdk.md
@@ -1,6 +1,6 @@
---
template: templates/complete-guide.html
-heading: Install and configure Asgardeo SDK
+heading: Install and configure WSO2 Identity Platform SDK
read_time: 2 min
---
diff --git a/en/asgardeo/docs/complete-guides/angular/prerequisite.md b/en/asgardeo/docs/complete-guides/angular/prerequisite.md
index 57732d4135..2d7f750fde 100644
--- a/en/asgardeo/docs/complete-guides/angular/prerequisite.md
+++ b/en/asgardeo/docs/complete-guides/angular/prerequisite.md
@@ -7,7 +7,7 @@ read_time: 30 secs
## Before you start, ensure you have the following
* About 60 minutes
-* Asgardeo [account](https://wso2.com/asgardeo/docs/get-started/create-asgardeo-account/){:target="_blank"}
+* WSO2 Identity Platform [account](https://wso2.com/asgardeo/docs/get-started/create-asgardeo-account/){:target="_blank"}
* [Node.js](https://nodejs.org/en/download/package-manager){:target="_blank"} v18+ and npm
* Install [Angular CLI](https://nodejs.org/en/download/package-manager){:target="_blank"}
* A favorite text editor or IDE
diff --git a/en/asgardeo/docs/complete-guides/angular/register-an-application.md b/en/asgardeo/docs/complete-guides/angular/register-an-application.md
index d60fae5a59..05e9a1a71e 100644
--- a/en/asgardeo/docs/complete-guides/angular/register-an-application.md
+++ b/en/asgardeo/docs/complete-guides/angular/register-an-application.md
@@ -1,11 +1,11 @@
---
template: templates/complete-guide.html
-heading: Register an application in Asgardeo
+heading: Register an application in WSO2 Identity Platform
read_time: 2 min
---
First unless you already have done that, you need to create an organization in {{product_name}} and register your application as a single page application.
-* Sign up for a [free Asgardeo account](https://wso2.com/asgardeo/docs/get-started/create-asgardeo-account/){:target="_blank"}
+* Sign up for a [free WSO2 Identity Platform account](https://wso2.com/asgardeo/docs/get-started/create-asgardeo-account/){:target="_blank"}
{% include "../../../../includes/complete-guides/angular/register-an-application.md" %}
diff --git a/en/asgardeo/docs/complete-guides/app-native/prerequisites.md b/en/asgardeo/docs/complete-guides/app-native/prerequisites.md
index 8ff143764b..5003cc57ca 100644
--- a/en/asgardeo/docs/complete-guides/app-native/prerequisites.md
+++ b/en/asgardeo/docs/complete-guides/app-native/prerequisites.md
@@ -8,7 +8,7 @@ read_time: 30 secs
* About 60 minutes
* {{product_name}} account
-* Create [a test user in Asgardeo](https://wso2.com/asgardeo/docs/guides/users/manage-users/#onboard-users)
+* Create [a test user in WSO2 Identity Platform](https://wso2.com/asgardeo/docs/guides/users/manage-users/#onboard-users)
* [Node.js](https://nodejs.org/en/download/package-manager){:target="_blank"} v20+ and npm
* Access to the [Google Developer Console](https://console.developers.google.com/apis/credentials)
* A favorite text editor or IDE
diff --git a/en/asgardeo/docs/complete-guides/app-native/register-an-application.md b/en/asgardeo/docs/complete-guides/app-native/register-an-application.md
index bec9b09cf7..e01e2640d5 100644
--- a/en/asgardeo/docs/complete-guides/app-native/register-an-application.md
+++ b/en/asgardeo/docs/complete-guides/app-native/register-an-application.md
@@ -25,7 +25,7 @@ Next, complete the wizard popup by providing a suitable name and an authorized r
The authorized redirect URL determines where {{product_name}} should send users after they successfully log in. Typically, this will be the web address where your application is hosted. For this guide, we'll use http://localhost:3000, as the sample application will be accessible at this URL
-Make a note of the following values from the **Guide** tab of the registered application. You will need them to configure the Asgardeo provider.
+Make a note of the following values from the **Guide** tab of the registered application. You will need them to configure the WSO2 Identity Platform provider.
```bash
NEXT_PUBLIC_ASGARDEO_BASE_URL="https://api.asgardeo.io/t/ - Onboard users
- Create organizations @@ -70,8 +70,8 @@ The source of the user account determines which entity manages the user's creden
- Onboard users diff --git a/en/asgardeo/docs/guides/users/manage-administrators.md b/en/asgardeo/docs/guides/users/manage-administrators.md index 1508879db2..7fc5419eef 100644 --- a/en/asgardeo/docs/guides/users/manage-administrators.md +++ b/en/asgardeo/docs/guides/users/manage-administrators.md @@ -3,7 +3,7 @@ This guide walks you through the steps of managing an administrator account. If you are the owner or an existing administrator in the organization, you can onboard new administrators or delete existing administrator accounts. !!! note - You cannot manage the user profiles of other administrators or update their passwords from the Asgardeo Console. Administrators must manage their own profiles and passwords using the [My Account portal]({{base_path}}/guides/your-asgardeo/asgardeo-self-service/). + You cannot manage the user profiles of other administrators or update their passwords from the WSO2 Identity Platform Console. Administrators must manage their own profiles and passwords using the [My Account portal]({{base_path}}/guides/your-asgardeo/asgardeo-self-service/). ## Onboard an administrator @@ -16,12 +16,12 @@ There are two ways to onboard an administrator: Existing administrators can onboard other administrators by sending them email invitations to join the organization. To do so, -1. On the Asgardeo Console, go to **Console Settings** > **Administrators**. +1. On the WSO2 Identity Platform Console, go to **Console Settings** > **Administrators**. 2. Click **Add Administrator** and provide the following details. !!! note - If you have enabled the option to [assign admin privileges to users](#assign-admin-privileges-to-users), you may proceed to invite external admins by clicking *Add Administrator* > *Invite Admins to Asgardeo*. + If you have enabled the option to [assign admin privileges to users](#assign-admin-privileges-to-users), you may proceed to invite external admins by clicking *Add Administrator* > *Invite Admins to WSO2 Identity Platform*. {% if default_roles %} @@ -32,7 +32,7 @@ Existing administrators can onboard other administrators by sending them email i
+ This API provides capability to retrieve all events of the WSO2 Identity Platform event publisher.
Permissions required:
* /permission/admin/manage/identity/eventconfig/view @@ -51,7 +51,7 @@ paths: - Events Configurations summary: Update multiple events. description: | - This API provides the capability to enable/ disable multiple events for the Asgardeo event publisher.
+ This API provides the capability to enable/ disable multiple events for the WSO2 Identity Platform event publisher.
You need to send the complete list of events in order for it to be accepted as a valid request.
Permissions required:
@@ -108,7 +108,7 @@ paths: - Event Configurations summary: Retrieve event publishing configuration by event name. description: | - This API provides the capability to retrieve Asgardeo event publisher configuration by event name.
+ This API provides the capability to retrieve WSO2 Identity Platform event publisher configuration by event name.
Permissions required:
* /permission/admin/manage/identity/eventconfig/view @@ -153,7 +153,7 @@ paths: - Event Configurations summary: Configure event publishing configuration by event name. description: | - This API provides the capability to configure Asgardeo event publisher configuration by event name.
+ This API provides the capability to configure WSO2 Identity Platform event publisher configuration by event name.
Permissions required:
* /permission/admin/manage/identity/eventconfig/update diff --git a/en/asgardeo/docs/apis/restapis/export-user-info.yaml b/en/asgardeo/docs/apis/restapis/export-user-info.yaml index 1ae0ce97f7..d586dce407 100644 --- a/en/asgardeo/docs/apis/restapis/export-user-info.yaml +++ b/en/asgardeo/docs/apis/restapis/export-user-info.yaml @@ -2,9 +2,9 @@ openapi: 3.0.0 info: description: | - This is the RESTful API for users to export their profile information stored in Asgardeo. + This is the RESTful API for users to export their profile information stored in WSO2 Identity Platform. version: "v1" - title: "Asgardeo - Export user profile information API" + title: "WSO2 Identity Platform - Export user profile information API" servers: - url: https://api.asgardeo.io/t/{organization-name}/api/identity/user/v1.0 diff --git a/en/asgardeo/docs/apis/restapis/extend-sessions.yaml b/en/asgardeo/docs/apis/restapis/extend-sessions.yaml index b7d7ee18f9..a6cf461927 100644 --- a/en/asgardeo/docs/apis/restapis/extend-sessions.yaml +++ b/en/asgardeo/docs/apis/restapis/extend-sessions.yaml @@ -1,9 +1,9 @@ openapi: 3.0.0 info: version: 1.0.0 - title: Asgardeo - User session extension API + title: WSO2 Identity Platform - User session extension API description: - "You can use this API to extend the user's session at Asgardeo. \n + "You can use this API to extend the user's session at WSO2 Identity Platform. \n To identify the session that needs to be extended, this API requires one of the following: \n
`internal_idp_view`" + description: "This API provides the list of supported federated authenticators for an identity provider in WSO2 Identity Platform. \n\nScope(Permission) required:
`internal_idp_view`" operationId: getMetaFederatedAuthenticators responses: '200': @@ -303,7 +303,7 @@ paths: - Metadata summary: | Get metadata of a supported federated authenticator - description: "This API provides the details of a single supported federated authenticator for an identity provider in Asgardeo. \n\nScope(Permission) required: `internal_idp_view`" + description: "This API provides the details of a single supported federated authenticator for an identity provider in WSO2 Identity Platform. \n\nScope(Permission) required: `internal_idp_view`" operationId: getMetaFederatedAuthenticator parameters: - name: federated-authenticator-id @@ -354,7 +354,7 @@ paths: - Metadata summary: > List supported outbound provisioning connectors of IdPs - description: "This API provides the list of supported federated authenticators for an identity provider (IdP) in the Asgardeo. \n\n Scope(Permission) required: `internal_idp_view`" + description: "This API provides the list of supported federated authenticators for an identity provider (IdP) in the WSO2 Identity Platform. \n\n Scope(Permission) required: `internal_idp_view`" operationId: getMetaOutboundConnectors responses: '200': @@ -400,7 +400,7 @@ paths: - Metadata summary: | Get metadata of a supported outbound provisioning connector - description: "This API provides the details of a single supported outbound provisioning connector for an identity provider (IdP) in the Asgardeo. \n\n Scope(Permission) required: `internal_idp_view`" + description: "This API provides the details of a single supported outbound provisioning connector for an identity provider (IdP) in the WSO2 Identity Platform. \n\n Scope(Permission) required: `internal_idp_view`" operationId: getMetaOutboundConnector parameters: - name: outbound-provisioning-connector-id @@ -2355,7 +2355,7 @@ components: example: "https://api.asgardeo.io/t/{org-name}/oauth2/jwks" samlMetadataUri: type: string - description: The SAML metadata endpoint URL of the external identity provider. When configured, Asgardeo fetches and caches the signing certificate from this URL to validate SAML response signatures and IdP-initiated logout request signatures. + description: The SAML metadata endpoint URL of the external identity provider. When configured, WSO2 Identity Platform fetches and caches the signing certificate from this URL to validate SAML response signatures and IdP-initiated logout request signatures. example: "https://idp.example.com/saml/metadata" IdentityProviderPOSTRequest: type: object @@ -3039,7 +3039,7 @@ components: example: http://wso2.org/claims/email attributeSyncMethod: description: "This variable specifies the method used for syncing attributes between the JIT-provisioned user account and the local user account. \n\n - Asgardeo allows the following syncing methods: \n\n + WSO2 Identity Platform allows the following syncing methods: \n\n
⚠️ NOTE
@@ -309,7 +309,7 @@ components:
type: array
items:
type: string
- description: The redirect URI determines where Asgardeo will redirect users after authentication and logout.
+ description: The redirect URI determines where WSO2 Identity Platform will redirect users after authentication and logout.
client_name:
type: string
description: The name of the OAuth2 client application.
@@ -326,7 +326,7 @@ components:
- password
items:
type: string
- description: "The This will determine how the application communicates with the token service. Asgardeo supports following grant types:
+ description: "The This will determine how the application communicates with the token service. WSO2 Identity Platform supports following grant types:
To access this API in Asgardeo, you need to first [get an access token](https://wso2.com/asgardeo/docs/apis/authentication/#get-an-access-token) from your organization using the following scopes. +
To access this API in WSO2 Identity Platform, you need to first [get an access token](https://wso2.com/asgardeo/docs/apis/authentication/#get-an-access-token) from your organization using the following scopes. Scopes required:
- ```internal_identity_mgt_view``` diff --git a/en/asgardeo/docs/apis/restapis/push-notification-devices.yaml b/en/asgardeo/docs/apis/restapis/push-notification-devices.yaml index cb316105c4..cdd9ff0613 100644 --- a/en/asgardeo/docs/apis/restapis/push-notification-devices.yaml +++ b/en/asgardeo/docs/apis/restapis/push-notification-devices.yaml @@ -2,7 +2,7 @@ openapi: 3.0.0 info: version: "v1" title: 'Push Notification Device Management API' - description: 'This is the RESTful API for managing devices used for the push notification feature by the users in Asgardeo.' + description: 'This is the RESTful API for managing devices used for the push notification feature by the users in WSO2 Identity Platform.' servers: - url: 'https://api.asgardeo.io/t/{tenant-domain}/api/users/v1/me/push' tags: diff --git a/en/asgardeo/docs/apis/restapis/roles.yaml b/en/asgardeo/docs/apis/restapis/roles.yaml index 3bc1055a05..d2d7b1da49 100644 --- a/en/asgardeo/docs/apis/restapis/roles.yaml +++ b/en/asgardeo/docs/apis/restapis/roles.yaml @@ -1,11 +1,11 @@ openapi: 3.0.0 info: - title: Asgardeo - SCIM 2.0 Roles V2 API + title: WSO2 Identity Platform - SCIM 2.0 Roles V2 API description: | - This is the RESTful API for SCIM 2.0 Roles API in Asgardeo. + This is the RESTful API for SCIM 2.0 Roles API in WSO2 Identity Platform. This API allows creating, deleting, listing, roles and updating role name, permissions, users and groups of the roles. - To access the SCIM 2.0 Roles APIs in Asgardeo, you need to first [get an access token](https://wso2.com/asgardeo/docs/apis/authentication/#get-an-access-token) from your organization. + To access the SCIM 2.0 Roles APIs in WSO2 Identity Platform, you need to first [get an access token](https://wso2.com/asgardeo/docs/apis/authentication/#get-an-access-token) from your organization. servers: - url: https://api.asgardeo.io/t/{organization-name}/scim2/v2 security: diff --git a/en/asgardeo/docs/apis/restapis/rule-metadata.yaml b/en/asgardeo/docs/apis/restapis/rule-metadata.yaml index 857b83853f..14c74881f4 100644 --- a/en/asgardeo/docs/apis/restapis/rule-metadata.yaml +++ b/en/asgardeo/docs/apis/restapis/rule-metadata.yaml @@ -1,6 +1,6 @@ openapi: 3.0.1 info: - title: Asgardeo Rule Metadata REST API + title: WSO2 Identity Platform Rule Metadata REST API description: "The Rule Metadata API provides the essential metadata required to configure rules dynamically based on the flow context. \nThe metadata retrieved by this API is designed to support rule configuration in the user interface (UI) by delivering information about each configurable field, the set of applicable comparison operators (e.g., equals, contains) for each field, and lists of possible values or options for fields.\n" contact: name: WSO2 diff --git a/en/asgardeo/docs/apis/restapis/scim2-agents.yaml b/en/asgardeo/docs/apis/restapis/scim2-agents.yaml index edb5c29627..108a441ab2 100644 --- a/en/asgardeo/docs/apis/restapis/scim2-agents.yaml +++ b/en/asgardeo/docs/apis/restapis/scim2-agents.yaml @@ -2,7 +2,7 @@ openapi: 3.1.0 info: title: AI Agent Management API description: | - This document specifies the REST API for **AI Agent Management** in **Asgardeo**. + This document specifies the REST API for **AI Agent Management** in **WSO2 Identity Platform**. The Agent Management API allows to create, retrieve, update, and delete AI agent identities, allowing agents to be managed in the same way as human users while remaining clearly distinguishable from them. version: 1.0.0 servers: diff --git a/en/asgardeo/docs/apis/restapis/scim2-bulk.yaml b/en/asgardeo/docs/apis/restapis/scim2-bulk.yaml index 6299f9bf05..9f9cf0e35e 100644 --- a/en/asgardeo/docs/apis/restapis/scim2-bulk.yaml +++ b/en/asgardeo/docs/apis/restapis/scim2-bulk.yaml @@ -1,8 +1,8 @@ openapi: 3.0.1 info: - title: Asgardeo - SCIM 2.0 Bulk API + title: WSO2 Identity Platform - SCIM 2.0 Bulk API description: | - This document specifies **SCIM 2.0 Bulk RESTful API** for **Asgardeo**. To access the SCIM 2.0 APIs in Asgardeo, you need to first [get an access token](https://wso2.com/asgardeo/docs/apis/authentication/#get-an-access-token) from your organization. + This document specifies **SCIM 2.0 Bulk RESTful API** for **WSO2 Identity Platform**. To access the SCIM 2.0 APIs in WSO2 Identity Platform, you need to first [get an access token](https://wso2.com/asgardeo/docs/apis/authentication/#get-an-access-token) from your organization. version: "v1" servers: - url: 'https://api.asgardeo.io/t/{organization-name}/scim2' @@ -99,7 +99,7 @@ components: failOnErrors: type: integer example: 1 - description: The number of errors that will be accepted by Asgardeo before returning the response. + description: The number of errors that will be accepted by WSO2 Identity Platform before returning the response. schemas: type: array description: This is the schema that is required for sending bulk requests @@ -121,7 +121,7 @@ components: failOnErrors: type: integer example: 1 - description: The number of errors that will be accepted by Asgardeo before returning the response. + description: The number of errors that will be accepted by WSO2 Identity Platform before returning the response. schemas: type: array description: This is the schema that is required for sending bulk requests @@ -143,7 +143,7 @@ components: failOnErrors: type: integer example: 1 - description: The number of errors that will be accepted by Asgardeo before returning the response. + description: The number of errors that will be accepted by WSO2 Identity Platform before returning the response. schemas: type: array description: This is the schema that is required for sending bulk requests @@ -165,7 +165,7 @@ components: failOnErrors: type: integer example: 1 - description: The number of errors that will be accepted by Asgardeo before returning the response. + description: The number of errors that will be accepted by WSO2 Identity Platform before returning the response. schemas: type: array description: This is the schema that is required for sending bulk requests @@ -187,7 +187,7 @@ components: failOnErrors: type: integer example: 1 - description: The number of errors that will be accepted by Asgardeo before returning the response. + description: The number of errors that will be accepted by WSO2 Identity Platform before returning the response. schemas: type: array description: This is the schema that is required for sending bulk requests @@ -209,7 +209,7 @@ components: failOnErrors: type: integer example: 1 - description: The number of errors that will be accepted by Asgardeo before returning the response. + description: The number of errors that will be accepted by WSO2 Identity Platform before returning the response. schemas: type: array description: This is the schema that is required for sending bulk requests @@ -231,7 +231,7 @@ components: failOnErrors: type: integer example: 1 - description: The number of errors that will be accepted by Asgardeo before returning the response. + description: The number of errors that will be accepted by WSO2 Identity Platform before returning the response. schemas: type: array description: This is the schema that is required for sending bulk requests @@ -253,7 +253,7 @@ components: failOnErrors: type: integer example: 1 - description: The number of errors that will be accepted by Asgardeo before returning the response. + description: The number of errors that will be accepted by WSO2 Identity Platform before returning the response. schemas: type: array description: This is the schema that is required for sending bulk requests diff --git a/en/asgardeo/docs/apis/restapis/scim2-groups.yaml b/en/asgardeo/docs/apis/restapis/scim2-groups.yaml index 57a3881804..ea29b0173a 100644 --- a/en/asgardeo/docs/apis/restapis/scim2-groups.yaml +++ b/en/asgardeo/docs/apis/restapis/scim2-groups.yaml @@ -1,8 +1,8 @@ openapi: 3.0.1 info: - title: Asgardeo - SCIM 2.0 Groups API + title: WSO2 Identity Platform - SCIM 2.0 Groups API description: | - This document specifies **SCIM 2.0 Group Management RESTful API** for **Asgardeo**. This endpoint performs actions related to all users in the organization. To access the SCIM 2.0 APIs in Asgardeo, you need to first [get an access token](https://wso2.com/asgardeo/docs/apis/authentication/#get-an-access-token) from your organization. + This document specifies **SCIM 2.0 Group Management RESTful API** for **WSO2 Identity Platform**. This endpoint performs actions related to all users in the organization. To access the SCIM 2.0 APIs in WSO2 Identity Platform, you need to first [get an access token](https://wso2.com/asgardeo/docs/apis/authentication/#get-an-access-token) from your organization. version: "v1" servers: - url: 'https://api.asgardeo.io/t/{organization-name}/scim2' diff --git a/en/asgardeo/docs/apis/restapis/scim2-me.yaml b/en/asgardeo/docs/apis/restapis/scim2-me.yaml index d350b559e6..f0aa38831d 100644 --- a/en/asgardeo/docs/apis/restapis/scim2-me.yaml +++ b/en/asgardeo/docs/apis/restapis/scim2-me.yaml @@ -2,7 +2,7 @@ openapi: 3.0.1 info: title: SCIM 2.0 Me API description: | - This document specifies **SCIM 2.0 Me RESTful API** for **Asgardeo**. + This document specifies **SCIM 2.0 Me RESTful API** for **WSO2 Identity Platform**. version: "v1" servers: - url: 'https://api.asgardeo.io/t/{organization-name}/scim2' @@ -217,7 +217,7 @@ components: example: Berry userName: type: string - description: By default, the username should be the email address and it will be stored in the `DEFAULT` user store. However, if username validation is changed to `Alphanumeric` in your Asgardeo organization, you need to specify an alphanumeric value (a-z, A-Z, 0-9) as the username instead of the email. + description: By default, the username should be the email address and it will be stored in the `DEFAULT` user store. However, if username validation is changed to `Alphanumeric` in your WSO2 Identity Platform organization, you need to specify an alphanumeric value (a-z, A-Z, 0-9) as the username instead of the email. example: DEFAULT/kim@gmail.com password: type: string @@ -269,7 +269,7 @@ components: example: Berry userName: type: string - description: By default, the username should be the email address and it will be stored in the `DEFAULT` user store. However, if username validation is changed to `Alphanumeric` in your Asgardeo organization, you need to specify an alphanumeric value (a-z, A-Z, 0-9) as the username instead of the email. + description: By default, the username should be the email address and it will be stored in the `DEFAULT` user store. However, if username validation is changed to `Alphanumeric` in your WSO2 Identity Platform organization, you need to specify an alphanumeric value (a-z, A-Z, 0-9) as the username instead of the email. example: DEFAULT/kim@gmail.com emails: type: array diff --git a/en/asgardeo/docs/apis/restapis/scim2-resource-types.yaml b/en/asgardeo/docs/apis/restapis/scim2-resource-types.yaml index e8a6ba643c..e39086b741 100644 --- a/en/asgardeo/docs/apis/restapis/scim2-resource-types.yaml +++ b/en/asgardeo/docs/apis/restapis/scim2-resource-types.yaml @@ -2,7 +2,7 @@ openapi: 3.0.1 info: title: SCIM 2.0 Resource Types Retrieval API description: | - This document specifies **SCIM 2.0 Resource types RESTful API** for **Asgardeo**. + This document specifies **SCIM 2.0 Resource types RESTful API** for **WSO2 Identity Platform**. version: "v1" servers: - url: 'https://api.asgardeo.io/t/{organization-name}/scim2' diff --git a/en/asgardeo/docs/apis/restapis/scim2-schemas.yaml b/en/asgardeo/docs/apis/restapis/scim2-schemas.yaml index 058cdabf15..ef42c24266 100644 --- a/en/asgardeo/docs/apis/restapis/scim2-schemas.yaml +++ b/en/asgardeo/docs/apis/restapis/scim2-schemas.yaml @@ -2,7 +2,7 @@ openapi: 3.0.1 info: title: SCIM 2.0 Schemas Retrieval API description: | - This document specifies **SCIM 2.0 Schemas RESTful API** for **Asgardeo**. + This document specifies **SCIM 2.0 Schemas RESTful API** for **WSO2 Identity Platform**. version: "v1" servers: - url: 'https://api.asgardeo.io/t/{organization-name}/scim2' diff --git a/en/asgardeo/docs/apis/restapis/scim2-sp-configs.yaml b/en/asgardeo/docs/apis/restapis/scim2-sp-configs.yaml index 2f9619dae5..a83e6c6483 100644 --- a/en/asgardeo/docs/apis/restapis/scim2-sp-configs.yaml +++ b/en/asgardeo/docs/apis/restapis/scim2-sp-configs.yaml @@ -1,8 +1,8 @@ openapi: 3.0.1 info: - title: Asgardeo - SCIM 2.0 Service Provider Configs API + title: WSO2 Identity Platform - SCIM 2.0 Service Provider Configs API description: | - This document specifies **SCIM 2.0 Service provider configuration RESTful API** for **Asgardeo**. + This document specifies **SCIM 2.0 Service provider configuration RESTful API** for **WSO2 Identity Platform**. version: "v1" servers: - url: 'https://api.asgardeo.io/t/{organization-name}/scim2' diff --git a/en/asgardeo/docs/apis/restapis/scim2-users.yaml b/en/asgardeo/docs/apis/restapis/scim2-users.yaml index 3fff9df7d3..23ff5104ab 100644 --- a/en/asgardeo/docs/apis/restapis/scim2-users.yaml +++ b/en/asgardeo/docs/apis/restapis/scim2-users.yaml @@ -1,8 +1,8 @@ openapi: 3.0.1 info: - title: Asgardeo - SCIM 2.0 Users API + title: WSO2 Identity Platform - SCIM 2.0 Users API description: | - This document specifies **SCIM 2.0 User Management RESTful API** for **Asgardeo**. This endpoint performs actions related to all users in the organization. To access the SCIM 2.0 APIs in Asgardeo, you need to first [get an access token](https://wso2.com/asgardeo/docs/apis/authentication/#get-an-access-token) from your organization. + This document specifies **SCIM 2.0 User Management RESTful API** for **WSO2 Identity Platform**. This endpoint performs actions related to all users in the organization. To access the SCIM 2.0 APIs in WSO2 Identity Platform, you need to first [get an access token](https://wso2.com/asgardeo/docs/apis/authentication/#get-an-access-token) from your organization. version: "v1" servers: - url: 'https://api.asgardeo.io/t/{organization-name}/scim2' @@ -514,7 +514,7 @@ components: example: Berry userName: type: string - description: By default, the username should be the email address and it will be stored in the `DEFAULT` user store. However, if username validation is changed to `Alphanumeric` in your Asgardeo organization, you need to specify an alphanumeric value (a-z, A-Z, 0-9) as the username instead of the email. + description: By default, the username should be the email address and it will be stored in the `DEFAULT` user store. However, if username validation is changed to `Alphanumeric` in your WSO2 Identity Platform organization, you need to specify an alphanumeric value (a-z, A-Z, 0-9) as the username instead of the email. example: DEFAULT/kim@gmail.com password: type: string @@ -566,7 +566,7 @@ components: example: Berry userName: type: string - description: By default, the username should be the email address and it will be stored in the `DEFAULT` user store. However, if username validation is changed to `Alphanumeric` in your Asgardeo organization, you need to specify an alphanumeric value (a-z, A-Z, 0-9) as the username instead of the email. + description: By default, the username should be the email address and it will be stored in the `DEFAULT` user store. However, if username validation is changed to `Alphanumeric` in your WSO2 Identity Platform organization, you need to specify an alphanumeric value (a-z, A-Z, 0-9) as the username instead of the email. example: DEFAULT/kim@gmail.com emails: type: array diff --git a/en/asgardeo/docs/apis/restapis/session.yaml b/en/asgardeo/docs/apis/restapis/session.yaml index a5069c00cb..d9d6ce7968 100644 --- a/en/asgardeo/docs/apis/restapis/session.yaml +++ b/en/asgardeo/docs/apis/restapis/session.yaml @@ -1,8 +1,8 @@ openapi: 3.0.1 info: - title: Asgardeo - User Session Management API - description: "This is the RESTful API for managing user sessions in Asgardeo. - \n To access the session management APIs in Asgardeo, you need to first [get an access token](https://wso2.com/asgardeo/docs/apis/authentication/#get-an-access-token) from your organization." + title: WSO2 Identity Platform - User Session Management API + description: "This is the RESTful API for managing user sessions in WSO2 Identity Platform. + \n To access the session management APIs in WSO2 Identity Platform, you need to first [get an access token](https://wso2.com/asgardeo/docs/apis/authentication/#get-an-access-token) from your organization." version: v1 servers: - url: https://api.asgardeo.io/t/{organization-name}/api/users/v1 diff --git a/en/asgardeo/docs/apis/restapis/totp.yaml b/en/asgardeo/docs/apis/restapis/totp.yaml index 6161a0148f..fe229b344a 100644 --- a/en/asgardeo/docs/apis/restapis/totp.yaml +++ b/en/asgardeo/docs/apis/restapis/totp.yaml @@ -2,9 +2,9 @@ openapi: 3.0.0 info: description: | - This is the RESTful API for a user to manage TOTP QR URLs/secrets in Asgardeo. + This is the RESTful API for a user to manage TOTP QR URLs/secrets in WSO2 Identity Platform. version: "v1" - title: "Asgardeo - TOTP API Definition" + title: "WSO2 Identity Platform - TOTP API Definition" servers: - url: https://api.asgardeo.io/t/{organization-name}/api/users/v1 diff --git a/en/asgardeo/docs/apis/restapis/user-account-recovery.yaml b/en/asgardeo/docs/apis/restapis/user-account-recovery.yaml index 6e569e394f..b965e67d9a 100644 --- a/en/asgardeo/docs/apis/restapis/user-account-recovery.yaml +++ b/en/asgardeo/docs/apis/restapis/user-account-recovery.yaml @@ -3,7 +3,7 @@ info: version: "v2" title: User Account Recovery API description: > - This document specifies **User initiated Username and Password Recovery related RESTful API** for Asgardeo. + This document specifies **User initiated Username and Password Recovery related RESTful API** for WSO2 Identity Platform. paths: /recovery/username/init: post: diff --git a/en/asgardeo/docs/apis/restapis/user-identity-verification.yaml b/en/asgardeo/docs/apis/restapis/user-identity-verification.yaml index df94a55357..6536939874 100644 --- a/en/asgardeo/docs/apis/restapis/user-identity-verification.yaml +++ b/en/asgardeo/docs/apis/restapis/user-identity-verification.yaml @@ -2,7 +2,7 @@ openapi: 3.0.3 info: title: Identity Verification API description: |- - This is the RESTful API for users to manage their identity verification information stored in Asgardeo. + This is the RESTful API for users to manage their identity verification information stored in WSO2 Identity Platform. servers: - url: 'https://api.asgardeo.io/t/{organization-name}/api/users/v1' security: diff --git a/en/asgardeo/docs/apis/restapis/user-organization.yaml b/en/asgardeo/docs/apis/restapis/user-organization.yaml index e3367da37d..ec4463ac95 100644 --- a/en/asgardeo/docs/apis/restapis/user-organization.yaml +++ b/en/asgardeo/docs/apis/restapis/user-organization.yaml @@ -1,9 +1,9 @@ openapi: 3.0.0 info: version: "v1" - title: 'Asgardeo - User Organization Management API Definition' + title: 'WSO2 Identity Platform - User Organization Management API Definition' description: | - This document specifies an **User Organization Management RESTful API** for **Asgardeo**. + This document specifies an **User Organization Management RESTful API** for **WSO2 Identity Platform**. This API provides the capability to retrieve the resident organization of the authenticated user. license: diff --git a/en/asgardeo/docs/apis/restapis/user-password.yaml b/en/asgardeo/docs/apis/restapis/user-password.yaml index 7d15d44b07..e28b4824a6 100644 --- a/en/asgardeo/docs/apis/restapis/user-password.yaml +++ b/en/asgardeo/docs/apis/restapis/user-password.yaml @@ -1,14 +1,14 @@ openapi: 3.0.0 info: version: "v1" - title: Asgardeo - Self Password Update API + title: WSO2 Identity Platform - Self Password Update API description: | - This is the RESTful API for self-password updates in Asgardeo, allowing authenticated users to change their own passwords. + This is the RESTful API for self-password updates in WSO2 Identity Platform, allowing authenticated users to change their own passwords. Scope(Permission) required: `internal_user_password_update`
⚠️ Mandatory Configuration
-To enable this API, you must authorize the following API resource within your application settings in the Asgardeo Console:
+To enable this API, you must authorize the following API resource within your application settings in the WSO2 Identity Platform Console:
" diff --git a/en/asgardeo/docs/complete-guides/dotnet/prerequisites.md b/en/asgardeo/docs/complete-guides/dotnet/prerequisites.md index 0eaa2891cd..55ae07404a 100644 --- a/en/asgardeo/docs/complete-guides/dotnet/prerequisites.md +++ b/en/asgardeo/docs/complete-guides/dotnet/prerequisites.md @@ -7,8 +7,8 @@ read_time: 30 secs Before you start, ensure you have the following: - About 60 minutes of time. -- An Asgardeo account. -- Create [a test user in Asgardeo](https://wso2.com/asgardeo/docs/guides/users/manage-users/#onboard-users) +- An WSO2 Identity Platform account. +- Create [a test user in WSO2 Identity Platform](https://wso2.com/asgardeo/docs/guides/users/manage-users/#onboard-users) - [.NET 8 SDK](https://dotnet.microsoft.com/en-us/download){:target="_blank"} or later. - [Visual Studio Code](https://code.visualstudio.com/). diff --git a/en/asgardeo/docs/complete-guides/dotnet/register-an-application.md b/en/asgardeo/docs/complete-guides/dotnet/register-an-application.md index e6f2d691be..2d45f90a23 100644 --- a/en/asgardeo/docs/complete-guides/dotnet/register-an-application.md +++ b/en/asgardeo/docs/complete-guides/dotnet/register-an-application.md @@ -4,7 +4,7 @@ heading: Register an application read_time: 2 min --- -If you have not already done so, you will need to create an organization in Asgardeo and register your application as given below. +If you have not already done so, you will need to create an organization in WSO2 Identity Platform and register your application as given below. * Sign up for a [free {{product_name}} account](https://wso2.com/asgardeo/docs/get-started/create-asgardeo-account/){:target="_blank"} diff --git a/en/asgardeo/docs/complete-guides/expressjs/install-passport-asgardeo.md b/en/asgardeo/docs/complete-guides/expressjs/install-passport-asgardeo.md index 10394290b0..7b2418eb71 100644 --- a/en/asgardeo/docs/complete-guides/expressjs/install-passport-asgardeo.md +++ b/en/asgardeo/docs/complete-guides/expressjs/install-passport-asgardeo.md @@ -1,6 +1,6 @@ --- template: templates/complete-guide.html -heading: Install and configure Passport Asgardeo +heading: Install and configure Passport WSO2 Identity Platform read_time: 2 min --- diff --git a/en/asgardeo/docs/complete-guides/expressjs/prerequisite.md b/en/asgardeo/docs/complete-guides/expressjs/prerequisite.md index 0d54ee6547..538cf92ba3 100644 --- a/en/asgardeo/docs/complete-guides/expressjs/prerequisite.md +++ b/en/asgardeo/docs/complete-guides/expressjs/prerequisite.md @@ -8,7 +8,7 @@ read_time: 30 secs * About 60 minutes * {{product_name}} account -* Create [a test user in Asgardeo](https://wso2.com/asgardeo/docs/guides/users/manage-users/#onboard-users) +* Create [a test user in WSO2 Identity Platform](https://wso2.com/asgardeo/docs/guides/users/manage-users/#onboard-users) * [Node.js](https://nodejs.org/en/download/package-manager){:target="_blank"} v18+ and npm * A favorite text editor or IDE diff --git a/en/asgardeo/docs/complete-guides/expressjs/register-an-application.md b/en/asgardeo/docs/complete-guides/expressjs/register-an-application.md index 68f5457989..ad9d74ffe7 100644 --- a/en/asgardeo/docs/complete-guides/expressjs/register-an-application.md +++ b/en/asgardeo/docs/complete-guides/expressjs/register-an-application.md @@ -1,6 +1,6 @@ --- template: templates/complete-guide.html -heading: Register an application in Asgardeo +heading: Register an application in WSO2 Identity Platform read_time: 2 min --- diff --git a/en/asgardeo/docs/complete-guides/javascript/install-asgardeo-sdk.md b/en/asgardeo/docs/complete-guides/javascript/install-asgardeo-sdk.md index f5d0ca540b..d50ee3ffb3 100644 --- a/en/asgardeo/docs/complete-guides/javascript/install-asgardeo-sdk.md +++ b/en/asgardeo/docs/complete-guides/javascript/install-asgardeo-sdk.md @@ -1,6 +1,6 @@ --- template: templates/complete-guide.html -heading: Install and configure Asgardeo SDK +heading: Install and configure WSO2 Identity Platform SDK read_time: 2 min --- diff --git a/en/asgardeo/docs/complete-guides/javascript/prerequisite.md b/en/asgardeo/docs/complete-guides/javascript/prerequisite.md index 08a3efac6c..cdc0a206ec 100644 --- a/en/asgardeo/docs/complete-guides/javascript/prerequisite.md +++ b/en/asgardeo/docs/complete-guides/javascript/prerequisite.md @@ -8,7 +8,7 @@ read_time: 30 secs * About 60 minutes * {{product_name}} account -* Create [a test user in Asgardeo](https://wso2.com/asgardeo/docs/guides/users/manage-users/#onboard-users) +* Create [a test user in WSO2 Identity Platform](https://wso2.com/asgardeo/docs/guides/users/manage-users/#onboard-users) * [Node.js](https://nodejs.org/en/download/package-manager){:target="_blank"} v18+ and npm * A favorite text editor or IDE diff --git a/en/asgardeo/docs/complete-guides/javascript/register-an-application.md b/en/asgardeo/docs/complete-guides/javascript/register-an-application.md index 8356f672ec..c6e7cf0794 100644 --- a/en/asgardeo/docs/complete-guides/javascript/register-an-application.md +++ b/en/asgardeo/docs/complete-guides/javascript/register-an-application.md @@ -1,6 +1,6 @@ --- template: templates/complete-guide.html -heading: Register an application in Asgardeo +heading: Register an application in WSO2 Identity Platform read_time: 2 min --- diff --git a/en/asgardeo/docs/complete-guides/nextjs-b2b/introduction.md b/en/asgardeo/docs/complete-guides/nextjs-b2b/introduction.md index c677531a8c..18a174180b 100644 --- a/en/asgardeo/docs/complete-guides/nextjs-b2b/introduction.md +++ b/en/asgardeo/docs/complete-guides/nextjs-b2b/introduction.md @@ -1,6 +1,6 @@ --- template: templates/complete-guide.html -heading: A Guide to Building a B2B Team Management App with Next.js and Asgardeo +heading: A Guide to Building a B2B Team Management App with Next.js and WSO2 Identity Platform read_time: 2 mins --- {% include "../../../../includes/complete-guides/nextjs-b2b/introduction.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/complete-guides/nextjs-b2b/prerequisite.md b/en/asgardeo/docs/complete-guides/nextjs-b2b/prerequisite.md index 0645da40b8..2fb4b2267f 100644 --- a/en/asgardeo/docs/complete-guides/nextjs-b2b/prerequisite.md +++ b/en/asgardeo/docs/complete-guides/nextjs-b2b/prerequisite.md @@ -8,7 +8,7 @@ read_time: 30 secs * About 120 minutes * {{product_name}} account -* Create [a test user in Asgardeo](https://wso2.com/asgardeo/docs/guides/users/manage-users/#onboard-users) +* Create [a test user in WSO2 Identity Platform](https://wso2.com/asgardeo/docs/guides/users/manage-users/#onboard-users) * [Node.js](https://nodejs.org/en/download/package-manager){:target="_blank"} v20+ and npm * A favorite text editor or IDE diff --git a/en/asgardeo/docs/complete-guides/nextjs-b2b/register-an-application.md b/en/asgardeo/docs/complete-guides/nextjs-b2b/register-an-application.md index 264701ad73..b87986226a 100644 --- a/en/asgardeo/docs/complete-guides/nextjs-b2b/register-an-application.md +++ b/en/asgardeo/docs/complete-guides/nextjs-b2b/register-an-application.md @@ -1,6 +1,6 @@ --- template: templates/complete-guide.html -heading: Register an application in Asgardeo +heading: Register an application in WSO2 Identity Platform read_time: 2 min --- @@ -25,7 +25,7 @@ First unless you already have done that, you need to create an organization in { The authorized redirect URL determines where {{product_name}} should send users after they successfully log in. Typically, this will be the web address where your application is hosted. For this guide, we'll use http://localhost:3000, as the sample application will be accessible at this URL -5. Make a note of the following values from the **Guide** tab of the registered application. You will need them to configure the Asgardeo provider. +5. Make a note of the following values from the **Guide** tab of the registered application. You will need them to configure the WSO2 Identity Platform provider. ```bash NEXT_PUBLIC_ASGARDEO_BASE_URL="https://api.asgardeo.io/t/ " diff --git a/en/asgardeo/docs/complete-guides/nextjs/prerequisite.md b/en/asgardeo/docs/complete-guides/nextjs/prerequisite.md index c9f44ee840..17694cda89 100644 --- a/en/asgardeo/docs/complete-guides/nextjs/prerequisite.md +++ b/en/asgardeo/docs/complete-guides/nextjs/prerequisite.md @@ -8,7 +8,7 @@ read_time: 30 secs * About 60 minutes * {{product_name}} account -* Create [a test user in Asgardeo](https://wso2.com/asgardeo/docs/guides/users/manage-users/#onboard-users) +* Create [a test user in WSO2 Identity Platform](https://wso2.com/asgardeo/docs/guides/users/manage-users/#onboard-users) * [Node.js](https://nodejs.org/en/download/package-manager){:target="_blank"} v20+ and npm * A favorite text editor or IDE diff --git a/en/asgardeo/docs/complete-guides/nextjs/register-an-application.md b/en/asgardeo/docs/complete-guides/nextjs/register-an-application.md index 1bbc3992fa..2d9dd2d0f7 100644 --- a/en/asgardeo/docs/complete-guides/nextjs/register-an-application.md +++ b/en/asgardeo/docs/complete-guides/nextjs/register-an-application.md @@ -1,6 +1,6 @@ --- template: templates/complete-guide.html -heading: Register an application in Asgardeo +heading: Register an application in WSO2 Identity Platform read_time: 2 min --- @@ -25,7 +25,7 @@ Next, complete the wizard popup by providing a suitable name and an authorized r The authorized redirect URL determines where {{product_name}} should send users after they successfully log in. Typically, this will be the web address where your application is hosted. For this guide, we'll use http://localhost:3000, as the sample application will be accessible at this URL -Make a note of the following values from the **Guide** tab of the registered application. You will need them to configure the Asgardeo provider. +Make a note of the following values from the **Guide** tab of the registered application. You will need them to configure the WSO2 Identity Platform provider. ```bash NEXT_PUBLIC_ASGARDEO_BASE_URL="https://api.asgardeo.io/t/ " diff --git a/en/asgardeo/docs/complete-guides/react/install-asgardeo-sdk.md b/en/asgardeo/docs/complete-guides/react/install-asgardeo-sdk.md index 7068cdceb5..84cc3c3484 100644 --- a/en/asgardeo/docs/complete-guides/react/install-asgardeo-sdk.md +++ b/en/asgardeo/docs/complete-guides/react/install-asgardeo-sdk.md @@ -1,6 +1,6 @@ --- template: templates/complete-guide.html -heading: Install and configure Asgardeo SDK +heading: Install and configure WSO2 Identity Platform SDK read_time: 2 min --- diff --git a/en/asgardeo/docs/complete-guides/react/prerequisite.md b/en/asgardeo/docs/complete-guides/react/prerequisite.md index 719dab8363..fa14bb39c5 100644 --- a/en/asgardeo/docs/complete-guides/react/prerequisite.md +++ b/en/asgardeo/docs/complete-guides/react/prerequisite.md @@ -7,8 +7,8 @@ read_time: 30 secs ## Before you start, ensure you have the following * About 60 minutes -* Asgardeo [account](https://wso2.com/asgardeo/docs/get-started/create-asgardeo-account/){:target="_blank"} -* Create a [test user in Asgardeo](https://wso2.com/asgardeo/docs/guides/users/manage-users/#onboard-users) +* WSO2 Identity Platform [account](https://wso2.com/asgardeo/docs/get-started/create-asgardeo-account/){:target="_blank"} +* Create a [test user in WSO2 Identity Platform](https://wso2.com/asgardeo/docs/guides/users/manage-users/#onboard-users) * [Node.js](https://nodejs.org/en/download/package-manager){:target="_blank"} v20+ and npm * A favorite text editor or IDE diff --git a/en/asgardeo/docs/complete-guides/react/register-an-application.md b/en/asgardeo/docs/complete-guides/react/register-an-application.md index a2e0bacc17..0c91e34c19 100644 --- a/en/asgardeo/docs/complete-guides/react/register-an-application.md +++ b/en/asgardeo/docs/complete-guides/react/register-an-application.md @@ -1,14 +1,14 @@ --- template: templates/complete-guide.html -heading: Register an application in Asgardeo +heading: Register an application in WSO2 Identity Platform read_time: 2 min --- First unless you already have done that, you need to create an organization in {{product_name}} and register your application as a single page application. -* Sign up for a [free Asgardeo account](https://wso2.com/asgardeo/docs/get-started/create-asgardeo-account/){:target="_blank"} +* Sign up for a [free WSO2 Identity Platform account](https://wso2.com/asgardeo/docs/get-started/create-asgardeo-account/){:target="_blank"} -* Sign into the Asgardeo console and navigate to **Applications > New Application.** +* Sign into the WSO2 Identity Platform console and navigate to **Applications > New Application.** * Select React Application {: width="600" style="display: block; margin: 0;"} diff --git a/en/asgardeo/docs/get-started/create-asgardeo-account.md b/en/asgardeo/docs/get-started/create-asgardeo-account.md index b6e703810c..35c3d45199 100644 --- a/en/asgardeo/docs/get-started/create-asgardeo-account.md +++ b/en/asgardeo/docs/get-started/create-asgardeo-account.md @@ -1,36 +1,36 @@ -# Create your Asgardeo account +# Create your WSO2 Identity Platform account -Let's begin setting up your Asgardeo account. +Let's begin setting up your WSO2 Identity Platform account. ## Create an organization -An organization in Asgardeo will be your own unique space and it will contain your users and application configurations. Let's sign up and create your first organization. +An organization in WSO2 Identity Platform will be your own unique space and it will contain your users and application configurations. Let's sign up and create your first organization. -1. Go to the [Asgardeo webpage](https://wso2.com/asgardeo/) and click **Sign up for free**. +1. Go to the [WSO2 Identity Platform webpage](https://wso2.com/asgardeo/) and click **Sign up for free**. 2. Enter your email address and click **Register**. You will receive an email with instructions on how to complete your account creation. - {: width="700" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} + {: width="700" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} -3. Click **Confirm** on the email and fill in your information to create your Asgardeo account. +3. Click **Confirm** on the email and fill in your information to create your WSO2 Identity Platform account. !!! note You can also use one of the social login methods to create your account. -!!! tip "Access the Asgardeo Console" +!!! tip "Access the WSO2 Identity Platform Console" - As an organization owner or administrator, you can manage your organizations, applications, and users through the Asgardeo Console. Make sure to use the appropriate console URL based on the region chosen during registration. + As an organization owner or administrator, you can manage your organizations, applications, and users through the WSO2 Identity Platform Console. Make sure to use the appropriate console URL based on the region chosen during registration. - US Region: https://console.asgardeo.io/ - EU Region: https://console.eu.asgardeo.io/ ## Create a user -Users can log in to applications that you register in Asgardeo. Let's create a user by following the steps below. +Users can log in to applications that you register in WSO2 Identity Platform. Let's create a user by following the steps below. -1. On the Asgardeo Console, go to **User Management** > **Users**. +1. On the WSO2 Identity Platform Console, go to **User Management** > **Users**. 2. Click **Add User** > **Single User**. 3. Fill in the user's details. @@ -40,17 +40,17 @@ Users can log in to applications that you register in Asgardeo. Let's create a u 6. Click **Next** and **Finish**. -You can now manage this user account from the Asgardeo Console. +You can now manage this user account from the WSO2 Identity Platform Console. !!! note - Users can also manage their own accounts from the Asgardeo self-service portal. Learn more about [user self-service]({{base_path}}/guides/user-self-service/). + Users can also manage their own accounts from the WSO2 Identity Platform self-service portal. Learn more about [user self-service]({{base_path}}/guides/user-self-service/). ## What's next? Now that you've set up your own organization and created your first user, you can: -1. Use a test application to quickly try out Asgardeo. See [Try login with Asgardeo]({{base_path}}/get-started/try-it-application/). -2. Set up Asgardeo in your application or in a sample application. See [Start integrating Asgardeo into applications]({{base_path}}/get-started/start-integrating-apps/). +1. Use a test application to quickly try out WSO2 Identity Platform. See [Try login with WSO2 Identity Platform]({{base_path}}/get-started/try-it-application/). +2. Set up WSO2 Identity Platform in your application or in a sample application. See [Start integrating WSO2 Identity Platform into applications]({{base_path}}/get-started/start-integrating-apps/). diff --git a/en/asgardeo/docs/get-started/explore-asgardeo.md b/en/asgardeo/docs/get-started/explore-asgardeo.md index 01bed31606..b3b597f2b4 100644 --- a/en/asgardeo/docs/get-started/explore-asgardeo.md +++ b/en/asgardeo/docs/get-started/explore-asgardeo.md @@ -1,31 +1,31 @@ -# Explore Asgardeo +# Explore WSO2 Identity Platform ::: **WORK IN PROGRESS** ::: -See the topics given below to explore Asgardeo and its components. +See the topics given below to explore WSO2 Identity Platform and its components. -## What is Asgardeo? +## What is WSO2 Identity Platform? -Asgardeo is an identity as a service (IDaaS) solution that provides a fully integrated developer experience to create seamless login experiences in minutes. You can get started with common IAM use cases with no installation or maintenance hassles. +WSO2 Identity Platform is an identity as a service (IDaaS) solution that provides a fully integrated developer experience to create seamless login experiences in minutes. You can get started with common IAM use cases with no installation or maintenance hassles. -## Asgardeo console +## WSO2 Identity Platform console - The Asgardeo console is the + The WSO2 Identity Platform console is the ## Self-service portals (My Account) -The **My Account** portal is the self-service portal for Asgardeo users. If you are an owner of an Asgardeo of one or multiple Asgardeo organization, you can manage your personal profile from this portal. +The **My Account** portal is the self-service portal for WSO2 Identity Platform users. If you are an owner of an WSO2 Identity Platform of one or multiple WSO2 Identity Platform organization, you can manage your personal profile from this portal. Customers of your organizations will have their own **My Account** portal to manage their personal accounts. diff --git a/en/asgardeo/docs/get-started/index.md b/en/asgardeo/docs/get-started/index.md index 1b957f937a..262d9f76f0 100644 --- a/en/asgardeo/docs/get-started/index.md +++ b/en/asgardeo/docs/get-started/index.md @@ -3,10 +3,10 @@ template: templates/no-right-sidebar.html --- # Get Started - Overview -Welcome to Asgardeo! Here are some quick guides to start your journey into identity and access management with Asgardeo. +Welcome to WSO2 Identity Platform! Here are some quick guides to start your journey into identity and access management with WSO2 Identity Platform. ## Start integrating apps -Select a technology and try integrating an application with Asgardeo. +Select a technology and try integrating an application with WSO2 Identity Platform. [Learn more]({{base_path}}/get-started/start-integrating-apps/) diff --git a/en/asgardeo/docs/get-started/start-integrating-apps/index.md b/en/asgardeo/docs/get-started/start-integrating-apps/index.md index 232260d8e8..025e590212 100644 --- a/en/asgardeo/docs/get-started/start-integrating-apps/index.md +++ b/en/asgardeo/docs/get-started/start-integrating-apps/index.md @@ -1,6 +1,6 @@ # Start integrating apps -You can get started by integrating applications with Asgardeo. Try one of the sample applications or integrate your app using the Asgardeo SDKs. +You can get started by integrating applications with WSO2 Identity Platform. Try one of the sample applications or integrate your app using the WSO2 Identity Platform SDKs. - [Try a Sample App]({{base_path}}/get-started/try-samples/) - [Try your Own App]({{base_path}}/get-started/try-your-own-app/) diff --git a/en/asgardeo/docs/get-started/try-it-application.md b/en/asgardeo/docs/get-started/try-it-application.md index a8e7156210..d9eb327fe6 100644 --- a/en/asgardeo/docs/get-started/try-it-application.md +++ b/en/asgardeo/docs/get-started/try-it-application.md @@ -1,32 +1,32 @@ -# Try login with Asgardeo +# Try login with WSO2 Identity Platform -The following guide explains how you can quickly test login with Asgardeo using the **Try it** application provided by Asgardeo. +The following guide explains how you can quickly test login with WSO2 Identity Platform using the **Try it** application provided by WSO2 Identity Platform. !!! note "Before you begin" - - Create an account in Asgardeo. - - Create a user in Asgardeo (only users can login to applications created in Asgardeo). + - Create an account in WSO2 Identity Platform. + - Create a user in WSO2 Identity Platform (only users can login to applications created in WSO2 Identity Platform). - Refer [create your Asgardeo account]({{base_path}}/get-started/create-asgardeo-account/) to learn more. + Refer [create your WSO2 Identity Platform account]({{base_path}}/get-started/create-asgardeo-account/) to learn more. -## Asgardeo Try It app +## WSO2 Identity Platform Try It app -**Try It** is a test application that we have already set up and configured for you to quickly integrate authenticators and see how Asgardeo login works with applications. +**Try It** is a test application that we have already set up and configured for you to quickly integrate authenticators and see how WSO2 Identity Platform login works with applications. -Let's try a simple login flow in the Asgardeo Try It application: +Let's try a simple login flow in the WSO2 Identity Platform Try It application: -1. On the [Asgardeo Console](https://console.asgardeo.io/login), navigate to **Home** and click **Try login with the Try It app**. +1. On the [WSO2 Identity Platform Console](https://console.asgardeo.io/login), navigate to **Home** and click **Try login with the Try It app**. 2. A dialog box appears prompting you to create a user account. Create a user account or if you already have one, click **Continue** to proceed. -3. You are directed to the Asgardeo login screen. Use credentials of the user account you created above to log in to the application. +3. You are directed to the WSO2 Identity Platform login screen. Use credentials of the user account you created above to log in to the application. {: width="400" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} ## Customize the login flow -You can use the various authenticators Asgardeo offers to customize the login flow of the **Try it** application. To set up a custom login flow: +You can use the various authenticators WSO2 Identity Platform offers to customize the login flow of the **Try it** application. To set up a custom login flow: -1. On the Asgardeo Console, go to **Applications**, and select the **Asgardeo Try It** application. +1. On the WSO2 Identity Platform Console, go to **Applications**, and select the **WSO2 Identity Platform Try It** application. !!! tip Alternatively, navigate to **Home** and click the gear icon that appear in the **Try login with the Try It app** card after you have set it up. diff --git a/en/asgardeo/docs/get-started/try-samples/qsg-oidc-webapp-java-ee.md b/en/asgardeo/docs/get-started/try-samples/qsg-oidc-webapp-java-ee.md index 68abba6d6d..68c0eb3f22 100644 --- a/en/asgardeo/docs/get-started/try-samples/qsg-oidc-webapp-java-ee.md +++ b/en/asgardeo/docs/get-started/try-samples/qsg-oidc-webapp-java-ee.md @@ -8,19 +8,19 @@ By following this guide, you will be able to deploy a Java EE web application lo If you don't have it, install [Apache tomcat](https://tomcat.apache.org/tomcat-9.0-doc/setup.html){target="_blank"}. -- **A user account in Asgardeo** +- **A user account in WSO2 Identity Platform** - If you don't already have one, [create a user account]({{base_path}}/guides/users/manage-users/#onboard-a-user) in Asgardeo. + If you don't already have one, [create a user account]({{base_path}}/guides/users/manage-users/#onboard-a-user) in WSO2 Identity Platform. ## Register the app -Follow the steps given below to register the sample Java EE web application in Asgardeo. +Follow the steps given below to register the sample Java EE web application in WSO2 Identity Platform. -1. On the [Asgardeo Console](https://console.asgardeo.io/login), go to **Applications**. +1. On the [WSO2 Identity Platform Console](https://console.asgardeo.io/login), go to **Applications**. 2. Click **New Application** and select **Traditional Web Application**: - {: width="700" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} + {: width="700" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} 3. Enter the following details: @@ -151,7 +151,7 @@ Follow the steps given below to configure the sample app. issuer- Issuer endpoint of Asgardeo used for id token validation: + Issuer endpoint of WSO2 Identity Platform used for id token validation: @@ -159,7 +159,7 @@ Follow the steps given below to configure the sample app.https://api.asgardeo.io/t/{organization_name}/oauth2/token- authorizeEndpointThe authorization endpoint of your Asgardeo organization: + The authorization endpoint of your WSO2 Identity Platform organization: @@ -167,7 +167,7 @@ Follow the steps given below to configure the sample app.https://api.asgardeo.io/t/{organization_name}/oauth2/authorize- logoutEndpointThe logout endpoint of your Asgardeo organization: + The logout endpoint of your WSO2 Identity Platform organization: @@ -175,7 +175,7 @@ Follow the steps given below to configure the sample app.https://api.asgardeo.io/t/{organization_name}/oidc/logout- tokenEndpointThe token endpoint of your Asgardeo organization: + The token endpoint of your WSO2 Identity Platform organization: @@ -183,7 +183,7 @@ Follow the steps given below to configure the sample app.https://api.asgardeo.io/t/{organization_name}/oauth2/token- jwksEndpointThe jwks endpoint of your Asgardeo organization: + The jwks endpoint of your WSO2 Identity Platform organization: @@ -202,8 +202,8 @@ Follow the steps given below to run the sample. 1. Access the application using the following URL: `http://localhost:8080/oidc-sample-app/index.html`. -2. Click **Login**. You will be redirected to the Asgardeo login page. +2. Click **Login**. You will be redirected to the WSO2 Identity Platform login page. - {: width="350" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} + {: width="350" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} 3. Enter the credentials of your user account and click **Sign In**. diff --git a/en/asgardeo/docs/get-started/try-samples/qsg-saml-webapp-java-ee.md b/en/asgardeo/docs/get-started/try-samples/qsg-saml-webapp-java-ee.md index 4684a32a6d..9790facdcf 100644 --- a/en/asgardeo/docs/get-started/try-samples/qsg-saml-webapp-java-ee.md +++ b/en/asgardeo/docs/get-started/try-samples/qsg-saml-webapp-java-ee.md @@ -8,19 +8,19 @@ By following this guide, you will be able to deploy a Java EE web application lo If you don't have it, install [Apache tomcat](https://tomcat.apache.org/tomcat-9.0-doc/setup.html){target="_blank"}. -- **A user account in Asgardeo** +- **A user account in WSO2 Identity Platform** - If you don't already have one, [create a user account]({{base_path}}/guides/users/manage-users/#onboard-a-user) in Asgardeo. + If you don't already have one, [create a user account]({{base_path}}/guides/users/manage-users/#onboard-a-user) in WSO2 Identity Platform. ## Register the app -Follow these steps given below to register the sample Java EE web application in Asgardeo. +Follow these steps given below to register the sample Java EE web application in WSO2 Identity Platform. -1. On the [Asgardeo Console](https://console.asgardeo.io/login), go to **Applications**. +1. On the [WSO2 Identity Platform Console](https://console.asgardeo.io/login), go to **Applications**. 2. Click **New Application** and select **Traditional Web Application**. - {: width="700" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} + {: width="700" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} 3. Enter the following details: @@ -110,8 +110,8 @@ Follow the steps given below to configure the sample app. !!! note - - Update the **SAML2.IdPEntityId** parameter with the Asgardeo issuer, which is `api.asgardeo.io/t/{organization_name}`. - - **SAML2.SPEntityId** should match the issuer name entered when registering the application in Asgardeo. + - Update the **SAML2.IdPEntityId** parameter with the WSO2 Identity Platform issuer, which is `api.asgardeo.io/t/{organization_name}`. + - **SAML2.SPEntityId** should match the issuer name entered when registering the application in WSO2 Identity Platform. ```saml SAML2.AssertionConsumerURL=http://localhost:8080/sample-app/home.jsp @@ -153,20 +153,20 @@ Follow the steps given below to configure the sample app.https://api.asgardeo.io/t/{organization_name}/oauth2/jwksSAML2.SPEntityId- The SAML issuer that is used when registering your application with Asgardeo. + The SAML issuer that is used when registering your application with WSO2 Identity Platform. SAML2.IdPEntityId- The issuer name of Asgardeo. + The issuer name of WSO2 Identity Platform.
api.asgardeo.io/t/{organization_name}@@ -223,8 +223,8 @@ Follow the steps given below to configure the sample app. SAML2.IdPURL- The endpoint of Asgardeo to which login and logout requests should be sent: + The endpoint of WSO2 Identity Platform to which login and logout requests should be sent:
https://api.asgardeo.io/t/{organization_name}/samlssoSAML2.EnableResponseSigning- If this configuration is set to true, the application validates the signature in the SAML response. You also need to [enable response signing from Asgardeo]({{base_path}}/references/app-settings/saml-settings-for-app/#response-signing). - If this configuration is set tofalse, the application does not mandate response signing from Asgardeo. + If this configuration is set totrue, the application validates the signature in the SAML response. You also need to [enable response signing from WSO2 Identity Platform]({{base_path}}/references/app-settings/saml-settings-for-app/#response-signing). + If this configuration is set tofalse, the application does not mandate response signing from WSO2 Identity Platform.@@ -232,8 +232,8 @@ Follow the steps given below to configure the sample app. SAML2.EnableAssertionSigning- If this configuration is set to true, the application validates the signature in the SAML assertion. You also need to [enable response signing from Asgardeo]({{base_path}}/references/app-settings/saml-settings-for-app/#response-signing). - If this configuration is set tofalse, the application does not mandate response signing from Asgardeo. + If this configuration is set totrue, the application validates the signature in the SAML assertion. You also need to [enable response signing from WSO2 Identity Platform]({{base_path}}/references/app-settings/saml-settings-for-app/#response-signing). + If this configuration is set tofalse, the application does not mandate response signing from WSO2 Identity Platform.@@ -241,7 +241,7 @@ Follow the steps given below to configure the sample app. SAML2.EnableAssertionEncryption- If this configuration is set to true, the application expects an encrypted SAML assertion. You also need to [enable encryption for SAML assertions]({{base_path}}/references/app-settings/saml-settings-for-app/) from Asgardeo. + If this configuration is set totrue, the application expects an encrypted SAML assertion. You also need to [enable encryption for SAML assertions]({{base_path}}/references/app-settings/saml-settings-for-app/) from WSO2 Identity Platform.@@ -249,7 +249,7 @@ Follow the steps given below to configure the sample app. SAML2.EnableRequestSigning- If this configuration is set to true, Asgardeo validates the SAML authentication request and logout request. You also need to [enable request signing]({{base_path}}/references/app-settings/saml-settings-for-app/) from Asgardeo. + If this configuration is set totrue, WSO2 Identity Platform validates the SAML authentication request and logout request. You also need to [enable request signing]({{base_path}}/references/app-settings/saml-settings-for-app/) from WSO2 Identity Platform.@@ -300,9 +300,9 @@ Follow the steps given below to run the sample. 1. Access the application using the following URL: `http://localhost:8080/sample-app/index.html`. -2. Click **Login**. You will be redirected to the Asgardeo login page. +2. Click **Login**. You will be redirected to the WSO2 Identity Platform login page. - {: width="350" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} + {: width="350" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} 3. Enter credentials of your user account and click **Sign In**. diff --git a/en/asgardeo/docs/get-started/try-samples/qsg-spa-javascript.md b/en/asgardeo/docs/get-started/try-samples/qsg-spa-javascript.md index 1b5864c114..255b7a3a63 100644 --- a/en/asgardeo/docs/get-started/try-samples/qsg-spa-javascript.md +++ b/en/asgardeo/docs/get-started/try-samples/qsg-spa-javascript.md @@ -8,15 +8,15 @@ By following this guide, you will be able to deploy a Javascript single-page app If you don't have it, [install npm and node](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm){target="_blank"} in your local environment. -- **A user account in Asgardeo** +- **A user account in WSO2 Identity Platform** - If you don't already have one, [create a user account]({{base_path}}/guides/users/manage-users/#onboard-a-user) in Asgardeo. + If you don't already have one, [create a user account]({{base_path}}/guides/users/manage-users/#onboard-a-user) in WSO2 Identity Platform. ## Register the app -Follow the steps given below to register the sample Javascript SPA in Asgardeo. +Follow the steps given below to register the sample Javascript SPA in WSO2 Identity Platform. -1. On the [Asgardeo Console](https://console.asgardeo.io/login), go to **Applications**. +1. On the [WSO2 Identity Platform Console](https://console.asgardeo.io/login), go to **Applications**. 2. Click **New Application** and select **Single-Page Application**. @@ -107,7 +107,7 @@ Follow the steps given below to configure the sample app. clientID- The client id that you received when you registered the application in Asgardeo. + The client id that you received when you registered the application in WSO2 Identity Platform. @@ -115,7 +115,7 @@ Follow the steps given below to configure the sample app. @@ -126,7 +126,7 @@ Follow the steps given below to configure the sample app.baseUrl- All authentication requests that the client application makes to Asgardeo will be appended to this base URL.:
+All authentication requests that the client application makes to WSO2 Identity Platform will be appended to this base URL.:
https://api.asgardeo.io/t/{organization_name}@@ -144,9 +144,9 @@ Follow the steps given below to run the sample. 2. Once the app is successfully compiled, it is accessible at `https://localhost:3000`. -3. Click **Login**. You will be redirected to the Asgardeo login page. +3. Click **Login**. You will be redirected to the WSO2 Identity Platform login page. - {: width="350" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} + {: width="350" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} 4. Enter the credentials of your user account and click **Sign In**. diff --git a/en/asgardeo/docs/get-started/try-samples/qsg-spa-react.md b/en/asgardeo/docs/get-started/try-samples/qsg-spa-react.md index 9ca5d61330..fbff3493c2 100755 --- a/en/asgardeo/docs/get-started/try-samples/qsg-spa-react.md +++ b/en/asgardeo/docs/get-started/try-samples/qsg-spa-react.md @@ -8,15 +8,15 @@ By following this guide, you will be able to deploy a React single-page applicat If you don't have it, [install npm and node](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm){target="_blank"} in your local environment. -- **A user account in Asgardeo** +- **A user account in WSO2 Identity Platform** - If you don't already have one, [create a user account]({{base_path}}/guides/users/manage-users/#onboard-a-user) in Asgardeo. + If you don't already have one, [create a user account]({{base_path}}/guides/users/manage-users/#onboard-a-user) in WSO2 Identity Platform. ## Register the app -Follow the steps given below to register the sample React SPA in Asgardeo. +Follow the steps given below to register the sample React SPA in WSO2 Identity Platform. -1. On the [Asgardeo Console](https://console.asgardeo.io/login), go to **Applications**. +1. On the [WSO2 Identity Platform Console](https://console.asgardeo.io/login), go to **Applications**. 2. Click **New Application** and select **Single-Page Application** @@ -111,7 +111,7 @@ Follow the steps given below to configure the sample app. The list of OIDC scopes that are used for requesting user information. You can add OIDC scopes such as
profileand"scope": ["profile", "email"]-Learn more about [OIDC scopes in Asgardeo]({{base_path}}/guides/users/attributes/manage-scopes/).
+Learn more about [OIDC scopes in WSO2 Identity Platform]({{base_path}}/guides/users/attributes/manage-scopes/).
clientID- The client id that you received when you registered the application in Asgardeo. + The client id that you received when you registered the application in WSO2 Identity Platform. @@ -119,7 +119,7 @@ Follow the steps given below to configure the sample app. @@ -130,7 +130,7 @@ Follow the steps given below to configure the sample app.baseUrl- All authentication requests that the client application makes to Asgardeo will be appended to this base URL.:
+All authentication requests that the client application makes to WSO2 Identity Platform will be appended to this base URL.:
https://api.asgardeo.io/t/{organization_name}@@ -148,9 +148,9 @@ Follow the steps given below to run the sample. 2. Once the app is successfully compiled, it is accessible at `https://localhost:3000`. -3. Click **Login**. You will be redirected to the Asgardeo login page. +3. Click **Login**. You will be redirected to the WSO2 Identity Platform login page. - {: width="350" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} + {: width="350" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} 4. Enter the credentials of your user account and click **Sign In**. diff --git a/en/asgardeo/docs/get-started/try-samples/ws-federation-webapp.md b/en/asgardeo/docs/get-started/try-samples/ws-federation-webapp.md index 7f2cb949a0..d38b2a563b 100644 --- a/en/asgardeo/docs/get-started/try-samples/ws-federation-webapp.md +++ b/en/asgardeo/docs/get-started/try-samples/ws-federation-webapp.md @@ -27,7 +27,7 @@ To deploy the sample web app on a web container: To configure additional properties for the sample application: 1. Add the following configurations to the `web.xml` file in ` The list of OIDC scopes that are used for requesting user information. You can add OIDC scopes such as
profileand"scope": ["profile", "email"]-Learn more about [OIDC scopes in Asgardeo]({{base_path}}/guides/users/attributes/manage-scopes/).
+Learn more about [OIDC scopes in WSO2 Identity Platform]({{base_path}}/guides/users/attributes/manage-scopes/).
/apache-tomcat- /webapps/PassiveSTSSampleApp/WEB-INF`. - - Specify Asgardeo Passive STS URL as `idpUrl`. + - Specify WSO2 Identity Platform Passive STS URL as `idpUrl`. ``` xml @@ -56,7 +56,7 @@ To configure additional properties for the sample application: 2. Restart the tomcat server. -## Configure the application in Asgardeo +## Configure the application in WSO2 Identity Platform 1. On the {{ product_name }} Console, go to **Applications**. diff --git a/en/asgardeo/docs/get-started/try-your-own-app/index.md b/en/asgardeo/docs/get-started/try-your-own-app/index.md index 2bd36cee96..75c45fe14c 100644 --- a/en/asgardeo/docs/get-started/try-your-own-app/index.md +++ b/en/asgardeo/docs/get-started/try-your-own-app/index.md @@ -4,7 +4,7 @@ template: templates/no-right-sidebar.html Try your own app
-Pick the technology of your application and follow the instructions to enable Asgardeo login.
+Pick the technology of your application and follow the instructions to enable WSO2 Identity Platform login.
diff --git a/en/asgardeo/docs/get-started/try-your-own-app/java-ee-oidc.md b/en/asgardeo/docs/get-started/try-your-own-app/java-ee-oidc.md index 6df1d82c01..bec473151a 100644 --- a/en/asgardeo/docs/get-started/try-your-own-app/java-ee-oidc.md +++ b/en/asgardeo/docs/get-started/try-your-own-app/java-ee-oidc.md @@ -1,11 +1,11 @@ # Integrate OIDC with your Java EE webapp -Follow the steps given below to authenticate users to your Java EE web application deployed on Tomcat using the [Asgardeo Tomcat OIDC Agent](https://github.com/asgardeo/asgardeo-tomcat-oidc-agent) which enables OIDC-based login and logout. +Follow the steps given below to authenticate users to your Java EE web application deployed on Tomcat using the [WSO2 Identity Platform Tomcat OIDC Agent](https://github.com/asgardeo/asgardeo-tomcat-oidc-agent) which enables OIDC-based login and logout. ## Prerequisites - [Download](https://tomcat.apache.org/tomcat-9.0-doc/) Apache Tomcat 9.x or 8.x in your local environment. - [Download](https://maven.apache.org/download.cgi), and [install](https://maven.apache.org/install.html) Apache Maven (3.6.x or higher) as the package manager if you already haven't. -- You need to have an application registered in Asgardeo. If you don't, see the instructions on [registering an OIDC application]({{base_path}}/guides/applications/register-oidc-web-app/). +- You need to have an application registered in WSO2 Identity Platform. If you don't, see the instructions on [registering an OIDC application]({{base_path}}/guides/applications/register-oidc-web-app/). ## Install the SDK @@ -38,7 +38,7 @@ The Agent is hosted at **WSO2 Internal Repository**. To resolve the dependency m ## Initialize the SDK -To initialize the OIDC agent, you need a property file with the configurations such as the Asgardeo endpoints. The Asgardeo OIDC agent reads the configurations from this file. +To initialize the OIDC agent, you need a property file with the configurations such as the WSO2 Identity Platform endpoints. The WSO2 Identity Platform OIDC agent reads the configurations from this file. Create a file named `oidc-sample-app.properties` in the _/src/main/resources_ directory, using the content below. @@ -118,7 +118,7 @@ flow if it does not find an authenticated application session. Add the following snippet to enable logout. -When the user initiates the logout, the local authenticated application session is cleared and the session in Asgardeo +When the user initiates the logout, the local authenticated application session is cleared and the session in WSO2 Identity Platform is terminated. ```html @@ -127,4 +127,4 @@ is terminated. ``` -See the [Asgardeo Tomcat OIDC Agent documentation](https://github.com/asgardeo/asgardeo-tomcat-oidc-agent#how-it-works) for more information on how it works. +See the [WSO2 Identity Platform Tomcat OIDC Agent documentation](https://github.com/asgardeo/asgardeo-tomcat-oidc-agent#how-it-works) for more information on how it works. diff --git a/en/asgardeo/docs/get-started/try-your-own-app/java-ee-saml.md b/en/asgardeo/docs/get-started/try-your-own-app/java-ee-saml.md index d10e1dc279..5282a5a285 100644 --- a/en/asgardeo/docs/get-started/try-your-own-app/java-ee-saml.md +++ b/en/asgardeo/docs/get-started/try-your-own-app/java-ee-saml.md @@ -1,12 +1,12 @@ # Integrate SAML with your Java EE webapp -Follow the steps given below to authenticate users to your Java EE web application deployed on Tomcat using the [Asgardeo Tomcat SAML Agent](https://github.com/asgardeo/asgardeo-tomcat-saml-agent) which enables SAML-based login and logout. +Follow the steps given below to authenticate users to your Java EE web application deployed on Tomcat using the [WSO2 Identity Platform Tomcat SAML Agent](https://github.com/asgardeo/asgardeo-tomcat-saml-agent) which enables SAML-based login and logout. ## Prerequisites - [Download](https://tomcat.apache.org/tomcat-9.0-doc/) Apache Tomcat 9.x or 8.x in your local environment. - [Download](https://maven.apache.org/download.cgi) and [install](https://maven.apache.org/install.html) Apache Maven (3.6.x or higher) as the package manager if you already haven't. -- You need to have an application already registered in Asgardeo. If you don't, see the instructions on [registering a SAML application]({{base_path}}/guides/applications/register-saml-web-app/). +- You need to have an application already registered in WSO2 Identity Platform. If you don't, see the instructions on [registering a SAML application]({{base_path}}/guides/applications/register-saml-web-app/). ## Install the SDK @@ -51,7 +51,7 @@ Follow the steps given below to initialize the SAML agent. ### Create the configuration file -To initialize the SAML agent, you need a property file with the configurations such as the Asgardeo endpoints. The Asgardeo SAML agent reads the configurations from this file. +To initialize the SAML agent, you need a property file with the configurations such as the WSO2 Identity Platform endpoints. The WSO2 Identity Platform SAML agent reads the configurations from this file. Create a file named **sample-app.properties** inside the ** /src/main/resources** directory, using the content below. @@ -60,7 +60,7 @@ Create a file named **sample-app.properties** inside the ** /src/main/r SAML2.AssertionConsumerURL= SAML2.SPEntityId= -#Asgardeo related configs +#WSO2 Identity Platform related configs SAML2.IdPEntityId=accounts.asgardeo.io/t/{organization_nam} SAML2.IdPURL=https://api.asgardeo.io/t/{organization_name}samlsso IdPPublicCert= @@ -87,7 +87,7 @@ PrivateKeyAlias= PrivateKeyPassword= ``` -For advanced use cases such as SAML response signing, the Asgardeo SAML Agent uses a keystore with your private key. If your application doesn't have a keystore already, generate a keystore file and copy it to the ** /src/main/resources** directory. Make sure to update KeyStorePassword, PrivateKeyAlias, and PrivateKeyPassword with relevant values. +For advanced use cases such as SAML response signing, the WSO2 Identity Platform SAML Agent uses a keystore with your private key. If your application doesn't have a keystore already, generate a keystore file and copy it to the ** /src/main/resources** directory. Make sure to update KeyStorePassword, PrivateKeyAlias, and PrivateKeyPassword with relevant values. Find the configuration information below: @@ -105,19 +105,19 @@ Find the configuration information below: SAML2.SPEntityId -This is the unique name of the application used when registering your application with Asgardeo. See [how to register a SAML app manually](../../guides/applications/register-saml-web-app/#register-app-using-manual-configurations) via the Asgardeo Console. +This is the unique name of the application used when registering your application with WSO2 Identity Platform. See [how to register a SAML app manually](../../guides/applications/register-saml-web-app/#register-app-using-manual-configurations) via the WSO2 Identity Platform Console. SAML2.IdPEntityId -This is the issuer of Asgardeo. This is always +accounts.asgardeo.io/t/{organization_name}.This is the issuer of WSO2 Identity Platform. This is always accounts.asgardeo.io/t/{organization_name}.SAML2.IdPURL -This specifies the endpoint of Asgardeo to which login and logout requests should be sent. Note that the organization name should be replaced in the URL with the correct value. +https://api.asgardeo.io/t/{organization_name}/samlsso.This specifies the endpoint of WSO2 Identity Platform to which login and logout requests should be sent. Note that the organization name should be replaced in the URL with the correct value. https://api.asgardeo.io/t/{organization_name}/samlsso.IdPPublicCert -This specifies the public certificate of Asgardeo. You can obtain the public certificate from the Asgardeo Console. See [how to get SAML configurations from the Asgardeo Console.](../../guides/authentication/saml/discover-saml-configs/#discover-saml-configurations-of-asgardeo) +This specifies the public certificate of WSO2 Identity Platform. You can obtain the public certificate from the WSO2 Identity Platform Console. See [how to get SAML configurations from the WSO2 Identity Platform Console.](../../guides/authentication/saml/discover-saml-configs/#discover-saml-configurations-of-asgardeo) EnableSAML2SSOLogin @@ -129,21 +129,21 @@ Find the configuration information below:SAML2.EnableResponseSigning -If this configuration is set to +true, the application validates the signature in the SAML response. If this configuration is set totrue, then [enable response signing from Asgardeo](../../references/app-settings/saml-settings-for-app/#response-signing). - If this configuration is set tofalse, the application does not mandate response signing from Asgardeo.If this configuration is set to true, the application validates the signature in the SAML response. If this configuration is set totrue, then [enable response signing from WSO2 Identity Platform](../../references/app-settings/saml-settings-for-app/#response-signing). + If this configuration is set tofalse, the application does not mandate response signing from WSO2 Identity Platform.SAML2.EnableAssertionSigning -If this configuration is set to +true, the application validates the signature in the SAML assertion. If this configuration is set totrue, then [enable response signing from Asgardeo](../../references/app-settings/saml-settings-for-app/#response-signing). - If this configuration is set tofalse, the application does not mandate response signing from Asgardeo.If this configuration is set to true, the application validates the signature in the SAML assertion. If this configuration is set totrue, then [enable response signing from WSO2 Identity Platform](../../references/app-settings/saml-settings-for-app/#response-signing). + If this configuration is set tofalse, the application does not mandate response signing from WSO2 Identity Platform.SAML2.EnableAssertionEncryption -If this configuration is set to +true,the application expects an encrypted SAML assertion. If this configuration is set totrue, then [enable encryption for SAML assertion](../../references/app-settings/saml-settings-for-app/) from Asgardeo.If this configuration is set to true,the application expects an encrypted SAML assertion. If this configuration is set totrue, then [enable encryption for SAML assertion](../../references/app-settings/saml-settings-for-app/) from WSO2 Identity Platform.SAML2.EnableRequestSigning -If this configuration is set to +true, Asgardeo validates the SAML authentication request and logout request. If this configuration is set totrue, then [enable request signing](../../references/app-settings/saml-settings-for-app/) from Asgardeo.If this configuration is set to true, WSO2 Identity Platform validates the SAML authentication request and logout request. If this configuration is set totrue, then [enable request signing](../../references/app-settings/saml-settings-for-app/) from WSO2 Identity Platform.SAML2.IsPassiveAuthn @@ -224,9 +224,9 @@ When the user clicks the button, the SAML agent intercepts the request and initi ## Add logout -In the previous steps, you implemented login for your app. Now you need a way to log users out of your application and remove the user sessions from Asgardeo. +In the previous steps, you implemented login for your app. Now you need a way to log users out of your application and remove the user sessions from WSO2 Identity Platform. -When the user initiates the logout, the local authenticated application session is cleared and the session in Asgardeo is terminated. +When the user initiates the logout, the local authenticated application session is cleared and the session in WSO2 Identity Platform is terminated. Add the following snippet to enable logout. @@ -236,4 +236,4 @@ Add the following snippet to enable logout. ``` -See the [Asgardeo Tomcat SAML Agent documentation](https://github.com/asgardeo/asgardeo-tomcat-saml-agent#how-it-works) for more information. +See the [WSO2 Identity Platform Tomcat SAML Agent documentation](https://github.com/asgardeo/asgardeo-tomcat-saml-agent#how-it-works) for more information. diff --git a/en/asgardeo/docs/get-started/try-your-own-app/javascript.md b/en/asgardeo/docs/get-started/try-your-own-app/javascript.md index ab2068dca8..9a24d374ed 100644 --- a/en/asgardeo/docs/get-started/try-your-own-app/javascript.md +++ b/en/asgardeo/docs/get-started/try-your-own-app/javascript.md @@ -1,10 +1,10 @@ -# Integrate Asgardeo with your JavaScript SPA +# Integrate WSO2 Identity Platform with your JavaScript SPA -Follow the steps given below to authenticate users to your JavaScript SPA with OpenID Connect using the [Asgardeo JavaScript SDK](https://github.com/asgardeo/asgardeo-auth-spa-sdk/blob/main/README/). +Follow the steps given below to authenticate users to your JavaScript SPA with OpenID Connect using the [WSO2 Identity Platform JavaScript SDK](https://github.com/asgardeo/asgardeo-auth-spa-sdk/blob/main/README/). ## Prerequisites - [Install npm and node](https://www.npmjs.com/get-npm) in your local environment. -- Register an application in Asgardeo. +- Register an application in WSO2 Identity Platform. ## Install the SDK @@ -41,7 +41,7 @@ To initialize the SDK, use the `getInstance()` function in the SDK and provide t- baseUrlThis is the Asgardeo server's host name along with your organization name. +This is the WSO2 Identity Platform server's host name along with your organization name. @@ -231,7 +231,7 @@ You can loop through the user info response(`userinfoResponse`), and get the fol ### Add logout -In the previous steps, you implemented login for your app and enabled your app to get some information about the user that is logged in. Now you need a way to log users out of your application and remove the user sessions from Asgardeo. +In the previous steps, you implemented login for your app and enabled your app to get some information about the user that is logged in. Now you need a way to log users out of your application and remove the user sessions from WSO2 Identity Platform. See the [signOut API reference](https://github.com/asgardeo/asgardeo-auth-spa-sdk#signout) for advanced usages. diff --git a/en/asgardeo/docs/get-started/try-your-own-app/react-native-cli-app-auth.md b/en/asgardeo/docs/get-started/try-your-own-app/react-native-cli-app-auth.md index 04bf314b1e..bed01abc43 100644 --- a/en/asgardeo/docs/get-started/try-your-own-app/react-native-cli-app-auth.md +++ b/en/asgardeo/docs/get-started/try-your-own-app/react-native-cli-app-auth.md @@ -1,6 +1,6 @@ -# Integrate Asgardeo with your React Native App CLI +# Integrate WSO2 Identity Platform with your React Native App CLI -The following guide walks you through integrating Asgardeo with your React Native mobile application using the React Native CLI. With {{product_name}}, your app can securely authorize and authenticate users via OAuth 2.0 and OpenID Connect. +The following guide walks you through integrating WSO2 Identity Platform with your React Native mobile application using the React Native CLI. With {{product_name}}, your app can securely authorize and authenticate users via OAuth 2.0 and OpenID Connect. This integration uses the [react-native-app-auth](https://github.com/FormidableLabs/react-native-app-auth){:target="_blank"} library, a production-ready library that handles OAuth 2.0 and OpenID Connect for React Native applications and provides: @@ -28,13 +28,13 @@ Make sure to install the required tools and set up your development environment: - Xcode 12.5 or newer. -## Step 1: Set up your Asgardeo environment +## Step 1: Set up your WSO2 Identity Platform environment -Before integrating Asgardeo with your React Native app, set up the following in your Asgardeo organization: +Before integrating WSO2 Identity Platform with your React Native app, set up the following in your WSO2 Identity Platform organization: -- **Register a mobile application** - Your application must have app-specific credentials to interact with Asgardeo. You can get these credentials by registering an application on the {{product_name}} Console. Follow the guide and [register a mobile application in Asgardeo]({{base_path}}/guides/applications/register-mobile-app/). +- **Register a mobile application** - Your application must have app-specific credentials to interact with WSO2 Identity Platform. You can get these credentials by registering an application on the {{product_name}} Console. Follow the guide and [register a mobile application in WSO2 Identity Platform]({{base_path}}/guides/applications/register-mobile-app/). -- **Create a user** - You also need a user in your Asgardeo organization to log into your application. Follow the guide and [onboard a user]({{base_path}}/guides/users/manage-users/#onboard-users) to your {{product_name}} organization. +- **Create a user** - You also need a user in your WSO2 Identity Platform organization to log into your application. Follow the guide and [onboard a user]({{base_path}}/guides/users/manage-users/#onboard-users) to your {{product_name}} organization. ## Step 2: Create a React Native application @@ -167,7 +167,7 @@ To ensure users are redirected correctly, configure deep linking for both Androi ## Step 5: Create a configuration file -Your React Native app needs to know your Asgardeo organization details to interact with it. Follow the steps below to create a configuration file in your React Native project. +Your React Native app needs to know your WSO2 Identity Platform organization details to interact with it. Follow the steps below to create a configuration file in your React Native project. 1. Create the `src/config.ts` file to store configurations and add the following: (You will define the actual values as environment variables in the next step.) @@ -185,11 +185,11 @@ Your React Native app needs to know your Asgardeo organization details to intera - **issuer** - API endpoint that issues tokens upon request. - **clientId** - The Client ID of your application. - - **redirectUrl** - After successful login, Asgardeo redirects the user to the redirect URL of your app. + - **redirectUrl** - After successful login, WSO2 Identity Platform redirects the user to the redirect URL of your app. - **scopes** - Scopes needed for requesting user information. The `openid` scope is mandatory to get the ID token. You can add other OIDC scopes such as `profile` and `email`. - - **postLogoutRedirectUrl** - After logout, Asgardeo redirects the user to the postLogoutRedirectUrl of your app. + - **postLogoutRedirectUrl** - After logout, WSO2 Identity Platform redirects the user to the postLogoutRedirectUrl of your app. -2. Create a `.env` file in your project root and enter the actual details of your Asgardeo environment: +2. Create a `.env` file in your project root and enter the actual details of your WSO2 Identity Platform environment: ```bash ASGARDEO_ISSUER=https://api.asgardeo.io/t/ signInRedirectURL/oauth2/token @@ -387,7 +387,7 @@ export default App; ## Step 7: Run the application -Now that you have developed the React Native app and integrated it with Asgardeo, you can run it by following the steps below: +Now that you have developed the React Native app and integrated it with WSO2 Identity Platform, you can run it by following the steps below: 1. In React Native projects, the Metro Bundler compiles your JavaScript code and serves it to the app. It also watches for file changes and enables hot reloading during development. Start it with: diff --git a/en/asgardeo/docs/get-started/try-your-own-app/react.md b/en/asgardeo/docs/get-started/try-your-own-app/react.md index 4e07f5cf8a..3994f630b9 100755 --- a/en/asgardeo/docs/get-started/try-your-own-app/react.md +++ b/en/asgardeo/docs/get-started/try-your-own-app/react.md @@ -1,16 +1,16 @@ -# Integrate Asgardeo with your React SPA +# Integrate WSO2 Identity Platform with your React SPA -Follow the steps given below to authenticate users to your React SPA with OpenID Connect using the [Asgardeo React SDK](https://github.com/asgardeo/asgardeo-auth-react-sdk/blob/main/README.md). +Follow the steps given below to authenticate users to your React SPA with OpenID Connect using the [WSO2 Identity Platform React SDK](https://github.com/asgardeo/asgardeo-auth-react-sdk/blob/main/README.md). ## Prerequisites - [Install node.js and npm](https://nodejs.org) in your local environment. -- [Register an application]({{base_path}}/guides/applications/register-single-page-app/) in Asgardeo. +- [Register an application]({{base_path}}/guides/applications/register-single-page-app/) in WSO2 Identity Platform. !!! note In the tutorial, - your organization name is referred to as `{org_name}`. - - `{client_id}` refers to the client credential that you obtain once you register your application in Asgardeo. + - `{client_id}` refers to the client credential that you obtain once you register your application in WSO2 Identity Platform. ## Install the SDK @@ -23,7 +23,7 @@ npm install @asgardeo/auth-react ## Configure the SDK SDK uses the [React Context API](https://react.dev/learn/passing-data-deeply-with-context) under the hood to share the data between components. -You can easily integrate Asgardeo in your application by using `AuthProvider` as the wrapper element to inject configurations. +You can easily integrate WSO2 Identity Platform in your application by using `AuthProvider` as the wrapper element to inject configurations. `AuthProvider` will provide the session state which contains information such as the authenticated user's display name, email address etc. as well as the methods required to implement authentication in the React app. @@ -68,7 +68,7 @@ Details of the parameters are given below. - baseUrlThis is the Asgardeo server's host name along with your organization name. +This is the WSO2 Identity Platform server's host name along with your organization name. @@ -105,9 +105,9 @@ Few common methods that you can access with `useAuthContext()` are listed below. - `state` object - This will contain attributes such as whether a user is currently logged in, the username of the currently logged-in user etc. -- `signIn` - Initiate a login request to Asgardeo, process the response to obtain authentication response. +- `signIn` - Initiate a login request to WSO2 Identity Platform, process the response to obtain authentication response. -- `signOut` - Logout the user from Asgardeo and clear any authentication data from the SDK storage. +- `signOut` - Logout the user from WSO2 Identity Platform and clear any authentication data from the SDK storage. - `isAuthenticated` - Check whether there is an authenticated user session. Based on the result you can decide to change the application view/behaviour. @@ -144,21 +144,21 @@ The `state` object contains attributes of a user. Its structure is as follows. } ``` !!! note - The `isAuthenticated` attribute checks whether a user is currently logged in via Asgardeo or not. + The `isAuthenticated` attribute checks whether a user is currently logged in via WSO2 Identity Platform or not. ### Add login to your application -You can use the `useAuthContext` hook from the Asgardeo React SDK to easily authenticate your React application. +You can use the `useAuthContext` hook from the WSO2 Identity Platform React SDK to easily authenticate your React application. Implement a login button as follows using the `signIn()` function in the `useAuthContext` hook. ```js ``` -Clicking on the **Login** button will take the user to the Asgardeo login page. Once `signIn()` succeeds, the user will be redirected to the app (based on the `signInRedirectURL` specified in the [AuthProvider configuration](#configure-the-sdk)) and the `state.isAuthenticated` will be set to `true`. +Clicking on the **Login** button will take the user to the WSO2 Identity Platform login page. Once `signIn()` succeeds, the user will be redirected to the app (based on the `signInRedirectURL` specified in the [AuthProvider configuration](#configure-the-sdk)) and the `state.isAuthenticated` will be set to `true`. ### Get access token -Once the user is logged in with Asgardeo, the application can get the access token issued by Asgardeo. +Once the user is logged in with WSO2 Identity Platform, the application can get the access token issued by WSO2 Identity Platform. See the [SDK reference](https://github.com/asgardeo/asgardeo-auth-react-sdk/blob/main/API.md#getaccesstoken) for more information. @@ -212,11 +212,11 @@ getBasicUserInfo().then((basicUserDetails) => { } ``` -You can get additional information from the user by [requesting user information from Asgardeo using scopes]({{base_path}}/guides/users/attributes/manage-scopes/#use-scopes-to-request-attributes) +You can get additional information from the user by [requesting user information from WSO2 Identity Platform using scopes]({{base_path}}/guides/users/attributes/manage-scopes/#use-scopes-to-request-attributes) ### Get decoded ID token -Once the user is logged in with Asgardeo, the application can get the ID token issued by Asgardeo. +Once the user is logged in with WSO2 Identity Platform, the application can get the ID token issued by WSO2 Identity Platform. The SDK provides the `getDecodedIDToken()` API to get the decoded token. You can use this decoded token to obtain user claims as below. @@ -290,4 +290,4 @@ If your application needs routing, you can use any router of your choice. You ca ## More Information -If you want to learn in-depth about the Asgardeo React SDK, you can refer to the [Asgardeo React SDK documentation](https://github.com/asgardeo/asgardeo-auth-react-sdk#readme). +If you want to learn in-depth about the WSO2 Identity Platform React SDK, you can refer to the [WSO2 Identity Platform React SDK documentation](https://github.com/asgardeo/asgardeo-auth-react-sdk#readme). diff --git a/en/asgardeo/docs/guides/account-configurations/account-disabling.md b/en/asgardeo/docs/guides/account-configurations/account-disabling.md index 6c51f17c6f..0f761d116a 100644 --- a/en/asgardeo/docs/guides/account-configurations/account-disabling.md +++ b/en/asgardeo/docs/guides/account-configurations/account-disabling.md @@ -1,3 +1,3 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/account-configurations/account-disabling.md" %} diff --git a/en/asgardeo/docs/guides/account-configurations/account-login/configure-login-identifiers.md b/en/asgardeo/docs/guides/account-configurations/account-login/configure-login-identifiers.md index 3fc8029d84..cdb7601b67 100644 --- a/en/asgardeo/docs/guides/account-configurations/account-login/configure-login-identifiers.md +++ b/en/asgardeo/docs/guides/account-configurations/account-login/configure-login-identifiers.md @@ -3,19 +3,19 @@ !!! note The feature is in the Beta stage. We are working on adding more capabilities for this feature. -You can now configure alternative login identifiers so that the users of your Asgardeo organization have the capability to use these identifiers to log in. +You can now configure alternative login identifiers so that the users of your WSO2 Identity Platform organization have the capability to use these identifiers to log in. !!! note The primary login identifier is the attribute you configure as your username. Learn more about [configuring username validation]({{base_path}}/guides/user-accounts/account-login/username-validation/). -Asgardeo allows admins to assign the following attributes as alternative login identifiers of the organization: +WSO2 Identity Platform allows admins to assign the following attributes as alternative login identifiers of the organization: - `Email` - `Mobile` To configure alternative login identifiers for your organization: -1. On the Asgardeo Console, go to **Login & Registration**. +1. On the WSO2 Identity Platform Console, go to **Login & Registration**. 2. Under **Login Identifier**, click on **Alternative Login Identifier**. @@ -24,7 +24,7 @@ To configure alternative login identifiers for your organization: {: width="700" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} !!! note - - Ensure that every user within your organization has a unique value assigned to the chosen login identifiers. For new users, Asgardeo will ensure it's uniqueness. + - Ensure that every user within your organization has a unique value assigned to the chosen login identifiers. For new users, WSO2 Identity Platform will ensure it's uniqueness. - If you have chosen `Email` as the [username type]({{base_path}}/guides/user-accounts/account-login/username-validation/), it automatically becomes the primary login identifier. Therefore, configuring it as an alternative login identifier will be disabled. diff --git a/en/asgardeo/docs/guides/account-configurations/account-login/username-validation.md b/en/asgardeo/docs/guides/account-configurations/account-login/username-validation.md index 2916e35c7b..15b0453fb1 100644 --- a/en/asgardeo/docs/guides/account-configurations/account-login/username-validation.md +++ b/en/asgardeo/docs/guides/account-configurations/account-login/username-validation.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../../includes/guides/user-accounts/account-login/username-validation.md" %} diff --git a/en/asgardeo/docs/guides/agentic-ai/mcp/register-mcp-client-app.md b/en/asgardeo/docs/guides/agentic-ai/mcp/register-mcp-client-app.md index 1879630231..a4ab30f88a 100644 --- a/en/asgardeo/docs/guides/agentic-ai/mcp/register-mcp-client-app.md +++ b/en/asgardeo/docs/guides/agentic-ai/mcp/register-mcp-client-app.md @@ -1,3 +1,3 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../../includes/guides/applications/register-mcp-client-app.md" %} diff --git a/en/asgardeo/docs/guides/api-security/aws/securing-aws-http-apis.md b/en/asgardeo/docs/guides/api-security/aws/securing-aws-http-apis.md index 225cad71c5..52bef6d04b 100644 --- a/en/asgardeo/docs/guides/api-security/aws/securing-aws-http-apis.md +++ b/en/asgardeo/docs/guides/api-security/aws/securing-aws-http-apis.md @@ -1,16 +1,16 @@ --- template: templates/quick-start.html -heading: Securing APIs with AWS API Gateway and Asgardeo -description: This guide walks you through securing a Pharmacy User API using AWS API Gateway and Asgardeo. You'll deploy a Lambda function, expose it via an HTTP API, and secure the endpoint using JWT tokens issued by Asgardeo and validated by API Gateway. +heading: Securing APIs with AWS API Gateway and WSO2 Identity Platform +description: This guide walks you through securing a Pharmacy User API using AWS API Gateway and WSO2 Identity Platform. You'll deploy a Lambda function, expose it via an HTTP API, and secure the endpoint using JWT tokens issued by WSO2 Identity Platform and validated by API Gateway. what_you_will_learn: - Deploy a serverless endpoint using AWS Lambda - Secure your API with AWS API Gateway’s JWT authorizer - - Configure an OAuth2 application and define API scopes in Asgardeo + - Configure an OAuth2 application and define API scopes in WSO2 Identity Platform - Protect and test your API using JWT-based access control prerequisites: - About 20 minutes - AWS Account with CLI access - - An Asgardeo account + - An WSO2 Identity Platform account - Tools: signInRedirectURLcurlandjq- Familiarity with shell and JSON --- @@ -142,13 +142,13 @@ aws apigatewayv2 create-stage --api-id $API_ID --stage-name dev --auto-deploy echo "API deployed to stage 'dev'" ``` -## Step 3: Configure Asgardeo to Secure the API +## Step 3: Configure WSO2 Identity Platform to Secure the API -In this step, you'll set up everything needed in Asgardeo to secure your Pharmacy User API. This includes getting a bearer token, registering the API as a protected resource, creating an OAuth2 application, linking the app to the API, and configuring role handling. +In this step, you'll set up everything needed in WSO2 Identity Platform to secure your Pharmacy User API. This includes getting a bearer token, registering the API as a protected resource, creating an OAuth2 application, linking the app to the API, and configuring role handling. -### 1. Obtain a Bearer Token for Asgardeo Manage App +### 1. Obtain a Bearer Token for WSO2 Identity Platform Manage App -You will need a Client ID and Client Secret from an Asgardeo application that is authorized to invoke Asgardeo management APIs. You can use an existing application or create a new application in the Asgardeo console with the Client Credentials grant enabled. Make sure the application has the scope `internal_application_mgt_create` (this scope is required to create a new application via the API). +You will need a Client ID and Client Secret from an WSO2 Identity Platform application that is authorized to invoke WSO2 Identity Platform management APIs. You can use an existing application or create a new application in the WSO2 Identity Platform console with the Client Credentials grant enabled. Make sure the application has the scope `internal_application_mgt_create` (this scope is required to create a new application via the API). ```bash curl -X POST "https://api.asgardeo.io/t//oauth2/token" \ @@ -156,15 +156,15 @@ curl -X POST "https://api.asgardeo.io/t/ /oauth2/token" \ -H "Content-Type: application/x-www-form-urlencoded" \ -d "grant_type=client_credentials&scope=internal_application_mgt_create" 2>/dev/null | jq -r .access_token ``` -Use the obtained token in all subsequent Asgardeo API calls: +Use the obtained token in all subsequent WSO2 Identity Platform API calls: ```bash -H "Authorization: Bearer $ACCESS_TOKEN" ``` -### 2. Register the API Resource in Asgardeo +### 2. Register the API Resource in WSO2 Identity Platform -In this step, you’ll register the Pharmacy User API as a protected resource in Asgardeo. This allows you to define access scopes that control which operations clients can perform on the API. +In this step, you’ll register the Pharmacy User API as a protected resource in WSO2 Identity Platform. This allows you to define access scopes that control which operations clients can perform on the API. ```bash curl -X POST "https://api.asgardeo.io/t/ /api/server/v1/api-resources" \ @@ -183,9 +183,9 @@ curl -X POST "https://api.asgardeo.io/t/ /api/server/v1/api-resources" }' ``` -### 3. Register an OAuth2 Application in Asgardeo +### 3. Register an OAuth2 Application in WSO2 Identity Platform -Create an application in Asgardeo that will request access tokens to call your API. This app represents the client, and you’ll configure it to use the Client Credentials grant type with JWT access tokens. +Create an application in WSO2 Identity Platform that will request access tokens to call your API. This app represents the client, and you’ll configure it to use the Client Credentials grant type with JWT access tokens. ```bash curl -X POST "https://api.asgardeo.io/t/ /api/server/v1/applications" \ @@ -235,7 +235,7 @@ curl -X PATCH "https://api.asgardeo.io/t/ /api/server/v1/applications/< ## Step 4: Secure the API Route with JWT Authorizer -In this step, you’ll configure API Gateway to validate JWT tokens issued by Asgardeo. This includes creating a JWT authorizer, attaching it to the /user route, and deploying the changes. +In this step, you’ll configure API Gateway to validate JWT tokens issued by WSO2 Identity Platform. This includes creating a JWT authorizer, attaching it to the /user route, and deploying the changes. ### 1. Configure JWT Authorizer @@ -276,11 +276,11 @@ aws apigatewayv2 create-stage \ ## Step 5: Try Out the Secured API -In this step, you’ll verify that the Pharmacy User API only allows access when a valid JWT with the correct scope is provided. The required scope in this setup is get_pharmacy_user, and it must be included in the access token issued by Asgardeo. +In this step, you’ll verify that the Pharmacy User API only allows access when a valid JWT with the correct scope is provided. The required scope in this setup is get_pharmacy_user, and it must be included in the access token issued by WSO2 Identity Platform. -### 1. Create a User in Asgardeo +### 1. Create a User in WSO2 Identity Platform -Create a user in Asgardeo to simulate a real-world client accessing the API. +Create a user in WSO2 Identity Platform to simulate a real-world client accessing the API. ```bash curl -X POST "https://api.asgardeo.io/t/ /scim2/Users" \ @@ -324,4 +324,4 @@ You should receive a 200 OK response. { "message": "Welcome User!" } ``` -Your Pharmacy User API is now secured with JWT authorization via Asgardeo +Your Pharmacy User API is now secured with JWT authorization via WSO2 Identity Platform diff --git a/en/asgardeo/docs/guides/applications/register-mobile-app.md b/en/asgardeo/docs/guides/applications/register-mobile-app.md index ab0ebe865e..f08b1106d1 100644 --- a/en/asgardeo/docs/guides/applications/register-mobile-app.md +++ b/en/asgardeo/docs/guides/applications/register-mobile-app.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/applications/register-mobile-app.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/applications/register-nextjs-app.md b/en/asgardeo/docs/guides/applications/register-nextjs-app.md index da0761edf7..4856a7bb75 100644 --- a/en/asgardeo/docs/guides/applications/register-nextjs-app.md +++ b/en/asgardeo/docs/guides/applications/register-nextjs-app.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set technology = "Next.js" %} {% set technology_quickstart = "nextjs" %} diff --git a/en/asgardeo/docs/guides/applications/register-oidc-web-app.md b/en/asgardeo/docs/guides/applications/register-oidc-web-app.md index 1f3f6c19cd..7b29562502 100644 --- a/en/asgardeo/docs/guides/applications/register-oidc-web-app.md +++ b/en/asgardeo/docs/guides/applications/register-oidc-web-app.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/applications/register-oidc-web-app.md" %} diff --git a/en/asgardeo/docs/guides/applications/register-react-app.md b/en/asgardeo/docs/guides/applications/register-react-app.md index 3968a4056e..afceddadb3 100644 --- a/en/asgardeo/docs/guides/applications/register-react-app.md +++ b/en/asgardeo/docs/guides/applications/register-react-app.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set technology = "React" %} {% set technology_quickstart = "react" %} diff --git a/en/asgardeo/docs/guides/applications/register-saml-web-app.md b/en/asgardeo/docs/guides/applications/register-saml-web-app.md index faf04db1a9..2c32567917 100644 --- a/en/asgardeo/docs/guides/applications/register-saml-web-app.md +++ b/en/asgardeo/docs/guides/applications/register-saml-web-app.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/applications/register-saml-web-app.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/applications/register-single-page-app.md b/en/asgardeo/docs/guides/applications/register-single-page-app.md index 8c95203051..e958699617 100644 --- a/en/asgardeo/docs/guides/applications/register-single-page-app.md +++ b/en/asgardeo/docs/guides/applications/register-single-page-app.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/applications/register-single-page-app.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/applications/register-standard-based-app.md b/en/asgardeo/docs/guides/applications/register-standard-based-app.md index 95449fe1d6..4add90a2c6 100644 --- a/en/asgardeo/docs/guides/applications/register-standard-based-app.md +++ b/en/asgardeo/docs/guides/applications/register-standard-based-app.md @@ -1,3 +1,3 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set api_authentication_path = "authentication" %} {% include "../../../../includes/guides/applications/register-standard-based-app.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/asgardeo-logs/audit-logs/audit-log-catalog.md b/en/asgardeo/docs/guides/asgardeo-logs/audit-logs/audit-log-catalog.md index 1d79fb4854..d9ff6dd8e0 100644 --- a/en/asgardeo/docs/guides/asgardeo-logs/audit-logs/audit-log-catalog.md +++ b/en/asgardeo/docs/guides/asgardeo-logs/audit-logs/audit-log-catalog.md @@ -1,6 +1,6 @@ # Audit log catalog -The audit log catalog provides detailed information about all audit log action keys used in Asgardeo. This guide helps you understand the structure and content of each audit log type along with sample audit logs for reference. +The audit log catalog provides detailed information about all audit log action keys used in WSO2 Identity Platform. This guide helps you understand the structure and content of each audit log type along with sample audit logs for reference. ## Action management diff --git a/en/asgardeo/docs/guides/asgardeo-logs/audit-logs/index.md b/en/asgardeo/docs/guides/asgardeo-logs/audit-logs/index.md index 27ad021113..4caabcb05f 100644 --- a/en/asgardeo/docs/guides/asgardeo-logs/audit-logs/index.md +++ b/en/asgardeo/docs/guides/asgardeo-logs/audit-logs/index.md @@ -1,6 +1,6 @@ # Audit logs -Audit logs in Asgardeo are designed for developers to access and analyze vital state changes that happen to resources in Asgardeo. These logs are important for enhancing system security as they proactively identify suspicious activities and potential security threats. +Audit logs in WSO2 Identity Platform are designed for developers to access and analyze vital state changes that happen to resources in WSO2 Identity Platform. These logs are important for enhancing system security as they proactively identify suspicious activities and potential security threats. In the event of incidents or errors, audit logs serve as a valuable forensic tool, facilitating the investigation process by providing detailed insights into the sequence of events and identifying the responsible parties. @@ -10,7 +10,7 @@ This guide provides instructions on how to access and analyze audit logs to moni To access audit logs: -1. On the Asgardeo Console, go to **Log** +1. On the WSO2 Identity Platform Console, go to **Log** 2. Switch to the **Audit** tab. @@ -28,7 +28,7 @@ For example, the diagram below shows the results for a search filtered with the ## Structure of an audit log -When you expand an audit log in Asgardeo by clicking on it, you will get the following view. +When you expand an audit log in WSO2 Identity Platform by clicking on it, you will get the following view. {: width="600" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} @@ -65,7 +65,7 @@ The following are the properties of an audit log: - targetTypeThe type of the target resource, such as +userorapplication.
Note that Asgardeo currently publishes audit logs for thetargetTypes: User, Group, Role, ApplicationThe type of the target resource, such as userorapplication.
Note that WSO2 Identity Platform currently publishes audit logs for thetargetTypes: User, Group, Role, Application@@ -85,9 +85,9 @@ The following are the properties of an audit log: Follow the steps below to observe an audit log due to user onboarding: -1. Onboard a user to Asgardeo. +1. Onboard a user to WSO2 Identity Platform. -2. On the Asgardeo Console, go to **Logs**. +2. On the WSO2 Identity Platform Console, go to **Logs**. 3. Switch to the **Audit** tab, expand the latest with the `add-user` tag, and observe the following audit log. diff --git a/en/asgardeo/docs/guides/asgardeo-logs/diagnostic-logs.md b/en/asgardeo/docs/guides/asgardeo-logs/diagnostic-logs.md index 3ae8b7aa4a..b46f92b333 100644 --- a/en/asgardeo/docs/guides/asgardeo-logs/diagnostic-logs.md +++ b/en/asgardeo/docs/guides/asgardeo-logs/diagnostic-logs.md @@ -1,16 +1,16 @@ # Diagnostic logs -Diagnostic logs in Asgardeo are designed to help developers diagnose and troubleshoot issues that occur when using Asgardeo features such as onboarding applications, and configuring authentication flows. Furthermore, support engineers can also use logs to troubleshoot user issues. +Diagnostic logs in WSO2 Identity Platform are designed to help developers diagnose and troubleshoot issues that occur when using WSO2 Identity Platform features such as onboarding applications, and configuring authentication flows. Furthermore, support engineers can also use logs to troubleshoot user issues. ## Access diagnostic logs To access diagnostics logs: -1. On the Asgardeo Console, go to **Log** +1. On the WSO2 Identity Platform Console, go to **Log** 2. Switch to the **Diagnostic** tab. - {: width="600" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} + {: width="600" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} By default, the console displays logs that occurred in the last 15 minutes. @@ -20,11 +20,11 @@ You can use the search bar to search for logs based on the Trace ID, Action ID, For example, the diagram below shows the results for a search based on the Result Message. -{: width="600" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} +{: width="600" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} ## Add custom logs to authentication scripts -In addition to the logs generated by Asgardeo, organization administrators can define their own logs when [setting up conditional authentication]({{base_path}}/guides/authentication/conditional-auth/) scripts. This is helpful when you need additional information to troubleshoot an application issue. +In addition to the logs generated by WSO2 Identity Platform, organization administrators can define their own logs when [setting up conditional authentication]({{base_path}}/guides/authentication/conditional-auth/) scripts. This is helpful when you need additional information to troubleshoot an application issue. !!! note Custom logs are marked by the **** icon in the logs portal. @@ -119,7 +119,7 @@ Conditional authentication scripts can generate two types of error logs in the l ## Structure of logs -The following table explains some of the common properties found in Asgardeo logs. +The following table explains some of the common properties found in WSO2 Identity Platform logs. actionId@@ -168,25 +168,25 @@ The following table explains some of the common properties found in Asgardeo log ## Sample scenarios -The following scenarios describe how you can use logs to troubleshoot some common issues that occur when using Asgardeo. +The following scenarios describe how you can use logs to troubleshoot some common issues that occur when using WSO2 Identity Platform. ### Application onboarding Follow the steps below to observe an application error log due to incorrect client credentials. -1. [Onboard an application]({{base_path}}/get-started/start-integrating-apps/) to Asgardeo but provide incorrect client credentials when configuring the application. +1. [Onboard an application]({{base_path}}/get-started/start-integrating-apps/) to WSO2 Identity Platform but provide incorrect client credentials when configuring the application. 2. Attempt to log in to the application with a user account. An error will occur in the application. -3. Go to the logs portal on the Asgardeo Console and observe the following error log. +3. Go to the logs portal on the WSO2 Identity Platform Console and observe the following error log. - {: width="600" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} + {: width="600" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} ### Conditional authentication Follow the steps below to observe an application error log due to not meeting the conditions of an authentication script. -1. [Onboard an application]({{base_path}}/get-started/start-integrating-apps/) to Asgardeo. +1. [Onboard an application]({{base_path}}/get-started/start-integrating-apps/) to WSO2 Identity Platform. 2. Restrict login to anyone outside the `employee` group using [group-based access control]({{base_path}}/guides/authentication/conditional-auth/group-based-template-access-control/). @@ -194,6 +194,6 @@ Follow the steps below to observe an application error log due to not meeting th 4. Log in to the application with a user account not belonging to the
@@ -200,13 +200,13 @@ As mentioned earlier, it's a best practice for mobile applications to use OpenID 3. After implementing the logic described above, set the `AuthorizeListener` as the `OnClickListener` for your sign-in button. !!! note - This triggers an authorization request to Asgardeo when the sign-in button is clicked, and the Asgardeo login page opens on your browser. + This triggers an authorization request to WSO2 Identity Platform when the sign-in button is clicked, and the WSO2 Identity Platform login page opens on your browser. -4. To log in, use your Asgardeo credentials. +4. To log in, use your WSO2 Identity Platform credentials. !!! note - As mentioned in the code snippets above, if the authorization is successful, you are redirected to the `UserInfoActivity`. If it fails, you are redirected to `MainActivity`. - - Once the authorization flow is successful, an authorization code is sent to the application via browser redirection. The application must then send the authorization code and additional information to Asgardeo to get the access token and ID token. + - Once the authorization flow is successful, an authorization code is sent to the application via browser redirection. The application must then send the authorization code and additional information to WSO2 Identity Platform to get the access token and ID token. 5. To retrieve the access token in the `UserInfoActivity` class of your application, add the following code. @@ -253,7 +253,7 @@ As mentioned earlier, it's a best practice for mobile applications to use OpenID After receiving the access token, you can use it to authenticate and call the user info endpoint. This retrieves the requested user details. In this scenario, since we only requested the `profile` scope with the username, the user info endpoint contains the username. !!! note - You can find the UserInfo endpoint in the **Info** tab of the application you created in Asgardeo. + You can find the UserInfo endpoint in the **Info** tab of the application you created in WSO2 Identity Platform. ```java String userinfoEndpoint = ConfigManager. @@ -299,12 +299,12 @@ public class LogoutListener implements Button.OnClickListener { } ``` -When the user clicks the logout button, the application sends a logout request to the Asgardeo logout endpoint. +When the user clicks the logout button, the application sends a logout request to the WSO2 Identity Platform logout endpoint. !!! note - You can find the logout endpoint in the **Info** tab of the application you created in Asgardeo. + You can find the logout endpoint in the **Info** tab of the application you created in WSO2 Identity Platform. -As a result, the user will be logged out from Asgardeo and redirected to the default logout page. If you want to redirect the user to a different page, you can include the `post_logout_redirect_uri` parameter in the logout request. +As a result, the user will be logged out from WSO2 Identity Platform and redirected to the default logout page. If you want to redirect the user to a different page, you can include the `post_logout_redirect_uri` parameter in the logout request. Once the logout is successful, the user is redirected to the URL specified in the `post_logout_redirect_uri` parameter. @@ -320,13 +320,13 @@ Let's walk through the end-to-end flow of the application we built in this tutor 2. Click **Sign In** to start the authentication process. - You are redirected to Asgardeo's login page, where you enter valid user credentials. + You are redirected to WSO2 Identity Platform's login page, where you enter valid user credentials. {: width="300" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} -3. Use the credentials of the user you created on Asgardeo. +3. Use the credentials of the user you created on WSO2 Identity Platform. - Upon the first login attempt, Asgardeo prompts for consent to share the configured attributes with the Android application. + Upon the first login attempt, WSO2 Identity Platform prompts for consent to share the configured attributes with the Android application. {: width="300" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} @@ -342,6 +342,6 @@ Let's walk through the end-to-end flow of the application we built in this tutor ## Summary -In this tutorial, we covered the steps to add authentication to an Android application using Asgardeo as the CIAM provider. The AppAuth SDK was used for integrating the authentication and authorization capabilities. We also looked at the configurations required on the Asgardeo side for the application. +In this tutorial, we covered the steps to add authentication to an Android application using WSO2 Identity Platform as the CIAM provider. The AppAuth SDK was used for integrating the authentication and authorization capabilities. We also looked at the configurations required on the WSO2 Identity Platform side for the application. -Starting with a basic Android application without user authentication, we modified the code to successfully integrate the login, logout, and user info retrieval methods with Asgardeo. You can access the [completed source code](https://github.com/asgardeo-samples/asgardeo-android-samples/tree/main/MealMagicAndroidApp) of the application. \ No newline at end of file +Starting with a basic Android application without user authentication, we modified the code to successfully integrate the login, logout, and user info retrieval methods with WSO2 Identity Platform. You can access the [completed source code](https://github.com/asgardeo-samples/asgardeo-android-samples/tree/main/MealMagicAndroidApp) of the application. \ No newline at end of file diff --git a/en/asgardeo/docs/tutorials/auth-users-into-flutter-apps.md b/en/asgardeo/docs/tutorials/auth-users-into-flutter-apps.md index 452f9f314a..47ed4c388d 100644 --- a/en/asgardeo/docs/tutorials/auth-users-into-flutter-apps.md +++ b/en/asgardeo/docs/tutorials/auth-users-into-flutter-apps.md @@ -1,4 +1,4 @@ -# Authenticate users into Flutter applications using Asgardeo +# Authenticate users into Flutter applications using WSO2 Identity Platform Flutter, introduced by Google, is an open-source software development kit (SDK) that enables developers to create high-quality and high-performance cross-platform applications for mobile, web, desktop, and embedded apps with a single codebase. @@ -14,11 +14,11 @@ If you choose the first option of handling user registration and login within th To avoid these challenges, it is recommended to use an identity provider to handle user registration and authentication. This means that all user identities are managed by the identity provider and that the login data is recorded. In cases of harmful activity, it will be easier to identify who was online and what they did, which makes problem-solving and threat elimination easier. -Asgardeo, a SaaS-based customer identity and access management (CIAM) solution, is a suitable identity provider for Flutter applications. +WSO2 Identity Platform, a SaaS-based customer identity and access management (CIAM) solution, is a suitable identity provider for Flutter applications. ## Overview -This tutorial guides you through the process of integrating user authentication capabilities into a Flutter application using Asgardeo. As Flutter supports multiple platforms with a single codebase, let's focus on developing for the iOS platform. +This tutorial guides you through the process of integrating user authentication capabilities into a Flutter application using WSO2 Identity Platform. As Flutter supports multiple platforms with a single codebase, let's focus on developing for the iOS platform. For detailed instructions on platform-specific development, see Flutter's [installation guide](https://docs.flutter.dev/get-started/install). @@ -27,20 +27,20 @@ For detailed instructions on platform-specific development, see Flutter's [insta The following steps explain the high-level authentication flow: 1. The user clicks the login button of a Flutter application. -2. The user is directed to the Asgardeo (CIAM provider) login page. -3. The user enters their Asgardeo account credentials. -4. The user is authenticated via Asgardeo, and upon successful login, they are redirected to the application's home page. -5. If the user clicks the logout button of the application, they are logged out from Asgardeo and redirected to the relevant page. +2. The user is directed to the WSO2 Identity Platform (CIAM provider) login page. +3. The user enters their WSO2 Identity Platform account credentials. +4. The user is authenticated via WSO2 Identity Platform, and upon successful login, they are redirected to the application's home page. +5. If the user clicks the logout button of the application, they are logged out from WSO2 Identity Platform and redirected to the relevant page. ### OIDC authentication method -The Flutter application integrates with Asgardeo using the [OIDC](https://openid.net/connect/) protocol, which is a standard way of supporting secure authentication and identity and access management. OIDC supports several grant types, and here the [Authorization Code flow]({{base_path}}/guides/authentication/oidc/implement-auth-code/) is used. +The Flutter application integrates with WSO2 Identity Platform using the [OIDC](https://openid.net/connect/) protocol, which is a standard way of supporting secure authentication and identity and access management. OIDC supports several grant types, and here the [Authorization Code flow]({{base_path}}/guides/authentication/oidc/implement-auth-code/) is used. ### SDKs In the world of software development, an SDK (Software Development Kit) is an essential set of software tools and programs that enable developers to create applications for specific platforms, operating systems, computer systems, or devices. -When integrating Asgardeo with your mobile application, you can use any third-party OIDC SDK that supports the protocol. For this tutorial, let's use the [flutter_appauth](https://pub.dev/packages/flutter_appauth) SDK. With this SDK, you can easily add OIDC-based login and logout capabilities to your Flutter applications. +When integrating WSO2 Identity Platform with your mobile application, you can use any third-party OIDC SDK that supports the protocol. For this tutorial, let's use the [flutter_appauth](https://pub.dev/packages/flutter_appauth) SDK. With this SDK, you can easily add OIDC-based login and logout capabilities to your Flutter applications. ## Prerequisites @@ -62,23 +62,23 @@ Be sure that the following prerequisites are fulfilled. Clone [this repository](https://github.com/asgardeo-samples/asgardeo-flutter-samples/tree/main/asgardeo-flutter-integration-demo) to get the sample application. At this initial stage, the application contains sign-in, view profile, and sign-out options that let you navigate the pages. User authentication is not implemented yet. Furthermore, all profile information is hard coded at the application level. -In this tutorial, we will walk you through the process of adding authentication capabilities to the application using Asgardeo as the CIAM provider. You will also learn how to retrieve and display the profile information of an authenticated user. +In this tutorial, we will walk you through the process of adding authentication capabilities to the application using WSO2 Identity Platform as the CIAM provider. You will also learn how to retrieve and display the profile information of an authenticated user. -## Step 2: Register your application in Asgardeo +## Step 2: Register your application in WSO2 Identity Platform -To integrate Asgardeo as your CIAM provider, you need to register your application as a Mobile Application in Asgardeo. Since you have chosen iOS as your development platform, you will register it as a mobile application. See the instructions on [registering a mobile application]({{base_path}}/guides/applications/register-mobile-app/). +To integrate WSO2 Identity Platform as your CIAM provider, you need to register your application as a Mobile Application in WSO2 Identity Platform. Since you have chosen iOS as your development platform, you will register it as a mobile application. See the instructions on [registering a mobile application]({{base_path}}/guides/applications/register-mobile-app/). !!! note When registering the mobile application, be sure to add `wso2.asgardeo.sampleflutterapp://login-callback` as the authorized redirect URI. This is the same callback URL you will add when setting up the application. -After registering your application with Asgardeo, you can enable [user attributes for the app]({{base_path}}/guides/authentication/user-attributes/enable-attributes-for-oidc-app/). These attributes correspond to the user's profile information that can be retrieved by the application with the user's consent. +After registering your application with WSO2 Identity Platform, you can enable [user attributes for the app]({{base_path}}/guides/authentication/user-attributes/enable-attributes-for-oidc-app/). These attributes correspond to the user's profile information that can be retrieved by the application with the user's consent. !!! note If you need additional attributes that are not listed in the user's profile section by default, you can [configure new attributes]({{base_path}}/guides/users/attributes/manage-attributes/) and retrieve them through the `profile` scope. In this tutorial, you will retrieve the First Name, Last Name, Mobile, Country, Birth Date, and Photo URL as profile information. -Note that admin users are not allowed to log in to the Android application. Therefore, it is necessary to create a business user in Asgardeo. See the instructions on [managing users in Asgardeo]({{base_path}}/guides/users/manage-users/#onboard-a-user). +Note that admin users are not allowed to log in to the Android application. Therefore, it is necessary to create a business user in WSO2 Identity Platform. See the instructions on [managing users in WSO2 Identity Platform]({{base_path}}/guides/users/manage-users/#onboard-a-user). ## Step 3: Install dependencies @@ -86,11 +86,11 @@ Let's start the integration by adding the required dependencies: - [flutter_appauth](https://pub.dev/packages/flutter_appauth) - A wrapper package around [AppAuth](https://appauth.io/) that provides functionalities for the authentication and authorization of users. This dependency will be used to communicate with Asgardeo to perform user authentication. + A wrapper package around [AppAuth](https://appauth.io/) that provides functionalities for the authentication and authorization of users. This dependency will be used to communicate with WSO2 Identity Platform to perform user authentication. - [http](https://pub.dev/packages/http) - A composable, future-based library for making HTTP requests. This will be used to access Asgardeo server endpoints in the application flow. + A composable, future-based library for making HTTP requests. This will be used to access WSO2 Identity Platform server endpoints in the application flow. To add these dependencies: @@ -111,7 +111,7 @@ To add these dependencies: ## Step 4: Configure the Callback URL -The callback URL is the method by which Asgardeo communicates back with the application. Once the authentication process is complete, Asgardeo redirects users back to the location specified in the callback URL. +The callback URL is the method by which WSO2 Identity Platform communicates back with the application. Once the authentication process is complete, WSO2 Identity Platform redirects users back to the location specified in the callback URL. - iOS setup @@ -139,9 +139,9 @@ The callback URL is the method by which Asgardeo communicates back with the appl Follow the [Readme](https://pub.dev/packages/flutter_appauth#flutter-appauth-plugin) of the Flutter AppAuth plugin for the configurations required for [macOS](https://pub.dev/packages/flutter_appauth#iosmacos-setup) and [Android](https://pub.dev/packages/flutter_appauth#android-setup). -## Step 5: Integrate your application with Asgardeo +## Step 5: Integrate your application with WSO2 Identity Platform -Follow the steps given below to integrate your application with Asgardeo: +Follow the steps given below to integrate your application with WSO2 Identity Platform: 1. Add the following code snippet to the `lib/main.dart` file to import the required external packages: @@ -162,7 +162,7 @@ Follow the steps given below to integrate your application with Asgardeo: ``` !!! note - You can find the values of these parameters in the **Quick Start** and **Info** tabs of the registered application in Asgardeo. + You can find the values of these parameters in the **Quick Start** and **Info** tabs of the registered application in WSO2 Identity Platform.employeegroup. An error will occur in the application. -5. Go to the logs portal on the Asgardeo Console and observe the following error log. +5. Go to the logs portal on the WSO2 Identity Platform Console and observe the following error log. - {: width="600" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} \ No newline at end of file + {: width="600" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/asgardeo-logs/index.md b/en/asgardeo/docs/guides/asgardeo-logs/index.md index 6cc09057b5..2cb93fc71a 100644 --- a/en/asgardeo/docs/guides/asgardeo-logs/index.md +++ b/en/asgardeo/docs/guides/asgardeo-logs/index.md @@ -1,14 +1,14 @@ -# Logs in Asgardeo +# Logs in WSO2 Identity Platform Logging is essential for maintaining system integrity and security. Two main types of logs are utilized: - [Diagnostic logs]({{base_path}}/guides/asgardeo-logs/diagnostic-logs/) help developers troubleshoot issues related to application onboarding and authentication flow configurations, -- [Audit logs]({{base_path}}/guides/asgardeo-logs/audit-logs/) track critical state changes within Asgardeo resources for security enhancement and incident investigation purposes. +- [Audit logs]({{base_path}}/guides/asgardeo-logs/audit-logs/) track critical state changes within WSO2 Identity Platform resources for security enhancement and incident investigation purposes. ## Analyze logs -You can access logs in Asgardeo by navigating to **Logs** on the Asgardeo Console. The logs portal looks as below. +You can access logs in WSO2 Identity Platform by navigating to **Logs** on the WSO2 Identity Platform Console. The logs portal looks as below. {: width="600" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} @@ -33,11 +33,11 @@ Besides the given timeframes, you can select a custom time range by following th ### Filter logs -When you expand a log in Asgardeo by clicking on it, you will get the following view. +When you expand a log in WSO2 Identity Platform by clicking on it, you will get the following view. {: width="600" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} -Click the **filter icon** next to one or more of the log parameters and Asgardeo will narrow the search based on those parameter values. +Click the **filter icon** next to one or more of the log parameters and WSO2 Identity Platform will narrow the search based on those parameter values. For example, if you would like to view logs related to a request, click the filter icon next to the relevant traceId and click **Run Query** to filter out all the related logs. @@ -46,4 +46,4 @@ For example, if you would like to view logs related to a request, click the filt ## Remote Log Publishing -Asgardeo allows you to securely publish both audit and diagnostic logs to external servers for long-term storage and analysis. You can configure separate publishers for audit and diagnostic logs with custom settings for each. Learn more about setting up [Remote Log Publishing]({{base_path}}/guides/asgardeo-logs/remote-log-publish). +WSO2 Identity Platform allows you to securely publish both audit and diagnostic logs to external servers for long-term storage and analysis. You can configure separate publishers for audit and diagnostic logs with custom settings for each. Learn more about setting up [Remote Log Publishing]({{base_path}}/guides/asgardeo-logs/remote-log-publish). diff --git a/en/asgardeo/docs/guides/asgardeo-logs/remote-log-publish.md b/en/asgardeo/docs/guides/asgardeo-logs/remote-log-publish.md index ca0bbbe59e..c0a1a66bd9 100644 --- a/en/asgardeo/docs/guides/asgardeo-logs/remote-log-publish.md +++ b/en/asgardeo/docs/guides/asgardeo-logs/remote-log-publish.md @@ -6,7 +6,7 @@ Remote Log Publishing enables organizations to securely transmit and store both Follow these steps to set up remote log publishing: -1. On the Asgardeo Console, navigate to **Logs**. +1. On the WSO2 Identity Platform Console, navigate to **Logs**. 2. Click on the **Configure** button in **Remote Log Publishing**. 3. You will see two sections for configuring remote publishers: * Diagnostic Logs Publisher diff --git a/en/asgardeo/docs/guides/authentication/add-identifier-first-login.md b/en/asgardeo/docs/guides/authentication/add-identifier-first-login.md index 9ff5e22f29..566dc0bf9b 100644 --- a/en/asgardeo/docs/guides/authentication/add-identifier-first-login.md +++ b/en/asgardeo/docs/guides/authentication/add-identifier-first-login.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/authentication/add-identifier-first-login.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/add-login-to-apps.md b/en/asgardeo/docs/guides/authentication/add-login-to-apps.md index 8a71ef7635..633390702c 100644 --- a/en/asgardeo/docs/guides/authentication/add-login-to-apps.md +++ b/en/asgardeo/docs/guides/authentication/add-login-to-apps.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/authentication/add-login-to-apps.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/add-login-to-mobile-app.md b/en/asgardeo/docs/guides/authentication/add-login-to-mobile-app.md index 4cfa036d11..149c0fe5da 100644 --- a/en/asgardeo/docs/guides/authentication/add-login-to-mobile-app.md +++ b/en/asgardeo/docs/guides/authentication/add-login-to-mobile-app.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set link_to_tutotials = "## Add login to your framework-based mobile apps diff --git a/en/asgardeo/docs/guides/authentication/add-login-to-single-page-app.md b/en/asgardeo/docs/guides/authentication/add-login-to-single-page-app.md index 9e14ba7092..7f50f4085a 100644 --- a/en/asgardeo/docs/guides/authentication/add-login-to-single-page-app.md +++ b/en/asgardeo/docs/guides/authentication/add-login-to-single-page-app.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/authentication/add-login-to-single-page-app.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/add-login-to-web-app.md b/en/asgardeo/docs/guides/authentication/add-login-to-web-app.md index a62ca44cf6..7a53fb3c87 100644 --- a/en/asgardeo/docs/guides/authentication/add-login-to-web-app.md +++ b/en/asgardeo/docs/guides/authentication/add-login-to-web-app.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/authentication/add-login-to-web-app.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/conditional-auth/access-control.md b/en/asgardeo/docs/guides/authentication/conditional-auth/access-control.md index 581f2d3d88..88bab33bff 100644 --- a/en/asgardeo/docs/guides/authentication/conditional-auth/access-control.md +++ b/en/asgardeo/docs/guides/authentication/conditional-auth/access-control.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% include "../../../../../includes/guides/authentication/conditional-auth/access-control.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/conditional-auth/adaptive-mfa.md b/en/asgardeo/docs/guides/authentication/conditional-auth/adaptive-mfa.md index 7b4a0e1ef0..4ff3bbd92b 100644 --- a/en/asgardeo/docs/guides/authentication/conditional-auth/adaptive-mfa.md +++ b/en/asgardeo/docs/guides/authentication/conditional-auth/adaptive-mfa.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% include "../../../../../includes/guides/authentication/conditional-auth/adaptive-mfa.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/conditional-auth/add-authentications-based-on-api-calls.md b/en/asgardeo/docs/guides/authentication/conditional-auth/add-authentications-based-on-api-calls.md index 8427879a81..529eb6ab60 100644 --- a/en/asgardeo/docs/guides/authentication/conditional-auth/add-authentications-based-on-api-calls.md +++ b/en/asgardeo/docs/guides/authentication/conditional-auth/add-authentications-based-on-api-calls.md @@ -1,9 +1,9 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% set asgardeo_auth_script_warning = ' !!! warning "Important" - As a security measure, Asgardeo does not allow the usage of two consecutive periods (`..`) in authentication scripts.' + As a security measure, WSO2 Identity Platform does not allow the usage of two consecutive periods (`..`) in authentication scripts.' %} {% include "../../../../../includes/guides/authentication/conditional-auth/add-authentications-based-on-api-calls.md" %} diff --git a/en/asgardeo/docs/guides/authentication/conditional-auth/configure-conditional-auth.md b/en/asgardeo/docs/guides/authentication/conditional-auth/configure-conditional-auth.md index 4ea93efdb5..47fdf78df7 100644 --- a/en/asgardeo/docs/guides/authentication/conditional-auth/configure-conditional-auth.md +++ b/en/asgardeo/docs/guides/authentication/conditional-auth/configure-conditional-auth.md @@ -1,10 +1,10 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% set jdk_version_message = "" %} {% set asgardeo_auth_script_warning = ' !!! warning "Important" - As a security measure, Asgardeo does not allow the usage of two consecutive periods (`..`) in authentication scripts.' + As a security measure, WSO2 Identity Platform does not allow the usage of two consecutive periods (`..`) in authentication scripts.' %} {% include "../../../../../includes/guides/authentication/conditional-auth/configure-conditional-auth.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/conditional-auth/group-based-template-access-control.md b/en/asgardeo/docs/guides/authentication/conditional-auth/group-based-template-access-control.md index 4ec34cf232..0260929425 100644 --- a/en/asgardeo/docs/guides/authentication/conditional-auth/group-based-template-access-control.md +++ b/en/asgardeo/docs/guides/authentication/conditional-auth/group-based-template-access-control.md @@ -1,9 +1,9 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% set asgardeo_auth_script_warning = ' !!! warning "Important" - As a security measure, Asgardeo does not allow the usage of two consecutive periods (`..`) in authentication scripts.' + As a security measure, WSO2 Identity Platform does not allow the usage of two consecutive periods (`..`) in authentication scripts.' %} {% include "../../../../../includes/guides/authentication/conditional-auth/group-based-template-access-control.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/conditional-auth/group-based-template.md b/en/asgardeo/docs/guides/authentication/conditional-auth/group-based-template.md index e918ed3860..7c2da77201 100644 --- a/en/asgardeo/docs/guides/authentication/conditional-auth/group-based-template.md +++ b/en/asgardeo/docs/guides/authentication/conditional-auth/group-based-template.md @@ -1,9 +1,9 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% set asgardeo_auth_script_warning = ' !!! warning "Important" - As a security measure, Asgardeo does not allow the usage of two consecutive periods (`..`) in authentication scripts.' + As a security measure, WSO2 Identity Platform does not allow the usage of two consecutive periods (`..`) in authentication scripts.' %} {% include "../../../../../includes/guides/authentication/conditional-auth/group-based-template.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/conditional-auth/index.md b/en/asgardeo/docs/guides/authentication/conditional-auth/index.md index d0a1b59aa8..a910f8391d 100644 --- a/en/asgardeo/docs/guides/authentication/conditional-auth/index.md +++ b/en/asgardeo/docs/guides/authentication/conditional-auth/index.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} # Add conditional authentication diff --git a/en/asgardeo/docs/guides/authentication/conditional-auth/ip-based-template.md b/en/asgardeo/docs/guides/authentication/conditional-auth/ip-based-template.md index 4977ee1a07..d5fbda6d2c 100644 --- a/en/asgardeo/docs/guides/authentication/conditional-auth/ip-based-template.md +++ b/en/asgardeo/docs/guides/authentication/conditional-auth/ip-based-template.md @@ -1,9 +1,9 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% set asgardeo_auth_script_warning = ' !!! warning "Important" - As a security measure, Asgardeo does not allow the usage of two consecutive periods (`..`) in authentication scripts.' + As a security measure, WSO2 Identity Platform does not allow the usage of two consecutive periods (`..`) in authentication scripts.' %} {% include "../../../../../includes/guides/authentication/conditional-auth/ip-based-template.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/conditional-auth/new-device-based-template.md b/en/asgardeo/docs/guides/authentication/conditional-auth/new-device-based-template.md index 23e6e6a3d5..c0d343be95 100644 --- a/en/asgardeo/docs/guides/authentication/conditional-auth/new-device-based-template.md +++ b/en/asgardeo/docs/guides/authentication/conditional-auth/new-device-based-template.md @@ -1,9 +1,9 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% set asgardeo_auth_script_warning = ' !!! warning "Important" - As a security measure, Asgardeo does not allow the usage of two consecutive periods (`..`) in authentication scripts.' + As a security measure, WSO2 Identity Platform does not allow the usage of two consecutive periods (`..`) in authentication scripts.' %} {% include "../../../../../includes/guides/authentication/conditional-auth/new-device-based-template.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/conditional-auth/on-demand-silent-password-migration-template.md b/en/asgardeo/docs/guides/authentication/conditional-auth/on-demand-silent-password-migration-template.md index 4719c2c6d6..160318d6c5 100644 --- a/en/asgardeo/docs/guides/authentication/conditional-auth/on-demand-silent-password-migration-template.md +++ b/en/asgardeo/docs/guides/authentication/conditional-auth/on-demand-silent-password-migration-template.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../../includes/guides/authentication/conditional-auth/on-demand-silent-password-migration-template.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/conditional-auth/otp-retry-resend-limits.md b/en/asgardeo/docs/guides/authentication/conditional-auth/otp-retry-resend-limits.md index af9ce0d877..47d9733194 100644 --- a/en/asgardeo/docs/guides/authentication/conditional-auth/otp-retry-resend-limits.md +++ b/en/asgardeo/docs/guides/authentication/conditional-auth/otp-retry-resend-limits.md @@ -1,9 +1,9 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% set asgardeo_auth_script_warning = ' !!! warning "Important" - As a security measure, Asgardeo does not allow the usage of two consecutive periods (`..`) in authentication scripts.' + As a security measure, WSO2 Identity Platform does not allow the usage of two consecutive periods (`..`) in authentication scripts.' %} {% include "../../../../../includes/guides/authentication/conditional-auth/otp-retry-resend-limits.md" %} diff --git a/en/asgardeo/docs/guides/authentication/conditional-auth/passkey-progressive-enrollment-based-template.md b/en/asgardeo/docs/guides/authentication/conditional-auth/passkey-progressive-enrollment-based-template.md index 1349330ef0..33e0b04368 100644 --- a/en/asgardeo/docs/guides/authentication/conditional-auth/passkey-progressive-enrollment-based-template.md +++ b/en/asgardeo/docs/guides/authentication/conditional-auth/passkey-progressive-enrollment-based-template.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../../includes/guides/authentication/conditional-auth/passkey-progressive-enrollment-based-template.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/conditional-auth/push-device-progressive-enrollment-based-template.md b/en/asgardeo/docs/guides/authentication/conditional-auth/push-device-progressive-enrollment-based-template.md index 1a77df768a..90945ec40d 100644 --- a/en/asgardeo/docs/guides/authentication/conditional-auth/push-device-progressive-enrollment-based-template.md +++ b/en/asgardeo/docs/guides/authentication/conditional-auth/push-device-progressive-enrollment-based-template.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../../includes/guides/authentication/conditional-auth/push-device-progressive-enrollment-based-template.md" %} diff --git a/en/asgardeo/docs/guides/authentication/conditional-auth/sign-in-option-based-template.md b/en/asgardeo/docs/guides/authentication/conditional-auth/sign-in-option-based-template.md index 9c55aedf05..e01f2dec2c 100644 --- a/en/asgardeo/docs/guides/authentication/conditional-auth/sign-in-option-based-template.md +++ b/en/asgardeo/docs/guides/authentication/conditional-auth/sign-in-option-based-template.md @@ -1,9 +1,9 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% set asgardeo_auth_script_warning = ' !!! warning "Important" - As a security measure, Asgardeo does not allow the usage of two consecutive periods (`..`) in authentication scripts.' + As a security measure, WSO2 Identity Platform does not allow the usage of two consecutive periods (`..`) in authentication scripts.' %} {% include "../../../../../includes/guides/authentication/conditional-auth/sign-in-option-based-template.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/conditional-auth/user-age-based-template.md b/en/asgardeo/docs/guides/authentication/conditional-auth/user-age-based-template.md index a2bcac0847..db665b4f4e 100644 --- a/en/asgardeo/docs/guides/authentication/conditional-auth/user-age-based-template.md +++ b/en/asgardeo/docs/guides/authentication/conditional-auth/user-age-based-template.md @@ -1,9 +1,9 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% set asgardeo_auth_script_warning = ' !!! warning "Important" - As a security measure, Asgardeo does not allow the usage of two consecutive periods (`..`) in authentication scripts.' + As a security measure, WSO2 Identity Platform does not allow the usage of two consecutive periods (`..`) in authentication scripts.' %} {% include "../../../../../includes/guides/authentication/conditional-auth/user-age-based-template.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/conditional-auth/write-your-first-script.md b/en/asgardeo/docs/guides/authentication/conditional-auth/write-your-first-script.md index d2e774c379..9e59228720 100644 --- a/en/asgardeo/docs/guides/authentication/conditional-auth/write-your-first-script.md +++ b/en/asgardeo/docs/guides/authentication/conditional-auth/write-your-first-script.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% include "../../../../../includes/guides/authentication/conditional-auth/write-your-first-script.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/decentralized-login/index.md b/en/asgardeo/docs/guides/authentication/decentralized-login/index.md index f5af99752c..80ad853ffe 100644 --- a/en/asgardeo/docs/guides/authentication/decentralized-login/index.md +++ b/en/asgardeo/docs/guides/authentication/decentralized-login/index.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../../includes/guides/authentication/decentralized-login/index.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/decentralized-login/sign-in-with-ethereum.md b/en/asgardeo/docs/guides/authentication/decentralized-login/sign-in-with-ethereum.md index 80f3fcf191..1250d1b529 100644 --- a/en/asgardeo/docs/guides/authentication/decentralized-login/sign-in-with-ethereum.md +++ b/en/asgardeo/docs/guides/authentication/decentralized-login/sign-in-with-ethereum.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% include "../../../../../includes/guides/authentication/decentralized-login/sign-in-with-ethereum.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/eid-login/add-france-connect-login.md b/en/asgardeo/docs/guides/authentication/eid-login/add-france-connect-login.md index 85e77c059f..2ba0881959 100644 --- a/en/asgardeo/docs/guides/authentication/eid-login/add-france-connect-login.md +++ b/en/asgardeo/docs/guides/authentication/eid-login/add-france-connect-login.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% include "../../../../../includes/guides/authentication/eid-login/add-franceconnect-login.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/eid-login/add-signicat-login.md b/en/asgardeo/docs/guides/authentication/eid-login/add-signicat-login.md index 7c909ed4d1..c3f8ded8ed 100644 --- a/en/asgardeo/docs/guides/authentication/eid-login/add-signicat-login.md +++ b/en/asgardeo/docs/guides/authentication/eid-login/add-signicat-login.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% include "../../../../../includes/guides/authentication/eid-login/add-signicat-login.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/eid-login/add-swiss-id-login.md b/en/asgardeo/docs/guides/authentication/eid-login/add-swiss-id-login.md index 6266f8a339..15580239ff 100644 --- a/en/asgardeo/docs/guides/authentication/eid-login/add-swiss-id-login.md +++ b/en/asgardeo/docs/guides/authentication/eid-login/add-swiss-id-login.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% include "../../../../../includes/guides/authentication/eid-login/add-swissid-login.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/index.md b/en/asgardeo/docs/guides/authentication/index.md index 9754e3cbef..1806bd7935 100644 --- a/en/asgardeo/docs/guides/authentication/index.md +++ b/en/asgardeo/docs/guides/authentication/index.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/authentication/index.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/jit-user-provisioning.md b/en/asgardeo/docs/guides/authentication/jit-user-provisioning.md index 0feb8298ef..edbb9e9693 100644 --- a/en/asgardeo/docs/guides/authentication/jit-user-provisioning.md +++ b/en/asgardeo/docs/guides/authentication/jit-user-provisioning.md @@ -1,3 +1,3 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set show_advanced_account_linking_content = "true"%} {% include "../../../../includes/guides/authentication/jit-user-provisioning.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/manage-consent-for-attributes.md b/en/asgardeo/docs/guides/authentication/manage-consent-for-attributes.md index f07f9a382d..2101be7cbe 100644 --- a/en/asgardeo/docs/guides/authentication/manage-consent-for-attributes.md +++ b/en/asgardeo/docs/guides/authentication/manage-consent-for-attributes.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/authentication/manage-consent-for-attributes.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/mfa/add-duo-login.md b/en/asgardeo/docs/guides/authentication/mfa/add-duo-login.md index aab7280a47..fa99ce343a 100644 --- a/en/asgardeo/docs/guides/authentication/mfa/add-duo-login.md +++ b/en/asgardeo/docs/guides/authentication/mfa/add-duo-login.md @@ -2,14 +2,14 @@ [Duo](https://duo.com/) is a multi-factor authentication option that offer multiple verification methods such as push notifications, SMS, phone calls, and hardware tokens. -In this guide, you'll learn how to integrate Duo as a second-factor authentication provider for your Asgardeo application. +In this guide, you'll learn how to integrate Duo as a second-factor authentication provider for your WSO2 Identity Platform application. ## Prerequisites Before you begin, ensure you have the following: - [Duo Account](https://signup.duo.com/): A Duo administrator account to configure your Duo application. -- [Asgardeo Account](https://asgardeo.io/signup): Access to your Asgardeo console with administrative privileges. +- [WSO2 Identity Platform Account](https://asgardeo.io/signup): Access to your WSO2 Identity Platform console with administrative privileges. ## Configure Duo Security Application @@ -24,11 +24,11 @@ Before you begin, ensure you have the following: 4. Save the **Client ID**, **Client secret**, and **API hostname** as you will need these later. -## Add Duo as a Connection in Asgardeo +## Add Duo as a Connection in WSO2 Identity Platform -Next, you need to register Duo as a connection in Asgardeo. To do so, follow the steps below. +Next, you need to register Duo as a connection in WSO2 Identity Platform. To do so, follow the steps below. -1. Log in to the [Asgardeo Console](https://console.asgardeo.io/) as an administrator. +1. Log in to the [WSO2 Identity Platform Console](https://console.asgardeo.io/) as an administrator. 2. Navigate to **Connections** from the left-hand panel 3. Click **New Connection** and select **Duo** from the listed templates. 4. Provide a Name for the Duo connection (e.g., "Duo Security"). @@ -39,7 +39,7 @@ Next, you need to register Duo as a connection in Asgardeo. To do so, follow the The created Duo connection should be added as an MFA option to the login flow of an application. To do so, follow the steps below. -1. On the [Asgardeo Console](https://console.asgardeo.io/), navigate to **Applications**. +1. On the [WSO2 Identity Platform Console](https://console.asgardeo.io/), navigate to **Applications**. 2. Select the application for which you want to enable Duo MFA. 3. Go to the **Login Flow** section. Username and Password will be added as the default login method. 4. Click on the **+ icon** to add a new step to the login flow. @@ -66,4 +66,4 @@ Finally, you need to verify that Duo has been successfully integrated and is fun 4. If your verification is successful, you will be logged into the app. -You've successfully integrated Duo 2FA into your Asgardeo application. This additional security layer helps protect your users and sensitive data from unauthorized access. \ No newline at end of file +You've successfully integrated Duo 2FA into your WSO2 Identity Platform application. This additional security layer helps protect your users and sensitive data from unauthorized access. \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/mfa/add-iproov-login.md b/en/asgardeo/docs/guides/authentication/mfa/add-iproov-login.md index 7b62d386b2..85e2cf4d7e 100644 --- a/en/asgardeo/docs/guides/authentication/mfa/add-iproov-login.md +++ b/en/asgardeo/docs/guides/authentication/mfa/add-iproov-login.md @@ -3,7 +3,7 @@ [iProov](https://www.iproov.com/) is a passwordless authentication method that allows users to log in to applications using facial biometrics. iProov's patented Flashmark biometric technology ensures that the user is a real person and not a spoof or a replay. -This guide explains how you can use iProov to add passwordless login to applications registered in your Asgardeo organization. +This guide explains how you can use iProov to add passwordless login to applications registered in your WSO2 Identity Platform organization. ## Prerequisites @@ -32,11 +32,11 @@ Follow the steps below to register your service provider in the iPortal. - **API key** - **API secret** -## Register iProov in Asgardeo as a connection +## Register iProov in WSO2 Identity Platform as a connection -Follow the steps below to register iProov as a connection in Asgardeo. +Follow the steps below to register iProov as a connection in WSO2 Identity Platform. -1. On the Asgardeo Console, go to **Connections**. +1. On the WSO2 Identity Platform Console, go to **Connections**. 2. Click **Create Connection** and select **iProov**. @@ -78,11 +78,11 @@ Follow the steps below to register iProov as a connection in Asgardeo. ## Enable iProov login !!! note "Before you begin" - You need to [register an application with Asgardeo]({{base_path}}/guides/applications/). You can register your own application or use one of the [sample applications]({{base_path}}/get-started/try-samples/) provided. + You need to [register an application with WSO2 Identity Platform]({{base_path}}/guides/applications/). You can register your own application or use one of the [sample applications]({{base_path}}/get-started/try-samples/) provided. To enable iProov login for your application: -1. On the Asgardeo Console, go to **Applications**. +1. On the WSO2 Identity Platform Console, go to **Applications**. 2. Go to the **Login Flow** tab of the application and add iProov login from your preferred editor: @@ -113,7 +113,7 @@ Follow the steps given below: 1. Access the application URL. -2. Click **Login** to open the Asgardeo login page. +2. Click **Login** to open the WSO2 Identity Platform login page. 3. Complete the preceding authentication steps. diff --git a/en/asgardeo/docs/guides/authentication/oidc/add-back-channel-logout.md b/en/asgardeo/docs/guides/authentication/oidc/add-back-channel-logout.md index 0c4ae306e7..cea6978e82 100644 --- a/en/asgardeo/docs/guides/authentication/oidc/add-back-channel-logout.md +++ b/en/asgardeo/docs/guides/authentication/oidc/add-back-channel-logout.md @@ -19,7 +19,7 @@ Follow the steps below to register the back-channel endpoint of your application [Register your OIDC application]({{base_path}}/guides/applications/) in {{product_name}}. -1. On the Asgardeo Console, go to **Applications** and select your OIDC application. +1. On the WSO2 Identity Platform Console, go to **Applications** and select your OIDC application. 2. Go to the **Protocol** tab, and under **Logout URLs**, enter the **Back channel logout URL**. diff --git a/en/asgardeo/docs/guides/authentication/oidc/add-logout.md b/en/asgardeo/docs/guides/authentication/oidc/add-logout.md index f7039b6d02..d1e66f7cfb 100644 --- a/en/asgardeo/docs/guides/authentication/oidc/add-logout.md +++ b/en/asgardeo/docs/guides/authentication/oidc/add-logout.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% include "../../../../../includes/guides/authentication/oidc/add-logout.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/oidc/discover-oidc-configs.md b/en/asgardeo/docs/guides/authentication/oidc/discover-oidc-configs.md index 43960a45da..e736297582 100644 --- a/en/asgardeo/docs/guides/authentication/oidc/discover-oidc-configs.md +++ b/en/asgardeo/docs/guides/authentication/oidc/discover-oidc-configs.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% include "../../../../../includes/guides/authentication/oidc/discover-oidc-configs.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/oidc/implement-auth-code-with-pkce.md b/en/asgardeo/docs/guides/authentication/oidc/implement-auth-code-with-pkce.md index 5d56bf7bf0..943cc10f20 100644 --- a/en/asgardeo/docs/guides/authentication/oidc/implement-auth-code-with-pkce.md +++ b/en/asgardeo/docs/guides/authentication/oidc/implement-auth-code-with-pkce.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% include "../../../../../includes/guides/authentication/oidc/implement-auth-code-with-pkce.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/oidc/implement-auth-code.md b/en/asgardeo/docs/guides/authentication/oidc/implement-auth-code.md index 3f2b6c1f04..1810d2436c 100644 --- a/en/asgardeo/docs/guides/authentication/oidc/implement-auth-code.md +++ b/en/asgardeo/docs/guides/authentication/oidc/implement-auth-code.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% include "../../../../../includes/guides/authentication/oidc/implement-auth-code.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/oidc/implement-device-flow.md b/en/asgardeo/docs/guides/authentication/oidc/implement-device-flow.md index 59536b82bc..55022e6d41 100644 --- a/en/asgardeo/docs/guides/authentication/oidc/implement-device-flow.md +++ b/en/asgardeo/docs/guides/authentication/oidc/implement-device-flow.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% include "../../../../../includes/guides/authentication/oidc/implement-device-flow.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/oidc/index.md b/en/asgardeo/docs/guides/authentication/oidc/index.md index bc144862cc..65edbd8360 100644 --- a/en/asgardeo/docs/guides/authentication/oidc/index.md +++ b/en/asgardeo/docs/guides/authentication/oidc/index.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% include "../../../../../includes/guides/authentication/oidc/index.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/oidc/private-key-jwt-client-auth.md b/en/asgardeo/docs/guides/authentication/oidc/private-key-jwt-client-auth.md index 17b6b6918a..6f39f2877f 100644 --- a/en/asgardeo/docs/guides/authentication/oidc/private-key-jwt-client-auth.md +++ b/en/asgardeo/docs/guides/authentication/oidc/private-key-jwt-client-auth.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% include "../../../../../includes/guides/authentication/oidc/private-key-jwt-client-auth.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/oidc/request-user-info.md b/en/asgardeo/docs/guides/authentication/oidc/request-user-info.md index 1a181aae87..cffe1c66f5 100644 --- a/en/asgardeo/docs/guides/authentication/oidc/request-user-info.md +++ b/en/asgardeo/docs/guides/authentication/oidc/request-user-info.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% include "../../../../../includes/guides/authentication/oidc/request-user-info.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/oidc/revoke-tokens.md b/en/asgardeo/docs/guides/authentication/oidc/revoke-tokens.md index 92d007f973..b0a4869b6e 100644 --- a/en/asgardeo/docs/guides/authentication/oidc/revoke-tokens.md +++ b/en/asgardeo/docs/guides/authentication/oidc/revoke-tokens.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% include "../../../../../includes/guides/authentication/oidc/revoke-tokens.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/oidc/token-validation-resource-server.md b/en/asgardeo/docs/guides/authentication/oidc/token-validation-resource-server.md index ddd3d8e408..fd7d0bc92f 100644 --- a/en/asgardeo/docs/guides/authentication/oidc/token-validation-resource-server.md +++ b/en/asgardeo/docs/guides/authentication/oidc/token-validation-resource-server.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% set username = "DEFAULT/Alica@gmail.com@bifrost" %} diff --git a/en/asgardeo/docs/guides/authentication/oidc/validate-id-tokens.md b/en/asgardeo/docs/guides/authentication/oidc/validate-id-tokens.md index 8442dbbc45..d5d46a9648 100644 --- a/en/asgardeo/docs/guides/authentication/oidc/validate-id-tokens.md +++ b/en/asgardeo/docs/guides/authentication/oidc/validate-id-tokens.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% set org_name = "bifrost" %} diff --git a/en/asgardeo/docs/guides/authentication/passwordless-login/add-passwordless-login-with-email-otp.md b/en/asgardeo/docs/guides/authentication/passwordless-login/add-passwordless-login-with-email-otp.md index 7db2ef2597..d9f5fe7461 100644 --- a/en/asgardeo/docs/guides/authentication/passwordless-login/add-passwordless-login-with-email-otp.md +++ b/en/asgardeo/docs/guides/authentication/passwordless-login/add-passwordless-login-with-email-otp.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set admin_login_note = diff --git a/en/asgardeo/docs/guides/authentication/passwordless-login/add-passwordless-login-with-hypr.md b/en/asgardeo/docs/guides/authentication/passwordless-login/add-passwordless-login-with-hypr.md index ad7f6ee9b2..dcb4e0842d 100644 --- a/en/asgardeo/docs/guides/authentication/passwordless-login/add-passwordless-login-with-hypr.md +++ b/en/asgardeo/docs/guides/authentication/passwordless-login/add-passwordless-login-with-hypr.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set admin_login_note = diff --git a/en/asgardeo/docs/guides/authentication/passwordless-login/add-passwordless-login-with-magic-link.md b/en/asgardeo/docs/guides/authentication/passwordless-login/add-passwordless-login-with-magic-link.md index 943bfbdb88..2d66d91e4f 100644 --- a/en/asgardeo/docs/guides/authentication/passwordless-login/add-passwordless-login-with-magic-link.md +++ b/en/asgardeo/docs/guides/authentication/passwordless-login/add-passwordless-login-with-magic-link.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set admin_login_note = diff --git a/en/asgardeo/docs/guides/authentication/passwordless-login/add-passwordless-login-with-push-notification.md b/en/asgardeo/docs/guides/authentication/passwordless-login/add-passwordless-login-with-push-notification.md index 1eb4bce4ba..5aadd7e58e 100644 --- a/en/asgardeo/docs/guides/authentication/passwordless-login/add-passwordless-login-with-push-notification.md +++ b/en/asgardeo/docs/guides/authentication/passwordless-login/add-passwordless-login-with-push-notification.md @@ -1,3 +1,3 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../../includes/guides/authentication/passwordless-login/add-passwordless-login-with-push-notification.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/passwordless-login/index.md b/en/asgardeo/docs/guides/authentication/passwordless-login/index.md index 6009f1729e..998fcb7852 100644 --- a/en/asgardeo/docs/guides/authentication/passwordless-login/index.md +++ b/en/asgardeo/docs/guides/authentication/passwordless-login/index.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set hypr_login = " ## HYPR login diff --git a/en/asgardeo/docs/guides/authentication/saml/discover-saml-configs.md b/en/asgardeo/docs/guides/authentication/saml/discover-saml-configs.md index 6375a7c93a..5735f9fe1f 100644 --- a/en/asgardeo/docs/guides/authentication/saml/discover-saml-configs.md +++ b/en/asgardeo/docs/guides/authentication/saml/discover-saml-configs.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% set entityID = "accounts.asgardeo.io/t/{organization_name}" %} diff --git a/en/asgardeo/docs/guides/authentication/saml/index.md b/en/asgardeo/docs/guides/authentication/saml/index.md index 73232ce0f0..da4aa0f42b 100644 --- a/en/asgardeo/docs/guides/authentication/saml/index.md +++ b/en/asgardeo/docs/guides/authentication/saml/index.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../../includes/guides/authentication/saml/index.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/social-login/add-apple-login.md b/en/asgardeo/docs/guides/authentication/social-login/add-apple-login.md index e62dce9f6f..973222242b 100644 --- a/en/asgardeo/docs/guides/authentication/social-login/add-apple-login.md +++ b/en/asgardeo/docs/guides/authentication/social-login/add-apple-login.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_domain = "api.asgardeo.io" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set localhost_warning_note = "" %} diff --git a/en/asgardeo/docs/guides/authentication/social-login/add-facebook-login.md b/en/asgardeo/docs/guides/authentication/social-login/add-facebook-login.md index ab98215869..2f03ee25e5 100644 --- a/en/asgardeo/docs/guides/authentication/social-login/add-facebook-login.md +++ b/en/asgardeo/docs/guides/authentication/social-login/add-facebook-login.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% include "../../../../../includes/guides/authentication/social-login/add-facebook-login.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/social-login/add-github-login.md b/en/asgardeo/docs/guides/authentication/social-login/add-github-login.md index ae95d2793b..e4c9652692 100644 --- a/en/asgardeo/docs/guides/authentication/social-login/add-github-login.md +++ b/en/asgardeo/docs/guides/authentication/social-login/add-github-login.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% include "../../../../../includes/guides/authentication/social-login/add-github-login.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/social-login/add-google-login.md b/en/asgardeo/docs/guides/authentication/social-login/add-google-login.md index 9814675dca..02bf0bc73e 100755 --- a/en/asgardeo/docs/guides/authentication/social-login/add-google-login.md +++ b/en/asgardeo/docs/guides/authentication/social-login/add-google-login.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% include "../../../../../includes/guides/authentication/social-login/add-google-login.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/social-login/add-linkedin-login.md b/en/asgardeo/docs/guides/authentication/social-login/add-linkedin-login.md index fa5df5aa88..2b1d4ffdf5 100644 --- a/en/asgardeo/docs/guides/authentication/social-login/add-linkedin-login.md +++ b/en/asgardeo/docs/guides/authentication/social-login/add-linkedin-login.md @@ -1,3 +1,3 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% include "../../../../../includes/guides/authentication/social-login/add-linkedin-login.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/social-login/add-microsoft-login.md b/en/asgardeo/docs/guides/authentication/social-login/add-microsoft-login.md index 017c31429f..31e26fe705 100644 --- a/en/asgardeo/docs/guides/authentication/social-login/add-microsoft-login.md +++ b/en/asgardeo/docs/guides/authentication/social-login/add-microsoft-login.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% include "../../../../../includes/guides/authentication/social-login/add-microsoft-login.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/social-login/index.md b/en/asgardeo/docs/guides/authentication/social-login/index.md index f2307cae62..5b566c3cb6 100644 --- a/en/asgardeo/docs/guides/authentication/social-login/index.md +++ b/en/asgardeo/docs/guides/authentication/social-login/index.md @@ -2,5 +2,5 @@ template: templates/no-right-sidebar.html --- -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../../includes/guides/authentication/social-login/index.md" %} diff --git a/en/asgardeo/docs/guides/authentication/sso-integrations/add-google-workspace-template.md b/en/asgardeo/docs/guides/authentication/sso-integrations/add-google-workspace-template.md index c8f356c2b6..8ca03e49d8 100644 --- a/en/asgardeo/docs/guides/authentication/sso-integrations/add-google-workspace-template.md +++ b/en/asgardeo/docs/guides/authentication/sso-integrations/add-google-workspace-template.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set issuer_name = "api.asgardeo.io/t/{organization_name}" %} {% set my_account_host_path = "https://myaccount.asgardeo.io/t/{organization_name}" %} diff --git a/en/asgardeo/docs/guides/authentication/sso-integrations/add-microsoft-365-template.md b/en/asgardeo/docs/guides/authentication/sso-integrations/add-microsoft-365-template.md index 4545889dd4..e482c4f4d3 100644 --- a/en/asgardeo/docs/guides/authentication/sso-integrations/add-microsoft-365-template.md +++ b/en/asgardeo/docs/guides/authentication/sso-integrations/add-microsoft-365-template.md @@ -1,3 +1,3 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% include "../../../../../includes/guides/authentication/sso-integrations/add-microsoft-365-template.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/sso-integrations/add-salesforce-template.md b/en/asgardeo/docs/guides/authentication/sso-integrations/add-salesforce-template.md index 6618be9dcf..e288985d6b 100644 --- a/en/asgardeo/docs/guides/authentication/sso-integrations/add-salesforce-template.md +++ b/en/asgardeo/docs/guides/authentication/sso-integrations/add-salesforce-template.md @@ -1,3 +1,3 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% include "../../../../../includes/guides/authentication/sso-integrations/add-salesforce-template.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/sso-integrations/add-slack-template.md b/en/asgardeo/docs/guides/authentication/sso-integrations/add-slack-template.md index f26d37bfd5..232b343719 100644 --- a/en/asgardeo/docs/guides/authentication/sso-integrations/add-slack-template.md +++ b/en/asgardeo/docs/guides/authentication/sso-integrations/add-slack-template.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set issuer_name = "api.asgardeo.io/t/{organization_name}" %} {% include "../../../../../includes/guides/authentication/sso-integrations/add-slack-template.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/sso-integrations/add-zoom-template.md b/en/asgardeo/docs/guides/authentication/sso-integrations/add-zoom-template.md index 450e34637c..eb173276d8 100644 --- a/en/asgardeo/docs/guides/authentication/sso-integrations/add-zoom-template.md +++ b/en/asgardeo/docs/guides/authentication/sso-integrations/add-zoom-template.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set issuer_name = "api.asgardeo.io/t/{organization_name}" %} {% include "../../../../../includes/guides/authentication/sso-integrations/add-zoom-template.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/standard-based-login/add-oidc-idp-login.md b/en/asgardeo/docs/guides/authentication/standard-based-login/add-oidc-idp-login.md index a3ae7acb4b..131e5a142e 100644 --- a/en/asgardeo/docs/guides/authentication/standard-based-login/add-oidc-idp-login.md +++ b/en/asgardeo/docs/guides/authentication/standard-based-login/add-oidc-idp-login.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% include "../../../../../includes/guides/authentication/standard-based-login/add-oidc-idp-login.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/standard-based-login/add-saml-idp-login.md b/en/asgardeo/docs/guides/authentication/standard-based-login/add-saml-idp-login.md index f416ae9887..a91993dfb7 100644 --- a/en/asgardeo/docs/guides/authentication/standard-based-login/add-saml-idp-login.md +++ b/en/asgardeo/docs/guides/authentication/standard-based-login/add-saml-idp-login.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% include "../../../../../includes/guides/authentication/standard-based-login/add-saml-idp-login.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/standard-based-login/index.md b/en/asgardeo/docs/guides/authentication/standard-based-login/index.md index eed0ac5e37..263f5f5eba 100644 --- a/en/asgardeo/docs/guides/authentication/standard-based-login/index.md +++ b/en/asgardeo/docs/guides/authentication/standard-based-login/index.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../../includes/guides/authentication/standard-based-login/index.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/user-attributes/enable-attributes-for-oidc-app.md b/en/asgardeo/docs/guides/authentication/user-attributes/enable-attributes-for-oidc-app.md index 9d8ee9f020..d85f370936 100644 --- a/en/asgardeo/docs/guides/authentication/user-attributes/enable-attributes-for-oidc-app.md +++ b/en/asgardeo/docs/guides/authentication/user-attributes/enable-attributes-for-oidc-app.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% set configure_subject_identifier = "" %} {% include "../../../../../includes/guides/authentication/user-attributes/enable-attributes-for-oidc-app.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/user-attributes/enable-attributes-for-saml-app.md b/en/asgardeo/docs/guides/authentication/user-attributes/enable-attributes-for-saml-app.md index f8a0fd8d72..4b5f0aa4a4 100644 --- a/en/asgardeo/docs/guides/authentication/user-attributes/enable-attributes-for-saml-app.md +++ b/en/asgardeo/docs/guides/authentication/user-attributes/enable-attributes-for-saml-app.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../../includes/guides/authentication/user-attributes/enable-attributes-for-saml-app.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/authentication/user-attributes/index.md b/en/asgardeo/docs/guides/authentication/user-attributes/index.md index 87d1599dc2..72e0a8dd38 100644 --- a/en/asgardeo/docs/guides/authentication/user-attributes/index.md +++ b/en/asgardeo/docs/guides/authentication/user-attributes/index.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../../includes/guides/authentication/user-attributes/index.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/branding/configure-custom-domains.md b/en/asgardeo/docs/guides/branding/configure-custom-domains.md index ffebf010da..cae845de5b 100644 --- a/en/asgardeo/docs/guides/branding/configure-custom-domains.md +++ b/en/asgardeo/docs/guides/branding/configure-custom-domains.md @@ -2,9 +2,9 @@!!! warning - You need a paid Asgardeo subscription to use this feature. If you don’t already have one, view the available [subscription plans](https://wso2.com/asgardeo/pricing/) and contact the Asgardeo sales team. + You need a paid WSO2 Identity Platform subscription to use this feature. If you don’t already have one, view the available [subscription plans](https://wso2.com/asgardeo/pricing/) and contact the WSO2 Identity Platform sales team. -By default, the Asgardeo interfaces presented to your users (during the login, sign-up, and account recovery flows), as well as the back-end services (such as APIs), are served by Asgardeo on the following domains: +By default, the WSO2 Identity Platform interfaces presented to your users (during the login, sign-up, and account recovery flows), as well as the back-end services (such as APIs), are served by WSO2 Identity Platform on the following domains: - **User interfaces**: `https://accounts.asgardeo.io/t/{org_name}` - **Services**: `https://api.asgardeo.io/t/{org_name}` @@ -17,5 +17,5 @@ With domain branding, you can customize the above endpoints to have hostnames sp !!! note "Custom domain branding for B2B applications" If you have configured [organizations]({{base_path}}/guides/organization-management/manage-organizations/), note that the custom domain you configure for your root organization also applies to your organizations. -If you have a paid Asgardeo subscription and wish to implement a custom domain for your organization, contact Asgardeo support through the [WSO2 cloud support portal](https://cloud-support.wso2.com/) or send a request email to `asgardeo-help@wso2.com` and the team will get back to you with instructions. +If you have a paid WSO2 Identity Platform subscription and wish to implement a custom domain for your organization, contact WSO2 Identity Platform support through the [WSO2 cloud support portal](https://cloud-support.wso2.com/) or send a request email to `asgardeo-help@wso2.com` and the team will get back to you with instructions. Note that email and support portal requests should be sent from the respective account of an administrator. diff --git a/en/asgardeo/docs/guides/branding/configure-ui-branding.md b/en/asgardeo/docs/guides/branding/configure-ui-branding.md index 571f4719d2..44e7475793 100644 --- a/en/asgardeo/docs/guides/branding/configure-ui-branding.md +++ b/en/asgardeo/docs/guides/branding/configure-ui-branding.md @@ -1,10 +1,10 @@ {% set powered_by_note = "!!! note - For free-tier subscriptions, the **Powered by Asgardeo** label will display on the Asgardeo-powered interfaces when branding is published." %} + For free-tier subscriptions, the **Powered by WSO2 Identity Platform** label will display on the WSO2 Identity Platform-powered interfaces when branding is published." %} {% set asgardeo_help = "## Extend branding -When you go to **Branding > Styles & Text** on the Asgardeo console, you will see the list of branding preferences that are supported for your user interfaces by default. +When you go to **Branding > Styles & Text** on the WSO2 Identity Platform console, you will see the list of branding preferences that are supported for your user interfaces by default. -If you require any of the extended branding capabilities (explained below), you can contact the Asgardeo team at **asgardeo-help@wso2.com** . Note that you need to send the request from an administrator account." %} +If you require any of the extended branding capabilities (explained below), you can contact the WSO2 Identity Platform team at **asgardeo-help@wso2.com** . Note that you need to send the request from an administrator account." %} {% include "../../../../includes/guides/branding/configure-ui-branding.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/branding/customize-email-templates.md b/en/asgardeo/docs/guides/branding/customize-email-templates.md index b21d43064a..afec3498df 100644 --- a/en/asgardeo/docs/guides/branding/customize-email-templates.md +++ b/en/asgardeo/docs/guides/branding/customize-email-templates.md @@ -1,14 +1,14 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set email_template_note = "!!! note This feature was onboarded on 20th September 2022. Email template branding will not be applied to email templates of organizations created before this date. - If you need to apply organization branding to your emails, contact the Asgardeo team at **asgardeo-help@wso2.com**. + If you need to apply organization branding to your emails, contact the WSO2 Identity Platform team at **asgardeo-help@wso2.com**. " %} {% set customize_email_settings = "## Customize email settings -You can customize the default settings set by Asgardeo for email parameters such as `from address` and `replyTo` by contacting the Asgardeo team at **asgardeo-help@wso2.com**." %} +You can customize the default settings set by WSO2 Identity Platform for email parameters such as `from address` and `replyTo` by contacting the WSO2 Identity Platform team at **asgardeo-help@wso2.com**." %} {% set email_templates_api_path = "email-template" %} diff --git a/en/asgardeo/docs/guides/branding/customize-sms-templates.md b/en/asgardeo/docs/guides/branding/customize-sms-templates.md index 3c6324ee9f..ccc4834536 100644 --- a/en/asgardeo/docs/guides/branding/customize-sms-templates.md +++ b/en/asgardeo/docs/guides/branding/customize-sms-templates.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set notification_templates_api_path = "notification-templates" %} diff --git a/en/asgardeo/docs/guides/identity-verification/add-identity-verification-with-onfido.md b/en/asgardeo/docs/guides/identity-verification/add-identity-verification-with-onfido.md index 7cf055bcbe..632f3573fd 100644 --- a/en/asgardeo/docs/guides/identity-verification/add-identity-verification-with-onfido.md +++ b/en/asgardeo/docs/guides/identity-verification/add-identity-verification-with-onfido.md @@ -1,3 +1,3 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/identity-verification/add-identity-verification-with-onfido.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/index.md b/en/asgardeo/docs/guides/index.md index b03561e75a..ffa6d36e9a 100644 --- a/en/asgardeo/docs/guides/index.md +++ b/en/asgardeo/docs/guides/index.md @@ -1,3 +1,3 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set myacc_doc_url = "your-asgardeo" %} {% include "../../../includes/guides/index.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/monitoring/asgardeo-events.md b/en/asgardeo/docs/guides/monitoring/asgardeo-events.md index e77b97f3d0..2f4ce1feb2 100644 --- a/en/asgardeo/docs/guides/monitoring/asgardeo-events.md +++ b/en/asgardeo/docs/guides/monitoring/asgardeo-events.md @@ -1,11 +1,11 @@ -# Asgardeo events +# WSO2 Identity Platform events -Asgardeo triggers events corresponding to the various user interactions in your Asgardeo organization. You can configure Asgardeo to publish these events to WSO2's integration platform, [Choreo](https://wso2.com/choreo/){:target="_blank"}. From there, you can define custom business logic that can be executed when an event occurs. +WSO2 Identity Platform triggers events corresponding to the various user interactions in your WSO2 Identity Platform organization. You can configure WSO2 Identity Platform to publish these events to WSO2's integration platform, [Choreo](https://wso2.com/choreo/){:target="_blank"}. From there, you can define custom business logic that can be executed when an event occurs. -Asgardeo publishes the following events under three main categories. +WSO2 Identity Platform publishes the following events under three main categories. !!! Important - All events published by Asgardeo are end-to-end encrypted until Choreo processes and decrypts them. + All events published by WSO2 Identity Platform are end-to-end encrypted until Choreo processes and decrypts them. - **Login events** - Events related to login flows. @@ -32,48 +32,48 @@ Asgardeo publishes the following events under three main categories. - **[Confirm self-signup event](#confirm-self-signup-event)**: Published when a user completes account verification during self-sign-up. -## Configure Asgardeo to publish events +## Configure WSO2 Identity Platform to publish events -Follow the steps below to configure event publishing for Asgardeo. +Follow the steps below to configure event publishing for WSO2 Identity Platform. -1. On the Asgardeo Console, go to **Monitoring** > **Events**. +1. On the WSO2 Identity Platform Console, go to **Monitoring** > **Events**. 2. Select the events that you wish to publish to Choreo and click **Update**. - {: width="600" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} + {: width="600" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} !!! info Alternatively, you can invoke the **Event Configuration Management** API to configure event publishing. See the API Documentation to learn more. -## Implement business use cases for Asgardeo events +## Implement business use cases for WSO2 Identity Platform events -Follow the steps below to define a business logic that will trigger when an Asgardeo event occurs. +Follow the steps below to define a business logic that will trigger when an WSO2 Identity Platform event occurs. ### Prerequisite - You need to have a GitHub repository to host the business logic. -- Download [Ballerina](https://ballerina.io/downloads/){:target="_blank"}, the programming language used to define business logic for Asgardeo events. +- Download [Ballerina](https://ballerina.io/downloads/){:target="_blank"}, the programming language used to define business logic for WSO2 Identity Platform events. ### Define the business logic -Let's set up a sample business use case such that whenever a registration event is generated in Asgardeo, it gets logged in the Choreo console. +Let's set up a sample business use case such that whenever a registration event is generated in WSO2 Identity Platform, it gets logged in the Choreo console. Follow the steps below to programmatically define the business logic. 1. Create a new Ballerina package. Learn how to do so in the [Ballerina documentation](https://ballerina.io/learn/get-started/){:target="_blank"}. -2. Navigate to the **Ballerina.toml** file and rename the organization name to that of your Asgardeo organization. +2. Navigate to the **Ballerina.toml** file and rename the organization name to that of your WSO2 Identity Platform organization. 3. Navigate to your **main.bal** file and define the business logic. - The following is a sample code that logs the event in the Choreo console, when a registration event is generated in Asgardeo. + The following is a sample code that logs the event in the Choreo console, when a registration event is generated in WSO2 Identity Platform. ``` java import ballerinax/trigger.asgardeo; @@ -114,10 +114,10 @@ Follow the steps below to programmatically define the business logic. Follow the steps below to create and deploy a webhook in Choreo. -1. Navigate to [Choreo](https://console.choreo.dev/login){:target="_blank"} and if you don't have one already, create an organization with the same name and email address you used to create your Asgardeo organization. +1. Navigate to [Choreo](https://console.choreo.dev/login){:target="_blank"} and if you don't have one already, create an organization with the same name and email address you used to create your WSO2 Identity Platform organization. !!! info - Organizations in Asgardeo and Choreo synchronize based on their names. + Organizations in WSO2 Identity Platform and Choreo synchronize based on their names. 2. Select a project from the **Project** dropdown. @@ -147,7 +147,7 @@ Follow the steps below to create and deploy a webhook in Choreo. Once the webhook is deployed in Choreo, follow the steps below to try it out. -1. Login to the Asgardeo Console and go to **User Management** > **Users**. +1. Login to the WSO2 Identity Platform Console and go to **User Management** > **Users**. 2. Click **Add User** and create a new user. @@ -158,13 +158,13 @@ Once the webhook is deployed in Choreo, follow the steps below to try it out. 4. Find the **Logs** tab and filter for the logged add user event. - {: width="600" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} + {: width="600" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} -## Payload of an Asgardeo event +## Payload of an WSO2 Identity Platform event -The payload of an Asgardeo event that is sent to Choreo consists of the following data objects: -- **Security Data** object - The security data object is common to all Asgardeo events. This contains the following security metadata about the event. +The payload of an WSO2 Identity Platform event that is sent to Choreo consists of the following data objects: +- **Security Data** object - The security data object is common to all WSO2 Identity Platform events. This contains the following security metadata about the event.New to Ballerina?
-Learn more about the **Asgardeo trigger** module and how to program business logic for different types of events in the Ballerina documentation.
+Learn more about the **WSO2 Identity Platform trigger** module and how to program business logic for different types of events in the Ballerina documentation.
@@ -202,18 +202,18 @@ The payload of an Asgardeo event that is sent to Choreo consists of the followin ``` js { - "iss": "Asgardeo", + "iss": "WSO2 Identity Platform", "jti": "3b69b103-fa6c-424a-bbf4-a974d0c2d2a3", "iat": 1659732032884, "aud": "https://websubhub/topics/myorg/REGISTRATIONS" } ``` -- **Event Data** object - The event data object contains the details of the event (or the user action). Learn more about event data in the Event data of Asgardeo events section. +- **Event Data** object - The event data object contains the details of the event (or the user action). Learn more about event data in the Event data of WSO2 Identity Platform events section. -## Event data of Asgardeo events +## Event data of WSO2 Identity Platform events -This section describes all the Asgardeo events that can be published to Choreo and their respective event payloads. +This section describes all the WSO2 Identity Platform events that can be published to Choreo and their respective event payloads. ### Login events diff --git a/en/asgardeo/docs/guides/monitoring/index.md b/en/asgardeo/docs/guides/monitoring/index.md index aa37a89c64..ecc2c382c5 100644 --- a/en/asgardeo/docs/guides/monitoring/index.md +++ b/en/asgardeo/docs/guides/monitoring/index.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/monitoring/index.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/monitoring/pii-in-asgardeo-logs.md b/en/asgardeo/docs/guides/monitoring/pii-in-asgardeo-logs.md index 819d9e8db7..8a0a9b3161 100644 --- a/en/asgardeo/docs/guides/monitoring/pii-in-asgardeo-logs.md +++ b/en/asgardeo/docs/guides/monitoring/pii-in-asgardeo-logs.md @@ -1,9 +1,9 @@ # Potential risks of including PII in query parameters -Including Personally Identifiable Information (PII) in query parameters can pose security and privacy risks. These can be in the form of plain text or embedded in `jwt` tokens. Asgardeo logs these query parameters to uphold security, compliance, and auditing standards, as well as to fulfill other legal obligations. +Including Personally Identifiable Information (PII) in query parameters can pose security and privacy risks. These can be in the form of plain text or embedded in `jwt` tokens. WSO2 Identity Platform logs these query parameters to uphold security, compliance, and auditing standards, as well as to fulfill other legal obligations. Therefore, any PII sent as query parameters will be logged in our server access logs. This means that sensitive information, such as names, email addresses, or other personal data, may be recorded and stored as part of routine system operations. To mitigate the risk of exposing PII, **we strongly recommend encrypting such information when sending as query parameters or consider sending such information in the request body**. -By using Asgardeo, you acknowledge and understand these potential risks, and you are encouraged to follow the guidance provided here to ensure data security and privacy for your data. If you have any questions or require guidance on handling sensitive information securely within our system, reach out to our support team at `asgardeo-help@wso2.com`. \ No newline at end of file +By using WSO2 Identity Platform, you acknowledge and understand these potential risks, and you are encouraged to follow the guidance provided here to ensure data security and privacy for your data. If you have any questions or require guidance on handling sensitive information securely within our system, reach out to our support team at `asgardeo-help@wso2.com`. \ No newline at end of file diff --git a/en/asgardeo/docs/guides/notification-channels/configure-email-provider.md b/en/asgardeo/docs/guides/notification-channels/configure-email-provider.md index b0c5bfd3b0..b8e74fc033 100644 --- a/en/asgardeo/docs/guides/notification-channels/configure-email-provider.md +++ b/en/asgardeo/docs/guides/notification-channels/configure-email-provider.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} # Configure Email Provider diff --git a/en/asgardeo/docs/guides/notification-channels/configure-push-provider.md b/en/asgardeo/docs/guides/notification-channels/configure-push-provider.md index 32b1e304f0..5e747bb2f7 100644 --- a/en/asgardeo/docs/guides/notification-channels/configure-push-provider.md +++ b/en/asgardeo/docs/guides/notification-channels/configure-push-provider.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} -{% set support_platforms = "Asgardeo supports **Firebase Cloud Messaging (FCM)** as a push notification provider." %} +{% set support_platforms = "WSO2 Identity Platform supports **Firebase Cloud Messaging (FCM)** as a push notification provider." %} {% include "../../../../includes/guides/notification-channels/configure-push-provider.md" %} diff --git a/en/asgardeo/docs/guides/notification-channels/configure-sms-provider.md b/en/asgardeo/docs/guides/notification-channels/configure-sms-provider.md index 2abc8ac27e..c5beeb9700 100644 --- a/en/asgardeo/docs/guides/notification-channels/configure-sms-provider.md +++ b/en/asgardeo/docs/guides/notification-channels/configure-sms-provider.md @@ -1,3 +1,3 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/notification-channels/configure-sms-provider.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/organization-insights.md b/en/asgardeo/docs/guides/organization-insights.md index 27decc8342..452d6b1024 100644 --- a/en/asgardeo/docs/guides/organization-insights.md +++ b/en/asgardeo/docs/guides/organization-insights.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../includes/guides/organization-insights.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/user-accounts/account-login/configure-login-identifiers.md b/en/asgardeo/docs/guides/user-accounts/account-login/configure-login-identifiers.md index 3fc8029d84..cdb7601b67 100644 --- a/en/asgardeo/docs/guides/user-accounts/account-login/configure-login-identifiers.md +++ b/en/asgardeo/docs/guides/user-accounts/account-login/configure-login-identifiers.md @@ -3,19 +3,19 @@ !!! note The feature is in the Beta stage. We are working on adding more capabilities for this feature. -You can now configure alternative login identifiers so that the users of your Asgardeo organization have the capability to use these identifiers to log in. +You can now configure alternative login identifiers so that the users of your WSO2 Identity Platform organization have the capability to use these identifiers to log in. !!! note The primary login identifier is the attribute you configure as your username. Learn more about [configuring username validation]({{base_path}}/guides/user-accounts/account-login/username-validation/). -Asgardeo allows admins to assign the following attributes as alternative login identifiers of the organization: +WSO2 Identity Platform allows admins to assign the following attributes as alternative login identifiers of the organization: - `Email` - `Mobile` To configure alternative login identifiers for your organization: -1. On the Asgardeo Console, go to **Login & Registration**. +1. On the WSO2 Identity Platform Console, go to **Login & Registration**. 2. Under **Login Identifier**, click on **Alternative Login Identifier**. @@ -24,7 +24,7 @@ To configure alternative login identifiers for your organization: {: width="700" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} !!! note - - Ensure that every user within your organization has a unique value assigned to the chosen login identifiers. For new users, Asgardeo will ensure it's uniqueness. + - Ensure that every user within your organization has a unique value assigned to the chosen login identifiers. For new users, WSO2 Identity Platform will ensure it's uniqueness. - If you have chosen `Email` as the [username type]({{base_path}}/guides/user-accounts/account-login/username-validation/), it automatically becomes the primary login identifier. Therefore, configuring it as an alternative login identifier will be disabled. diff --git a/en/asgardeo/docs/guides/user-accounts/account-login/username-validation.md b/en/asgardeo/docs/guides/user-accounts/account-login/username-validation.md index 6eeca589ad..a180311d34 100644 --- a/en/asgardeo/docs/guides/user-accounts/account-login/username-validation.md +++ b/en/asgardeo/docs/guides/user-accounts/account-login/username-validation.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../../includes/guides/user-accounts/account-login/username-validation.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/user-accounts/account-security/bot-detection.md b/en/asgardeo/docs/guides/user-accounts/account-security/bot-detection.md index 9f1d69a6b6..04991ca012 100644 --- a/en/asgardeo/docs/guides/user-accounts/account-security/bot-detection.md +++ b/en/asgardeo/docs/guides/user-accounts/account-security/bot-detection.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../../includes/guides/user-accounts/account-security/bot-detection.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/user-accounts/account-security/login-attempts-security.md b/en/asgardeo/docs/guides/user-accounts/account-security/login-attempts-security.md index 760df6b436..47849a0004 100644 --- a/en/asgardeo/docs/guides/user-accounts/account-security/login-attempts-security.md +++ b/en/asgardeo/docs/guides/user-accounts/account-security/login-attempts-security.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../../includes/guides/user-accounts/account-security/login-attempts-security.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/user-accounts/account-security/password-validation.md b/en/asgardeo/docs/guides/user-accounts/account-security/password-validation.md index 22519a3d71..c01ae0d4e4 100644 --- a/en/asgardeo/docs/guides/user-accounts/account-security/password-validation.md +++ b/en/asgardeo/docs/guides/user-accounts/account-security/password-validation.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../../includes/guides/user-accounts/account-security/password-validation.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/user-accounts/index.md b/en/asgardeo/docs/guides/user-accounts/index.md index 80ed8cbd45..ad2d4e2dae 100644 --- a/en/asgardeo/docs/guides/user-accounts/index.md +++ b/en/asgardeo/docs/guides/user-accounts/index.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/user-accounts/index.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/user-self-service/build-self-service-capabilities.md b/en/asgardeo/docs/guides/user-self-service/build-self-service-capabilities.md index c126750ab3..baf3d3fc71 100644 --- a/en/asgardeo/docs/guides/user-self-service/build-self-service-capabilities.md +++ b/en/asgardeo/docs/guides/user-self-service/build-self-service-capabilities.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set scim_list_user = "scim2/#/paths/Me/get" %} diff --git a/en/asgardeo/docs/guides/user-self-service/change-password.md b/en/asgardeo/docs/guides/user-self-service/change-password.md index 81d410328d..dab6c1c72a 100644 --- a/en/asgardeo/docs/guides/user-self-service/change-password.md +++ b/en/asgardeo/docs/guides/user-self-service/change-password.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/user-self-service/change-password.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/user-self-service/configure-self-service-portal.md b/en/asgardeo/docs/guides/user-self-service/configure-self-service-portal.md index a41a3c5509..04f703bbe8 100644 --- a/en/asgardeo/docs/guides/user-self-service/configure-self-service-portal.md +++ b/en/asgardeo/docs/guides/user-self-service/configure-self-service-portal.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set my_account_link = "
@@ -61,7 +61,7 @@ This option has to be enabled for the organization. If enabled, administrators c To enable this option, -1. On the Asgardeo Console, go to **Console Settings** > **Administrators**. +1. On the WSO2 Identity Platform Console, go to **Console Settings** > **Administrators**. 2. Click the settings icon next to **Add Administrator** to open the **Administrator Settings** page. @@ -76,24 +76,24 @@ To assign users the administrator role, 1. On the **Console Settings** > **Administrators** page, click **+Add Administrator > Add Existing User**. 2. Select the user's username and the **Administrator** role and click **Add**. -The new administrator can now access the Asgardeo Console using the following URL: +The new administrator can now access the WSO2 Identity Platform Console using the following URL: ``` https://console.asgardeo.io/t/{organization_name} ``` !!! note - Currently, only privileged users onboarded from the internal user store and remote user stores can log in to the Asgardeo Console. + Currently, only privileged users onboarded from the internal user store and remote user stores can log in to the WSO2 Identity Platform Console. ## View administrators To view the administrators of your organization: -On the Asgardeo Console, go to **Console Settings > Administrators**. You will see the list of administrators presented in two tabs as follow. +On the WSO2 Identity Platform Console, go to **Console Settings > Administrators**. You will see the list of administrators presented in two tabs as follow.https://myaccount.asgardeo.io/t/{organization_name}diff --git a/en/asgardeo/docs/guides/user-self-service/discover-applications.md b/en/asgardeo/docs/guides/user-self-service/discover-applications.md index 748f4b85e9..36e53e8b11 100644 --- a/en/asgardeo/docs/guides/user-self-service/discover-applications.md +++ b/en/asgardeo/docs/guides/user-self-service/discover-applications.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/user-self-service/discover-applications.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/user-self-service/enable-totp.md b/en/asgardeo/docs/guides/user-self-service/enable-totp.md index 4710b173a8..8f3f993c5f 100644 --- a/en/asgardeo/docs/guides/user-self-service/enable-totp.md +++ b/en/asgardeo/docs/guides/user-self-service/enable-totp.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/user-self-service/enable-totp.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/user-self-service/export-profile-information.md b/en/asgardeo/docs/guides/user-self-service/export-profile-information.md index b593c670cf..2c7b12e045 100644 --- a/en/asgardeo/docs/guides/user-self-service/export-profile-information.md +++ b/en/asgardeo/docs/guides/user-self-service/export-profile-information.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/user-self-service/export-profile-information.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/user-self-service/index.md b/en/asgardeo/docs/guides/user-self-service/index.md index 6a8e80e3fa..bc95493cbd 100644 --- a/en/asgardeo/docs/guides/user-self-service/index.md +++ b/en/asgardeo/docs/guides/user-self-service/index.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/user-self-service/index.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/user-self-service/manage-backup-codes.md b/en/asgardeo/docs/guides/user-self-service/manage-backup-codes.md index 1e954ff730..be9e009c60 100644 --- a/en/asgardeo/docs/guides/user-self-service/manage-backup-codes.md +++ b/en/asgardeo/docs/guides/user-self-service/manage-backup-codes.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/user-self-service/manage-backup-codes.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/user-self-service/manage-consents.md b/en/asgardeo/docs/guides/user-self-service/manage-consents.md index eb98474423..7def25e693 100644 --- a/en/asgardeo/docs/guides/user-self-service/manage-consents.md +++ b/en/asgardeo/docs/guides/user-self-service/manage-consents.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/user-self-service/manage-consents.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/user-self-service/manage-linked-accounts.md b/en/asgardeo/docs/guides/user-self-service/manage-linked-accounts.md index 90d51af109..025bcfd5d8 100644 --- a/en/asgardeo/docs/guides/user-self-service/manage-linked-accounts.md +++ b/en/asgardeo/docs/guides/user-self-service/manage-linked-accounts.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/user-self-service/manage-linked-accounts.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/user-self-service/manage-login-sessions.md b/en/asgardeo/docs/guides/user-self-service/manage-login-sessions.md index 90849a5545..7e3815cca6 100644 --- a/en/asgardeo/docs/guides/user-self-service/manage-login-sessions.md +++ b/en/asgardeo/docs/guides/user-self-service/manage-login-sessions.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/user-self-service/manage-login-sessions.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/user-self-service/register-passkey.md b/en/asgardeo/docs/guides/user-self-service/register-passkey.md index 1d8d6a2264..1ff28c6f87 100644 --- a/en/asgardeo/docs/guides/user-self-service/register-passkey.md +++ b/en/asgardeo/docs/guides/user-self-service/register-passkey.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/user-self-service/register-passkey.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/user-self-service/register-push-notification-device.md b/en/asgardeo/docs/guides/user-self-service/register-push-notification-device.md index b1c95c2034..81197881ca 100644 --- a/en/asgardeo/docs/guides/user-self-service/register-push-notification-device.md +++ b/en/asgardeo/docs/guides/user-self-service/register-push-notification-device.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/user-self-service/register-push-notification-device.md" %} diff --git a/en/asgardeo/docs/guides/user-self-service/self-register.md b/en/asgardeo/docs/guides/user-self-service/self-register.md index 7f09183629..f883a84b96 100644 --- a/en/asgardeo/docs/guides/user-self-service/self-register.md +++ b/en/asgardeo/docs/guides/user-self-service/self-register.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/user-self-service/self-register.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/user-self-service/update-profile-info.md b/en/asgardeo/docs/guides/user-self-service/update-profile-info.md index d3f574cb58..dcadcea315 100644 --- a/en/asgardeo/docs/guides/user-self-service/update-profile-info.md +++ b/en/asgardeo/docs/guides/user-self-service/update-profile-info.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/user-self-service/update-profile-info.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/user-self-service/user-password-recovery.md b/en/asgardeo/docs/guides/user-self-service/user-password-recovery.md index c1d1e67b25..609e78d23d 100644 --- a/en/asgardeo/docs/guides/user-self-service/user-password-recovery.md +++ b/en/asgardeo/docs/guides/user-self-service/user-password-recovery.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/user-self-service/user-password-recovery.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/users/index.md b/en/asgardeo/docs/guides/users/index.md index df62319c95..4710c30bbc 100644 --- a/en/asgardeo/docs/guides/users/index.md +++ b/en/asgardeo/docs/guides/users/index.md @@ -1,22 +1,22 @@ # User management -The users in Asgardeo are the digital representations of the identities of physical users who interact with your -organization. With Asgardeo, the identity lifecycle of each of these users can be easily managed by the admins of the +The users in WSO2 Identity Platform are the digital representations of the identities of physical users who interact with your +organization. With WSO2 Identity Platform, the identity lifecycle of each of these users can be easily managed by the admins of the organization. -The admins can grant users access to resources in your organization and control user access. Admins can also manage various user operations via the Asgardeo Console and SCIM APIs. +The admins can grant users access to resources in your organization and control user access. Admins can also manage various user operations via the WSO2 Identity Platform Console and SCIM APIs. -Shown below are some main user management capabilities available in Asgardeo. +Shown below are some main user management capabilities available in WSO2 Identity Platform. {: width="800" style="display: block; margin: 0;"} ## User accounts -Asgardeo supports the following types of user accounts based on their relationship to the organization. +WSO2 Identity Platform supports the following types of user accounts based on their relationship to the organization. ### Owner -The owner has all the administrative rights in the organization. The owner can access the Asgardeo console and manage the organization using the following actions: +The owner has all the administrative rights in the organization. The owner can access the WSO2 Identity Platform console and manage the organization using the following actions: - Onboard users - Create organizations @@ -43,14 +43,14 @@ Refer [Manage users]({{base_path}}/guides/users/manage-users/) for more informat ### Comparing User Accounts -The following table compares the different user account types available in Asgardeo. +The following table compares the different user account types available in WSO2 Identity Platform. -Based on your requirements, you can choose user types and create them via the Asgardeo Console. +Based on your requirements, you can choose user types and create them via the WSO2 Identity Platform Console. The source of the user account determines which entity manages the user's credentials and details. -- **Accounts managed by Asgardeo** can persist across multiple organizations. That is, the same user account can be associated with other organizations as an owner or an administrator. When removed from one organization, these associations with other organizations continue to persist. -- **Accounts managed by an organization** are confined to that organization. When removed from that organization, the account is completely deleted from Asgardeo. +- **Accounts managed by WSO2 Identity Platform** can persist across multiple organizations. That is, the same user account can be associated with other organizations as an owner or an administrator. When removed from one organization, these associations with other organizations continue to persist. +- **Accounts managed by an organization** are confined to that organization. When removed from that organization, the account is completely deleted from WSO2 Identity Platform.
@@ -60,8 +60,8 @@ The source of the user account determines which entity manages the user's creden
@@ -45,7 +45,7 @@ Existing administrators can onboard other administrators by sending them email iCapabilities - Owner -Asgardeo +Owner +WSO2 Identity Platform - Administrator -Asgardeo +Administrator +WSO2 Identity Platform By default, administrators are assigned all administration capabilities: Role -Users can be assigned one or more default roles. For details on the available user roles and the permissions assigned to them, see [Asgardeo User Roles]({{base_path}}/references/user-management/user-roles/). +Users can be assigned one or more default roles. For details on the available user roles and the permissions assigned to them, see [WSO2 Identity Platform User Roles]({{base_path}}/references/user-management/user-roles/). Role -The Administrator role is assigned by default. For details on the available user roles and the permissions assigned to them, see [Asgardeo User Roles]({{base_path}}/references/user-management/user-roles/). +The Administrator role is assigned by default. For details on the available user roles and the permissions assigned to them, see [WSO2 Identity Platform User Roles]({{base_path}}/references/user-management/user-roles/). -- These IP addresses facilitate outbound communication from Asgardeo's infrastructure. +- These IP addresses facilitate outbound communication from WSO2 Identity Platform's infrastructure. - If you have firewalls or network security policies in place, ensure these IPs are allowlisted to maintain seamless connectivity. diff --git a/en/asgardeo/docs/references/authorization-policies-for-apps.md b/en/asgardeo/docs/references/authorization-policies-for-apps.md index 6a3a5e16da..6a5c5627e3 100644 --- a/en/asgardeo/docs/references/authorization-policies-for-apps.md +++ b/en/asgardeo/docs/references/authorization-policies-for-apps.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../includes/references/authorization-policies-for-apps.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/references/conditional-auth/api-reference.md b/en/asgardeo/docs/references/conditional-auth/api-reference.md index f8e14ee277..4bc6423684 100644 --- a/en/asgardeo/docs/references/conditional-auth/api-reference.md +++ b/en/asgardeo/docs/references/conditional-auth/api-reference.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/references/conditional-auth/api-reference.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/references/data-residency-in-asgardeo.md b/en/asgardeo/docs/references/data-residency-in-asgardeo.md index b0b5549fda..5bd5c20822 100644 --- a/en/asgardeo/docs/references/data-residency-in-asgardeo.md +++ b/en/asgardeo/docs/references/data-residency-in-asgardeo.md @@ -1,12 +1,12 @@ -# Data residency in Asgardeo +# Data residency in WSO2 Identity Platform Data residency is the geographical (or regulatory) boundary where your data is stored and processed. -{: width="700"} +{: width="700"} ## Data centers -Asgardeo uses two regional data centers to store data: +WSO2 Identity Platform uses two regional data centers to store data:
- Asgardeo -This includes administrators whose identity is managed by Asgardeo. +WSO2 Identity Platform +This includes administrators whose identity is managed by WSO2 Identity Platform. {organization_name} organization @@ -110,7 +110,7 @@ On the Asgardeo Console, go to **Console Settings > Administrators**. You will s To delete an administrator: -1. On the Asgardeo Console, click **Console Settings** > **Administrators**. +1. On the WSO2 Identity Platform Console, click **Console Settings** > **Administrators**. 2. Click **Delete** for the administrator you want to remove. 3. Select the checkbox to confirm your action. 4. Click **Confirm**. diff --git a/en/asgardeo/docs/guides/users/manage-groups.md b/en/asgardeo/docs/guides/users/manage-groups.md index 233980bb0b..0fb3306c15 100644 --- a/en/asgardeo/docs/guides/users/manage-groups.md +++ b/en/asgardeo/docs/guides/users/manage-groups.md @@ -7,16 +7,16 @@ Applications can get details about groups a user belongs to as a user attribute ## Onboard a group There are two ways to onboard a group: -- An administrator can onboard users from an on-premise user store by [connecting a remote user store to Asgardeo]({{base_path}}/guides/users/user-stores/configure-a-user-store/). +- An administrator can onboard users from an on-premise user store by [connecting a remote user store to WSO2 Identity Platform]({{base_path}}/guides/users/user-stores/configure-a-user-store/). !!! note If the remote user store access type is read-only, you cannot update the user groups onboarded from this read-only user store. -- Administrators can add groups via the Asgardeo Console. +- Administrators can add groups via the WSO2 Identity Platform Console. -Let's look at how administrators can onboard groups from the Asgardeo Console. +Let's look at how administrators can onboard groups from the WSO2 Identity Platform Console. -1. On the Asgardeo Console, go to **User Management** > **Groups**. +1. On the WSO2 Identity Platform Console, go to **User Management** > **Groups**. 2. Click **New Group** and provide the following details. - **Group Name:** A unique name to identify the group. @@ -31,7 +31,7 @@ Users can be assigned to groups. Admins can allow/restrict access to resources b To assign users to groups: -1. On the Asgardeo Console, go to **User Management** > **Groups**. +1. On the WSO2 Identity Platform Console, go to **User Management** > **Groups**. 2. Select the group to assign the user. 3. Click **Edit** and navigate to **Users**. @@ -45,7 +45,7 @@ To assign users to groups: To remove users from groups: -1. On the Asgardeo Console, go to **User Management** > **Groups**. +1. On the WSO2 Identity Platform Console, go to **User Management** > **Groups**. 2. Select the group to remove the user. 3. Click the **Edit** icon and navigate to **Users**. @@ -59,7 +59,7 @@ You can assign groups to application roles and grant permission for the group's To assign a group to a role: -1. On the Asgardeo Console, go to **User Management** > **Groups**. +1. On the WSO2 Identity Platform Console, go to **User Management** > **Groups**. 2. Go to the **Roles** tab and click **+ Assign Roles**. 3. Expand the application to which the required roles belong. 4. Select the application role/s you wish to add to the group. @@ -69,19 +69,19 @@ To assign a group to a role: 5. Click **Save** to assign the group to the selected application role. ## Delete a group -An administrator can delete groups via the Asgardeo Console. +An administrator can delete groups via the WSO2 Identity Platform Console. To delete a group: -1. On the Asgardeo Console, go to **User Management** > **Groups**. +1. On the WSO2 Identity Platform Console, go to **User Management** > **Groups**. 2. Click the trash icon next to the group you wish to delete. 3. Select the checkbox and confirm your action. ## View remote user store groups -Once you connect a remote user store to Asgardeo, you can view the onboarded groups and the members of the groups. +Once you connect a remote user store to WSO2 Identity Platform, you can view the onboarded groups and the members of the groups. To view the onboarded groups: -1. On the Asgardeo Console, go to **User Management** > **Groups**. +1. On the WSO2 Identity Platform Console, go to **User Management** > **Groups**. 2. Select the preferred user store from the drop-down menu. !!! note - Remote groups are read-only in the Asgardeo console. Administrators can only view the group details and its members. \ No newline at end of file + Remote groups are read-only in the WSO2 Identity Platform console. Administrators can only view the group details and its members. \ No newline at end of file diff --git a/en/asgardeo/docs/guides/users/manage-sessions.md b/en/asgardeo/docs/guides/users/manage-sessions.md index 61affdf5b0..84476eeee0 100644 --- a/en/asgardeo/docs/guides/users/manage-sessions.md +++ b/en/asgardeo/docs/guides/users/manage-sessions.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/guides/users/manage-sessions.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/users/manage-users.md b/en/asgardeo/docs/guides/users/manage-users.md index 03d48243b2..ce12d836cd 100644 --- a/en/asgardeo/docs/guides/users/manage-users.md +++ b/en/asgardeo/docs/guides/users/manage-users.md @@ -198,7 +198,7 @@ To reset the password: **Using the API** -You can also use Asgardeo's [SCIM API]({{base_path}}/apis/scim2/#tag/Users-Endpoint/operation/patchUser) to initiate the admin initiated password recovery flow. +You can also use WSO2 Identity Platform's [SCIM API]({{base_path}}/apis/scim2/#tag/Users-Endpoint/operation/patchUser) to initiate the admin initiated password recovery flow. 1. [Get an access token]({{base_path}}/apis/authentication/#get-an-access-token) with the `internal_user_mgt_update` scope. diff --git a/en/asgardeo/docs/guides/users/migrate-users/index.md b/en/asgardeo/docs/guides/users/migrate-users/index.md index b13831d3f2..3c8bc2ff16 100644 --- a/en/asgardeo/docs/guides/users/migrate-users/index.md +++ b/en/asgardeo/docs/guides/users/migrate-users/index.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../../includes/guides/users/migrate-users/index.md" %} diff --git a/en/asgardeo/docs/guides/users/migrate-users/migrate-passwords.md b/en/asgardeo/docs/guides/users/migrate-users/migrate-passwords.md index fb4bf55795..2712748c55 100644 --- a/en/asgardeo/docs/guides/users/migrate-users/migrate-passwords.md +++ b/en/asgardeo/docs/guides/users/migrate-users/migrate-passwords.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../../includes/guides/users/migrate-users/migrate-passwords.md" %} diff --git a/en/asgardeo/docs/guides/users/migrate-users/migrate-users.md b/en/asgardeo/docs/guides/users/migrate-users/migrate-users.md index 849858b2ab..b2b190d714 100644 --- a/en/asgardeo/docs/guides/users/migrate-users/migrate-users.md +++ b/en/asgardeo/docs/guides/users/migrate-users/migrate-users.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../../includes/guides/users/migrate-users/migrate-users.md" %} diff --git a/en/asgardeo/docs/guides/users/user-stores/configure-a-user-store.md b/en/asgardeo/docs/guides/users/user-stores/configure-a-user-store.md index 4923b12b2d..df65ed6833 100644 --- a/en/asgardeo/docs/guides/users/user-stores/configure-a-user-store.md +++ b/en/asgardeo/docs/guides/users/user-stores/configure-a-user-store.md @@ -1,14 +1,14 @@ # Connect a remote user store -Asgardeo allows you to connect a remote user store and onboard users and groups from it. The user store connection can either be with read-only or read/write permissions. Administrators can then start managing access to business applications in Asgardeo for these users and groups. This guide explains how you can set up a remote user store for your Asgardeo organization. +WSO2 Identity Platform allows you to connect a remote user store and onboard users and groups from it. The user store connection can either be with read-only or read/write permissions. Administrators can then start managing access to business applications in WSO2 Identity Platform for these users and groups. This guide explains how you can set up a remote user store for your WSO2 Identity Platform organization. ## User store connections -Asgardeo supports the following user store connections. +WSO2 Identity Platform supports the following user store connections. ### Optimized user store connection (recommended) -Asgardeo has introduced **optimized user store connections**, designed for high scalability and performance. At the moment, it supports **read-only** user stores and can be used to authenticate users and retrieve attributes. This connection is continuously evolving and will support a wide range of use cases in the future. +WSO2 Identity Platform has introduced **optimized user store connections**, designed for high scalability and performance. At the moment, it supports **read-only** user stores and can be used to authenticate users and retrieve attributes. This connection is continuously evolving and will support a wide range of use cases in the future. If this connection's capabilities meet your organization's requirements, we highly recommend that you use the optimized connection instead of the classic connection. @@ -26,21 +26,21 @@ The optimized user store connection is the recommended choice, though its capabi !!! note "Switch classic connections from read-only to read/write" - If you have connected a classic user store before 7th February 2023, you will only have **read-only** access for the user store. If you need **read/write** access for your user store in Asgardeo, + If you have connected a classic user store before 7th February 2023, you will only have **read-only** access for the user store. If you need **read/write** access for your user store in WSO2 Identity Platform, 1. Delete the existing remote user store. 2. [Register a classic user store](#register-a-remote-user-store) again with Read/Write access type. Make sure to select the classic user store path. 3. [Set up the remote user store](#set-up-the-remote-user-store) with the latest user store agent. -## Register and configure a user store in Asgardeo +## Register and configure a user store in WSO2 Identity Platform -The following guides explain how you can register and set up a remote user store for your Asgardeo organization. +The following guides explain how you can register and set up a remote user store for your WSO2 Identity Platform organization. ### Prerequisites Ensure your system has the following before you proceed. -- An on-premise user store. Currently, Asgardeo supports: +- An on-premise user store. Currently, WSO2 Identity Platform supports: - Lightweight Directory Access Protocol (LDAP) - Active Directory (AD) @@ -94,11 +94,11 @@ Ensure your system has the following before you proceed. To configure a remote user store for your organization: -1. On the Asgardeo Console, go to **User Attributes & Stores** > **User Stores**. +1. On the WSO2 Identity Platform Console, go to **User Attributes & Stores** > **User Stores**. 2. Click **Connect userstore** to open the following: - {: width="600" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} + {: width="600" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} 3. If the [optimized connection](#optimized-user-store-connection-recommended) supports your use case, this is the recommended choice. If not, click **Classic User Store Connection** instead. @@ -246,7 +246,7 @@ After registering the user store, you'll be redirected to the **Setup Guide** of Refer [remote agent properties]({{base_path}}/references/remote-user-store/remote-user-store-properties/) for the complete list of agent configurations. - 4. Return to the Asgardeo Console and click **Generate Token** to create an installation token. The installation token is essential to run the user store agent. The token can be configured in one of the following ways. + 4. Return to the WSO2 Identity Platform Console and click **Generate Token** to create an installation token. The installation token is essential to run the user store agent. The token can be configured in one of the following ways. 1. Configure the token in the configuration file @@ -324,7 +324,7 @@ After registering the user store, you'll be redirected to the **Setup Guide** of Refer [remote agent properties]({{base_path}}/references/remote-user-store/remote-user-store-properties/) for the complete list of agent configurations. - 3. Return to the Asgardeo Console and, click **Generate Token** to create an installation token. The installation token is essential to run the user store agent. + 3. Return to the WSO2 Identity Platform Console and, click **Generate Token** to create an installation token. The installation token is essential to run the user store agent. !!! warning - Copy the installation token and save it in a safe location. You won't be able to see it again! @@ -366,6 +366,6 @@ After registering the user store, you'll be redirected to the **Setup Guide** of ## What's Next - [Configure high availability for a remote user store]({{base_path}}/guides/users/user-stores/configure-high-availability/) -- [Manage remote user stores in Asgardeo]({{base_path}}/guides/users/user-stores/update-user-stores/) +- [Manage remote user stores in WSO2 Identity Platform]({{base_path}}/guides/users/user-stores/update-user-stores/) - [Deployment best practices for the remote agent]({{base_path}}/guides/users/user-stores/deployment-best-practices/) - [Advanced configuration for the remote agent]({{base_path}}/guides/users/user-stores/advanced-configurations-for-the-agent/) diff --git a/en/asgardeo/docs/guides/users/user-stores/configure-high-availability.md b/en/asgardeo/docs/guides/users/user-stores/configure-high-availability.md index 52cff350c8..ecfc37e140 100644 --- a/en/asgardeo/docs/guides/users/user-stores/configure-high-availability.md +++ b/en/asgardeo/docs/guides/users/user-stores/configure-high-availability.md @@ -4,13 +4,13 @@ Remote user stores must be highly available to ensure continuous access to criti ## Prerequisites -[Configure and connect a remote user store]({{base_path}}/guides/users/user-stores/configure-a-user-store/) in Asgardeo. +[Configure and connect a remote user store]({{base_path}}/guides/users/user-stores/configure-a-user-store/) in WSO2 Identity Platform. ## Connect a second user store agent To connect a second user store agent: -1. On the Asgardeo Console, go to **User Attributes & Stores** > **User Stores**. +1. On the WSO2 Identity Platform Console, go to **User Attributes & Stores** > **User Stores**. 2. Select your user store from the **User stores** list. 3. In the **General** tab, a second user store agent is listed under **User Store Agent Connection(s)**. 4. Click **Generate token** on the second user store agent. diff --git a/en/asgardeo/docs/guides/users/user-stores/deployment-best-practices.md b/en/asgardeo/docs/guides/users/user-stores/deployment-best-practices.md index fe0ddccd8e..8f3f939000 100644 --- a/en/asgardeo/docs/guides/users/user-stores/deployment-best-practices.md +++ b/en/asgardeo/docs/guides/users/user-stores/deployment-best-practices.md @@ -1,6 +1,6 @@ # Deployment best practices for the remote agent -Deploying the remote agent efficiently is crucial for ensuring a stable and secure connection between Asgardeo and your on-premise user store. Follow these best practices to enhance security and monitoring. +Deploying the remote agent efficiently is crucial for ensuring a stable and secure connection between WSO2 Identity Platform and your on-premise user store. Follow these best practices to enhance security and monitoring. ### Secure the installation token @@ -12,11 +12,11 @@ Encrypt sensitive information such as user store credentials in the agent config ### Deploy in a local network -Deploy the agent in a local network where the actual user store resides and allow only the outbound traffic to the Asgardeo server. If required, you can also configure secure communication between the agent and the user store by configuring ldap over ssl (i.e. ldaps). +Deploy the agent in a local network where the actual user store resides and allow only the outbound traffic to the WSO2 Identity Platform server. If required, you can also configure secure communication between the agent and the user store by configuring ldap over ssl (i.e. ldaps). ### Monitor the agent -Monitor the agent to ensure that it is running without any issues. You can configure a monitoring job by utilizing the Asgardeo remote user store API to check the status of the agent. Following is a sample curl command to check the agent status. +Monitor the agent to ensure that it is running without any issues. You can configure a monitoring job by utilizing the WSO2 Identity Platform remote user store API to check the status of the agent. Following is a sample curl command to check the agent status. === "Optimized Agent" diff --git a/en/asgardeo/docs/guides/users/user-stores/index.md b/en/asgardeo/docs/guides/users/user-stores/index.md index ef2ecfcdce..2e0cd3a92b 100644 --- a/en/asgardeo/docs/guides/users/user-stores/index.md +++ b/en/asgardeo/docs/guides/users/user-stores/index.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../../includes/guides/users/user-stores/index.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/users/user-stores/update-user-stores.md b/en/asgardeo/docs/guides/users/user-stores/update-user-stores.md index 807209d504..bb245179ac 100644 --- a/en/asgardeo/docs/guides/users/user-stores/update-user-stores.md +++ b/en/asgardeo/docs/guides/users/user-stores/update-user-stores.md @@ -1,11 +1,11 @@ -# Manage remote user stores in Asgardeo -This guide walks you through the process of managing your remote user stores via the Asgardeo Console. +# Manage remote user stores in WSO2 Identity Platform +This guide walks you through the process of managing your remote user stores via the WSO2 Identity Platform Console. ## Update attribute mappings -To update attribute mappings via the Asgardeo Console: +To update attribute mappings via the WSO2 Identity Platform Console: -1. On the Asgardeo Console, go to **User Attributes & Stores** > **User Stores**. +1. On the WSO2 Identity Platform Console, go to **User Attributes & Stores** > **User Stores**. 2. Select your user store from the **User stores** list. 3. Go to the **Configurations** tab and update the required information. @@ -13,7 +13,7 @@ To update attribute mappings via the Asgardeo Console: - Update **User Attributes** and **Group Attributes** as per your user store. - Update **Custom Attributes** and **Local Attributes** mapped to your user store. - - Be sure to map Asgardeo attributes with the corresponding on-premise user store attributes. + - Be sure to map WSO2 Identity Platform attributes with the corresponding on-premise user store attributes. 4. Click **Update** to save the configurations. @@ -21,7 +21,7 @@ To update attribute mappings via the Asgardeo Console: To disconnect a user store agent: -1. On the Asgardeo Console, go to **User Attributes & Stores** > **User Stores**. +1. On the WSO2 Identity Platform Console, go to **User Attributes & Stores** > **User Stores**. 2. Select your user store from the **User stores** list. 3. In the **User Store Agent Connection(s)** section, click **Disconnect** on the user store agent that you wish to disconnect. 4. Select the checkbox to confirm your action and click **Confirm**. @@ -39,7 +39,7 @@ In case you forget or lose this installation token, you can regenerate it. To regenerate an installation token: -1. On the Asgardeo Console, go to **User Attributes & Stores** > **User Stores**. +1. On the WSO2 Identity Platform Console, go to **User Attributes & Stores** > **User Stores**. 2. Select your user store from the **User Stores** list and go to the **General** tab. 3. In the **User Store Agent Connection(s)** section, click **Regenerate Token** on the user store agent that you wish to regenerate the token for. @@ -47,11 +47,11 @@ To regenerate an installation token: ## Disable a user store !!! warning - If you disable a user store, its users will lose access to Asgardeo applications and administrators can no longer view users or groups of that user store in the Asgardeo Console. + If you disable a user store, its users will lose access to WSO2 Identity Platform applications and administrators can no longer view users or groups of that user store in the WSO2 Identity Platform Console. To disable a user store: -1. On the Asgardeo Console, go to **User Attributes & Stores** > **User Stores** and select your user store. +1. On the WSO2 Identity Platform Console, go to **User Attributes & Stores** > **User Stores** and select your user store. 2. Turn on the **Disable User Store** toggle at the bottom of the page to disable the user store. {: style="display: block; margin: 0; border: 0.3px solid lightgrey;"} @@ -68,7 +68,7 @@ A user store can be deleted by an administrator. Once a user store is deleted, t To delete a user store: -1. On the Asgardeo Console, go to **User Attributes & Stores** > **User Stores** and select your user store. +1. On the WSO2 Identity Platform Console, go to **User Attributes & Stores** > **User Stores** and select your user store. 2. Click **Delete User Store** at the bottom of the page. {: style="display: block; margin: 0; border: 0.3px solid lightgrey;"} diff --git a/en/asgardeo/docs/guides/your-asgardeo/asgardeo-self-service.md b/en/asgardeo/docs/guides/your-asgardeo/asgardeo-self-service.md index ab6286a93c..7a9597c460 100644 --- a/en/asgardeo/docs/guides/your-asgardeo/asgardeo-self-service.md +++ b/en/asgardeo/docs/guides/your-asgardeo/asgardeo-self-service.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set my_account_url_note = " You can access the My Account portal using the following URL: diff --git a/en/asgardeo/docs/guides/your-asgardeo/delete-your-user-account.md b/en/asgardeo/docs/guides/your-asgardeo/delete-your-user-account.md index 5ef15023f1..8282f157ca 100644 --- a/en/asgardeo/docs/guides/your-asgardeo/delete-your-user-account.md +++ b/en/asgardeo/docs/guides/your-asgardeo/delete-your-user-account.md @@ -1,3 +1,3 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set path = "your-asgardeo/manage-root-organizations" %} {% include "../../../../includes/guides/admin-portal/delete-your-user-account.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/your-asgardeo/index.md b/en/asgardeo/docs/guides/your-asgardeo/index.md index 626ae511ff..f2892e679a 100644 --- a/en/asgardeo/docs/guides/your-asgardeo/index.md +++ b/en/asgardeo/docs/guides/your-asgardeo/index.md @@ -1,7 +1,7 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set path = "your-asgardeo/asgardeo-self-service" %} {% set root_organization_creation_flow = -"When you [create an account](../../get-started/create-asgardeo-account.md) in Asgardeo, you define your first organization (root), which functions as the root organization or tenant in your Asgardeo subscription. From thereon, you (the account owner) or other delegated administrators can create multiple root organizations via the Asgardeo Console and switch between them." +"When you [create an account](../../get-started/create-asgardeo-account.md) in WSO2 Identity Platform, you define your first organization (root), which functions as the root organization or tenant in your WSO2 Identity Platform subscription. From thereon, you (the account owner) or other delegated administrators can create multiple root organizations via the WSO2 Identity Platform Console and switch between them." %} {% set resource_management_in_multiple_root_orgs = diff --git a/en/asgardeo/docs/guides/your-asgardeo/manage-environments/index.md b/en/asgardeo/docs/guides/your-asgardeo/manage-environments/index.md index e8a6be67a9..b4b9f581bd 100644 --- a/en/asgardeo/docs/guides/your-asgardeo/manage-environments/index.md +++ b/en/asgardeo/docs/guides/your-asgardeo/manage-environments/index.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../../includes/guides/admin-portal/manage-environments.md" %} diff --git a/en/asgardeo/docs/guides/your-asgardeo/manage-root-organizations.md b/en/asgardeo/docs/guides/your-asgardeo/manage-root-organizations.md index e3a6898a6a..57554267f4 100644 --- a/en/asgardeo/docs/guides/your-asgardeo/manage-root-organizations.md +++ b/en/asgardeo/docs/guides/your-asgardeo/manage-root-organizations.md @@ -1,3 +1,3 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set path = "your-asgardeo" %} {% include "../../../../includes/guides/admin-portal/manage-root-organizations.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/your-asgardeo/recover-password.md b/en/asgardeo/docs/guides/your-asgardeo/recover-password.md index 130bcfd40f..aa997381c6 100644 --- a/en/asgardeo/docs/guides/your-asgardeo/recover-password.md +++ b/en/asgardeo/docs/guides/your-asgardeo/recover-password.md @@ -1,3 +1,3 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set myacc_doc_url = "your-asgardeo/asgardeo-self-service" %} {% include "../../../../includes/guides/admin-portal/recover-password.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/your-asgardeo/subscribe-to-asgardeo/index.md b/en/asgardeo/docs/guides/your-asgardeo/subscribe-to-asgardeo/index.md index e0e80148ef..54c5f304de 100644 --- a/en/asgardeo/docs/guides/your-asgardeo/subscribe-to-asgardeo/index.md +++ b/en/asgardeo/docs/guides/your-asgardeo/subscribe-to-asgardeo/index.md @@ -1,6 +1,6 @@ -# Subscribe to Asgardeo +# Subscribe to WSO2 Identity Platform -Asgardeo is free to use for anyone who wants to integrate powerful identity and access management capabilities in their applications and continue to use it for free if it fits their requirements. +WSO2 Identity Platform is free to use for anyone who wants to integrate powerful identity and access management capabilities in their applications and continue to use it for free if it fits their requirements. If you wish to subscribe to a higher-tier plan, follow the guides below. diff --git a/en/asgardeo/docs/guides/your-asgardeo/subscribe-to-asgardeo/subscribe-via-azure-marketplace.md b/en/asgardeo/docs/guides/your-asgardeo/subscribe-to-asgardeo/subscribe-via-azure-marketplace.md index 837789d64d..e553478359 100644 --- a/en/asgardeo/docs/guides/your-asgardeo/subscribe-to-asgardeo/subscribe-via-azure-marketplace.md +++ b/en/asgardeo/docs/guides/your-asgardeo/subscribe-to-asgardeo/subscribe-via-azure-marketplace.md @@ -1,28 +1,28 @@ # Subscribe via Azure Marketplace -Asgardeo is available on the Microsoft Azure Marketplace. Development teams that rely on the Azure cloud platform can conveniently subscribe to Asgardeo and get started with implementing identity and access management features in their applications. +WSO2 Identity Platform is available on the Microsoft Azure Marketplace. Development teams that rely on the Azure cloud platform can conveniently subscribe to WSO2 Identity Platform and get started with implementing identity and access management features in their applications. -## Asgardeo offerings +## WSO2 Identity Platform offerings -Listed below are the Asgardeo offerings on the Azure marketplace. +Listed below are the WSO2 Identity Platform offerings on the Azure marketplace. -- [Asgardeo for B2C](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/wso2inc1602241248883.asgardeo_b2c?tab=Overview) - Manage your customers and secure access to customer-facing applications. -- [Asgardeo for B2B](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/wso2inc1602241248883.asgardeo_b2b?tab=Overview) - Manage business customers and partners and secure access to your B2B applications. -- [Asgardeo for B2E](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/wso2inc1602241248883.asgardeo_b2e_enterprise?tab=Overview) - Manage your organization employees and secure access to critical internal applications and services. +- [WSO2 Identity Platform for B2C](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/wso2inc1602241248883.asgardeo_b2c?tab=Overview) - Manage your customers and secure access to customer-facing applications. +- [WSO2 Identity Platform for B2B](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/wso2inc1602241248883.asgardeo_b2b?tab=Overview) - Manage business customers and partners and secure access to your B2B applications. +- [WSO2 Identity Platform for B2E](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/wso2inc1602241248883.asgardeo_b2e_enterprise?tab=Overview) - Manage your organization employees and secure access to critical internal applications and services. -## Purchase an Asgardeo subscription +## Purchase an WSO2 Identity Platform subscription -Follow the steps below to purchase an Asgardeo subscription via the Azure Marketplace. +Follow the steps below to purchase an WSO2 Identity Platform subscription via the Azure Marketplace. -1. Navigate to one of the following Asgardeo offerings on the Azure marketplace. +1. Navigate to one of the following WSO2 Identity Platform offerings on the Azure marketplace. - - [Asgardeo for B2C](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/wso2inc1602241248883.asgardeo_b2c?tab=Overview) - - [Asgardeo for B2B](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/wso2inc1602241248883.asgardeo_b2b?tab=Overview) + - [WSO2 Identity Platform for B2C](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/wso2inc1602241248883.asgardeo_b2c?tab=Overview) + - [WSO2 Identity Platform for B2B](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/wso2inc1602241248883.asgardeo_b2b?tab=Overview) !!! note Learn more about Azure Marketplace SaaS offerings in the [Microsoft documentation](https://learn.microsoft.com/en-us/marketplace/purchase-saas-offer-in-azure-portal). - {: width="700" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} + {: width="700" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} 2. Click **Get it Now**, if prompted, enter your information and click **Continue**. @@ -30,7 +30,7 @@ Follow the steps below to purchase an Asgardeo subscription via the Azure Market 3. You will be redirected to Microsoft Azure. In Azure, select your desired plan and click **Subscribe**. !!! note - Navigate to the **Plans + Pricing** section to view details on all the available Asgardeo subscription plans. + Navigate to the **Plans + Pricing** section to view details on all the available WSO2 Identity Platform subscription plans. 4. Provide a unique name for the subscription and provide a Resource group. @@ -38,24 +38,24 @@ Follow the steps below to purchase an Asgardeo subscription via the Azure Market 6. Review the details of your subscription and click **Subscribe**. -7. Click **Configure account now** and you will be redirected to Asgardeo to [link your subscription](#link-your-subscription) to an organization. +7. Click **Configure account now** and you will be redirected to WSO2 Identity Platform to [link your subscription](#link-your-subscription) to an organization. ## Link your subscription -Once you purchase an Asgardeo subscription via the Azure Marketplace, you will be redirected to Asgardeo to link your subscription to an organization where your applications reside. +Once you purchase an WSO2 Identity Platform subscription via the Azure Marketplace, you will be redirected to WSO2 Identity Platform to link your subscription to an organization where your applications reside. To do so, follow the steps below. -1. Log in to Asgardeo using the same Microsoft account you used to purchase the subscription. +1. Log in to WSO2 Identity Platform using the same Microsoft account you used to purchase the subscription. -2. Enter the name of your existing Asgardeo organization or choose to create a new organization. +2. Enter the name of your existing WSO2 Identity Platform organization or choose to create a new organization. !!! note You can only link an organization that you own. If you wish to upgrade an organization that you do not own, contact the relevant organization owner. - {: width="400" border: 0.3px solid lightgrey;"} + {: width="400" border: 0.3px solid lightgrey;"} 3. Once the linking is successful, the following prompt appears. Click **Sign In** to access your organization and enjoy your subscription! - {: width="700" border: 0.3px solid lightgrey;"} \ No newline at end of file + {: width="700" border: 0.3px solid lightgrey;"} \ No newline at end of file diff --git a/en/asgardeo/docs/guides/your-asgardeo/subscribe-to-asgardeo/subscribe-via-billing-portal.md b/en/asgardeo/docs/guides/your-asgardeo/subscribe-to-asgardeo/subscribe-via-billing-portal.md index 0e32ac954c..2fb86315d8 100644 --- a/en/asgardeo/docs/guides/your-asgardeo/subscribe-to-asgardeo/subscribe-via-billing-portal.md +++ b/en/asgardeo/docs/guides/your-asgardeo/subscribe-to-asgardeo/subscribe-via-billing-portal.md @@ -1,6 +1,6 @@ # Subscribe via Billing Portal -Start your Asgardeo journey with the free plan and use it for as long as you want if it fits your requirements. You can also upgrade to a paid plan, downgrade to a lower plan, or cancel your subscription, as explained below. +Start your WSO2 Identity Platform journey with the free plan and use it for as long as you want if it fits your requirements. You can also upgrade to a paid plan, downgrade to a lower plan, or cancel your subscription, as explained below. See the [pricing details](https://wso2.com/asgardeo/pricing/) and the available resource limits and usage limits for each subscription plan. @@ -8,7 +8,7 @@ See the [pricing details](https://wso2.com/asgardeo/pricing/) and the available To upgrade your subscription: -1. Sign in to the Asgardeo Console. +1. Sign in to the WSO2 Identity Platform Console. 2. Click **Upgrade** on the upper menu or go to the profile menu and select **Billing Portal** to open the portal. {: width="700" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} @@ -31,7 +31,7 @@ To upgrade your subscription: - **Upgrade an existing paid subscription** by selecting a higher tier plan and following the same steps mentioned above. - - **Subscribe to an Enterprise plan** by clicking Contact Us, and submitting your information. The Asgardeo team will get back to you with the next steps. + - **Subscribe to an Enterprise plan** by clicking Contact Us, and submitting your information. The WSO2 Identity Platform team will get back to you with the next steps. ## Plan details @@ -81,22 +81,22 @@ Note that the price for each subscription plan varies depending on the business ### Monthly Active Users (MAUs) -This value indicates the total number of users that can be authenticated into your system using Asgardeo within a month. Use the slider to select the number of monthly active users (MAU) you expect to have. Note that the price for each subscription plan varies depending on the MAU. +This value indicates the total number of users that can be authenticated into your system using WSO2 Identity Platform within a month. Use the slider to select the number of monthly active users (MAU) you expect to have. Note that the price for each subscription plan varies depending on the MAU. -If you are on the free subscription, the MAU count will be throttled when the limit is exceeded. However, for higher subscription plans, additional MAUs will not be throttled but charged as specified in the [Asgardeo pricing](https://wso2.com/asgardeo/pricing/) page. +If you are on the free subscription, the MAU count will be throttled when the limit is exceeded. However, for higher subscription plans, additional MAUs will not be throttled but charged as specified in the [WSO2 Identity Platform pricing](https://wso2.com/asgardeo/pricing/) page. ### Subscription plan Depending on your selected use case, the available subscription plans will change. You can customize the subscription plan by changing your selected options such as MAUs, support plan, etc. !!! note - To compare the different subscription plans, go to [Asgardeo pricing](https://wso2.com/asgardeo/pricing/). + To compare the different subscription plans, go to [WSO2 Identity Platform pricing](https://wso2.com/asgardeo/pricing/). {: width="700" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} ### Support plan -The support plan you select determines the availability of support services from the Asgardeo team. Select the support plan you want using the drop-down list available for the subscription plan, as shown in the following example. +The support plan you select determines the availability of support services from the WSO2 Identity Platform team. Select the support plan you want using the drop-down list available for the subscription plan, as shown in the following example. Available support packages for each plan are as follows: @@ -121,4 +121,4 @@ Once you have upgraded to a paid plan, you can find and download your invoice fr ## Downgrade/Cancel your subscription -Contact the Asgardeo support team at **asgardeo-help@wso2.com** for subscription downgrades and cancellations. \ No newline at end of file +Contact the WSO2 Identity Platform support team at **asgardeo-help@wso2.com** for subscription downgrades and cancellations. \ No newline at end of file diff --git a/en/asgardeo/docs/page-not-found.md b/en/asgardeo/docs/page-not-found.md index 69df046724..64acaca0e7 100644 --- a/en/asgardeo/docs/page-not-found.md +++ b/en/asgardeo/docs/page-not-found.md @@ -11,7 +11,7 @@ template: templates/no-navbars.htmlPage Not Found
Sorry, but the page you are looking for does not exist, has been removed, renamed, or is temporarily unavailable. Please try using one of the navigation links above or the search bar in the top right corner.
For further inquiries, reach us at the `help-asgardeo` channel in the WSO2 Discord server. - Alternatively, you can reach out to the Asgardeo support team.
+ Alternatively, you can reach out to the WSO2 Identity Platform support team.diff --git a/en/asgardeo/docs/quick-starts/branding-ai.md b/en/asgardeo/docs/quick-starts/branding-ai.md index 456ecd6db9..987c16f448 100644 --- a/en/asgardeo/docs/quick-starts/branding-ai.md +++ b/en/asgardeo/docs/quick-starts/branding-ai.md @@ -11,7 +11,7 @@ template: templates/quick-start.html ], prerequisites: [ "About 15 minutes", - "Asgardeo account" + "WSO2 Identity Platform account" ], whats_next: [ "Try out Login Flow AI Quickstart", @@ -28,9 +28,9 @@ Welcome to the Quickstart Guide for Branding AI! In this guide, you’ll ## Create and configure a sample app -You can either use the Asgardeo [Try-It]({{ base_path }}/get-started/try-it-application/){:target="_blank"} hosted app without setting up a local app or create and run a sample app locally using the Asgardeo React template. +You can either use the WSO2 Identity Platform [Try-It]({{ base_path }}/get-started/try-it-application/){:target="_blank"} hosted app without setting up a local app or create and run a sample app locally using the WSO2 Identity Platform React template. -=== "Using Asgardeo Try-It hosted app" +=== "Using WSO2 Identity Platform Try-It hosted app" 1. On the {{product_name}} Console, navigate to **Home** and click **Try login with the Try It app**. 2. A dialog box appears prompting you to create a user account. Create a user account or if you already have one, click Continue to proceed. @@ -38,9 +38,9 @@ You can either use the Asgardeo [Try-It]({{ base_path }}/get-started/try-it-appl !!! note "Note" {{product_name}} provides a hosted sample app called [Try-It]({{ base_path }}/get-started/try-it-application/){:target="_blank"} , which allows you to explore features like passwordless login, Multi-Factor Authentication (MFA), social logins, adaptive authentication, and user provisioning without the need to create or run a local app. Once you enable the {{product_name}} Try-It app, it will automatically register and configure an application in the {{product_name}} console, making it ready for you to use. -=== "Using Asgardeo React template " +=== "Using WSO2 Identity Platform React template " - - Sign into Asgardeo console and navigate to **Applications > New Application**. + - Sign into WSO2 Identity Platform console and navigate to **Applications > New Application**. - Select **Single Page Application** and complete the wizard popup by providing a suitable name and an authorized redirect URL. @@ -49,19 +49,19 @@ You can either use the Asgardeo [Try-It]({{ base_path }}/get-started/try-it-appl **Authorized redirect URL:** http://localhost:5173 - - Note down the following values from the Protocol tab of the registered application. You will need them to configure Asgardeo React SDK. + - Note down the following values from the Protocol tab of the registered application. You will need them to configure WSO2 Identity Platform React SDK. - **`client-id`** from the **Protocol** tab. - - The **name** of your Asgardeo organization + - The **name** of your WSO2 Identity Platform organization - - Use the Asgardeo React template to bootstrap your application by running the following command. + - Use the WSO2 Identity Platform React template to bootstrap your application by running the following command. ```bash npx tmplr --dir my-vite-react-app asgardeo/asgardeo-vite-react-template ``` - The Asgardeo React template generates a ready-made React sample app with pre-configured login and logout capabilities, helping you kick-start your project in just 2 minutes. + The WSO2 Identity Platform React template generates a ready-made React sample app with pre-configured login and logout capabilities, helping you kick-start your project in just 2 minutes. ## **Try out Branding AI** diff --git a/en/asgardeo/docs/quick-starts/javascript.md b/en/asgardeo/docs/quick-starts/javascript.md index 5861290235..15e9e27a01 100644 --- a/en/asgardeo/docs/quick-starts/javascript.md +++ b/en/asgardeo/docs/quick-starts/javascript.md @@ -6,13 +6,13 @@ template: templates/quick-start.html const meta = { what_you_will_learn: [ "Create new single-page JavaScript app", - "Install Asgardeo JavaScript SDK", + "Install WSO2 Identity Platform JavaScript SDK", "Add user login and logout", "Display user profile information" ], prerequisites: [ "About 15 minutes", - "Asgardeo account", + "WSO2 Identity Platform account", "Install Node.js on your system.", "Make sure you have a JavaScript package manager like
npm,yarn, orpnpm.", "A favorite text editor or IDE" diff --git a/en/asgardeo/docs/quick-starts/loginflow-ai.md b/en/asgardeo/docs/quick-starts/loginflow-ai.md index 91a4573704..0a5990027d 100644 --- a/en/asgardeo/docs/quick-starts/loginflow-ai.md +++ b/en/asgardeo/docs/quick-starts/loginflow-ai.md @@ -39,18 +39,18 @@ MFA, passwordless and social providers are configured in {{product_name}} as **c - {{product_name}} pre-configured with **Magic Link** and **Email OTP** as connections, so you can follow this guide without needing to modify the default settings. - Configure **GitHub** as a **social login provider** by creating a connection in {{product_name}} console. - 1. Register a GitHub OAuth App or a GitHub App by following the [***Register Asgardeo on GitHub*** step in this guide]({{ base_path }}/guides/authentication/social-login/add-github-login/#register-asgardeo-on-github){:target="_blank"}. Once the GitHub app is registered you need to copy **`Client ID`** and **`Client secret`** for the next step. + 1. Register a GitHub OAuth App or a GitHub App by following the [***Register WSO2 Identity Platform on GitHub*** step in this guide]({{ base_path }}/guides/authentication/social-login/add-github-login/#register-wso2-identity-platform-on-github){:target="_blank"}. Once the GitHub app is registered you need to copy **`Client ID`** and **`Client secret`** for the next step. 2. Register GitHub connection in {{product_name}} console by following the [***Register the GitHub IdP*** step in this guide]({{ base_path }}/guides/authentication/social-login/add-github-login/#register-the-github-idp){:target="_blank"}. ## Create and configure a sample app -You can either use the Asgardeo [Try-It]({{ base_path }}/get-started/try-it-application/){:target="_blank"} hosted app without setting up a local app or create & run a sample app locally using the Asgardeo React template. +You can either use the WSO2 Identity Platform [Try-It]({{ base_path }}/get-started/try-it-application/){:target="_blank"} hosted app without setting up a local app or create & run a sample app locally using the WSO2 Identity Platform React template. -=== "Using Asgardeo Try-It hosted app" +=== "Using WSO2 Identity Platform Try-It hosted app" 1. On the {{product_name}} Console, go to **Home** and click **Try login with the Try It app**. 2. A dialog box appears prompting you to create a user account. Create a user account or if you already have one, click Continue to proceed. @@ -60,9 +60,9 @@ You can either use the Asgardeo [Try-It]({{ base_path }}/get-started/try-it-appl -=== "Using Asgardeo React template " +=== "Using WSO2 Identity Platform React template " - - Sign into Asgardeo console and navigate to **Applications > New Application**. + - Sign into WSO2 Identity Platform console and navigate to **Applications > New Application**. - Select **Single Page Application** and complete the wizard popup by providing a suitable name and an authorized redirect URL. @@ -71,23 +71,23 @@ You can either use the Asgardeo [Try-It]({{ base_path }}/get-started/try-it-appl **Authorized redirect URL:** http://localhost:5173 - - Note down the following values from the Protocol tab of the registered application. You will need them to configure Asgardeo React SDK. + - Note down the following values from the Protocol tab of the registered application. You will need them to configure WSO2 Identity Platform React SDK. - **`client-id`** from the **Protocol** tab. - - The **name** of your Asgardeo organization + - The **name** of your WSO2 Identity Platform organization - - Use the Asgardeo React template to bootstrap your application by running the following command. + - Use the WSO2 Identity Platform React template to bootstrap your application by running the following command. ```bash npx tmplr --dir my-vite-react-app asgardeo/asgardeo-vite-react-template ``` - The Asgardeo React template generates a ready-made React sample app with pre-configured login and logout capabilities, helping you kick-start your project in just 2 minutes. + The WSO2 Identity Platform React template generates a ready-made React sample app with pre-configured login and logout capabilities, helping you kick-start your project in just 2 minutes. ## Open the **Login Flow AI** prompt -1. On the {{product_name}} Console, go to **Applications**, and select the **Try It** application *(or select Asgardeo-react app in case if you have created and running an app locally in the previous step)*. +1. On the {{product_name}} Console, go to **Applications**, and select the **Try It** application *(or select WSO2 Identity Platform-react app in case if you have created and running an app locally in the previous step)*. 2. Go to the **Login Flow** tab of the application and click the **Try Login Flow AI** button to open the Login Flow AI prompt. @@ -223,7 +223,7 @@ If successful, the application won’t prompt you for the Email OTP. Instead, yo Next, Let's add our test user to the **manager role**. -1. On the Asgardeo Console, go to **User Management > Roles**. +1. On the WSO2 Identity Platform Console, go to **User Management > Roles**. 2. Click **New Role** > button. 3. In the New Role creation wizard, enter *manager* as the **Role Name** and select **Organization** as the role **audience**, then click next. 4. Skip the Permission Selection screen by clicking next. diff --git a/en/asgardeo/docs/quick-starts/mcp-auth-server.md b/en/asgardeo/docs/quick-starts/mcp-auth-server.md index 35130f340d..95fb702320 100644 --- a/en/asgardeo/docs/quick-starts/mcp-auth-server.md +++ b/en/asgardeo/docs/quick-starts/mcp-auth-server.md @@ -7,7 +7,7 @@ template: templates/quick-start.html what_you_will_learn: [ "Create a new MCP server in TypeScript", "Defines an MCP tool that adds two numbers", - "Install Asgardeo MCP SDK", + "Install WSO2 Identity Platform MCP SDK", "Set up MCP authorization with {{ product_name }}" ], prerequisites: [ diff --git a/en/asgardeo/docs/quick-starts/nodejs.md b/en/asgardeo/docs/quick-starts/nodejs.md index e4277106a4..11b506b8a6 100644 --- a/en/asgardeo/docs/quick-starts/nodejs.md +++ b/en/asgardeo/docs/quick-starts/nodejs.md @@ -6,18 +6,18 @@ template: templates/quick-start.html const meta = { what_you_will_learn: [ "Create a new Express.js app", - "Install Passport Asgardeo strategy @asgardeo/passport-asgardeo", + "Install Passport WSO2 Identity Platform strategy @asgardeo/passport-asgardeo", "Add user login and logout", "Display user profile information" ], prerequisites: [ "About 15 minutes", - "Asgardeo account", + "WSO2 Identity Platform account", "Install Node.js on your system.", "Make sure you have a JavaScript package manager likenpm,yarn, orpnpm.", "A favorite text editor or IDE" ], - source_code: "Asgardeo Node.js Sample" + source_code: "WSO2 Identity Platform Node.js Sample" }; diff --git a/en/asgardeo/docs/quick-starts/react.md b/en/asgardeo/docs/quick-starts/react.md index 7bf1e82415..9d833426d3 100644 --- a/en/asgardeo/docs/quick-starts/react.md +++ b/en/asgardeo/docs/quick-starts/react.md @@ -12,7 +12,7 @@ template: templates/quick-start.html ], prerequisites: [ "About 15 minutes", - "Asgardeo account", + "WSO2 Identity Platform account", "Install Node.js on your system.", "Make sure you have a JavaScript package manager likenpm,yarn, orpnpm.", "A favorite text editor or IDE" diff --git a/en/asgardeo/docs/quick-starts/vue.md b/en/asgardeo/docs/quick-starts/vue.md index f628164759..9aa19c0085 100644 --- a/en/asgardeo/docs/quick-starts/vue.md +++ b/en/asgardeo/docs/quick-starts/vue.md @@ -12,7 +12,7 @@ template: templates/quick-start.html ], prerequisites: [ "About 15 minutes", - "Asgardeo account", + "WSO2 Identity Platform account", "Install Node.js on your system.", "Make sure you have a JavaScript package manager likenpm,yarn, orpnpm.", "A favorite text editor or IDE" diff --git a/en/asgardeo/docs/references/accessibility.md b/en/asgardeo/docs/references/accessibility.md index 8be468a596..e6062b4b6f 100644 --- a/en/asgardeo/docs/references/accessibility.md +++ b/en/asgardeo/docs/references/accessibility.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../includes/references/accessibility.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/references/app-settings/index.md b/en/asgardeo/docs/references/app-settings/index.md index 0fe8048f58..35aac996db 100644 --- a/en/asgardeo/docs/references/app-settings/index.md +++ b/en/asgardeo/docs/references/app-settings/index.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/references/app-settings/index.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/references/app-settings/oidc-settings-for-app.md b/en/asgardeo/docs/references/app-settings/oidc-settings-for-app.md index e1eacf0f78..4c96af6296 100644 --- a/en/asgardeo/docs/references/app-settings/oidc-settings-for-app.md +++ b/en/asgardeo/docs/references/app-settings/oidc-settings-for-app.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% set token_endpoint = "https://api.asgardeo.io/t/<organization_name>/oauth2/token" %} diff --git a/en/asgardeo/docs/references/app-settings/saml-settings-for-app.md b/en/asgardeo/docs/references/app-settings/saml-settings-for-app.md index 7cc34e5eb2..d1873ce1f5 100644 --- a/en/asgardeo/docs/references/app-settings/saml-settings-for-app.md +++ b/en/asgardeo/docs/references/app-settings/saml-settings-for-app.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% set entityID = "accounts.asgardeo.io/t/{organization_name}" %} diff --git a/en/asgardeo/docs/references/app-settings/ws-federation-settings-for-app.md b/en/asgardeo/docs/references/app-settings/ws-federation-settings-for-app.md index 580e7685bd..d6e23822d4 100644 --- a/en/asgardeo/docs/references/app-settings/ws-federation-settings-for-app.md +++ b/en/asgardeo/docs/references/app-settings/ws-federation-settings-for-app.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% set entityID = "accounts.asgardeo.io/t/{organization_name}" %} diff --git a/en/asgardeo/docs/references/asgardeo-outbound-ip-addresses.md b/en/asgardeo/docs/references/asgardeo-outbound-ip-addresses.md index f52d4f4e6a..408af5c0c4 100644 --- a/en/asgardeo/docs/references/asgardeo-outbound-ip-addresses.md +++ b/en/asgardeo/docs/references/asgardeo-outbound-ip-addresses.md @@ -1,6 +1,6 @@ -# Asgardeo outbound IP addresses +# WSO2 Identity Platform outbound IP addresses -Asgardeo uses the following outbound IP addresses for its production environments. If your network security settings require allowlisting specific IPs, refer to the corresponding IPs for your region. +WSO2 Identity Platform uses the following outbound IP addresses for its production environments. If your network security settings require allowlisting specific IPs, refer to the corresponding IPs for your region. !!! warning "Note" @@ -46,7 +46,7 @@ Asgardeo uses the following outbound IP addresses for its production environment-You can onboard to Asgardeo in your preferred region by using the relevant URL (listed below). Your data will be stored in the corresponding regional data center. +You can onboard to WSO2 Identity Platform in your preferred region by using the relevant URL (listed below). Your data will be stored in the corresponding regional data center. -- **Asgardeo Console - US region**: https://console.asgardeo.io/ -- **Asgardeo Console - EU region**: https://console.eu.asgardeo.io/ +- **WSO2 Identity Platform Console - US region**: https://console.asgardeo.io/ +- **WSO2 Identity Platform Console - EU region**: https://console.eu.asgardeo.io/ Effective June 27, 2025, all applicable user and service-related data are stored in the selected regional data center (US or EU), replacing the previous approach of storing some data types only in the US. ### Subscription data -Your subscription account is the user account that's created when you are onboarded to Asgardeo. Billing details are linked to this account. Listed below are some of the subscription data: +Your subscription account is the user account that's created when you are onboarded to WSO2 Identity Platform. Billing details are linked to this account. Listed below are some of the subscription data: - Billing email - Subscription ID @@ -65,7 +65,7 @@ Your subscription account is the user account that's created when you are onboar ### Administrator data -Users onboarded to Asgardeo as [organization administrators]({{base_path}}/guides/users/manage-administrators/) are granted access to the global WSO2 services such as billing and support. Therefore, the administrator data (including profile information and login information from the billing/support portals) was previously stored exclusively in the US datacenter. +Users onboarded to WSO2 Identity Platform as [organization administrators]({{base_path}}/guides/users/manage-administrators/) are granted access to the global WSO2 services such as billing and support. Therefore, the administrator data (including profile information and login information from the billing/support portals) was previously stored exclusively in the US datacenter. The profile information of organization administrators includes all the data that organization administrators enter in their user profiles. @@ -75,7 +75,7 @@ The profile information of organization administrators includes all the data tha ### End-user data -Data of your end users are only stored in the regional datacenter you selected when onboarding to Asgardeo. +Data of your end users are only stored in the regional datacenter you selected when onboarding to WSO2 Identity Platform. ## Data sharing @@ -86,8 +86,8 @@ Therefore, note that your organization–level logs may include personal informa ## Data privacy -Learn about Asgardeo's [privacy policy](https://wso2.com/asgardeo/privacy-policy/#:~:text=Asgardeo%20doesn%27t%20store%20any,API%20Services%20User%20Data%20Policy.) to understand how your data privacy is protected. +Learn about WSO2 Identity Platform's [privacy policy](https://wso2.com/asgardeo/privacy-policy/#:~:text=WSO2 Identity Platform%20doesn%27t%20store%20any,API%20Services%20User%20Data%20Policy.) to understand how your data privacy is protected. ## Get support -If you require more details or have other data residency requirements for your organizations and businesses, contact the Asgardeo support team. +If you require more details or have other data residency requirements for your organizations and businesses, contact the WSO2 Identity Platform support team. diff --git a/en/asgardeo/docs/references/email-templates.md b/en/asgardeo/docs/references/email-templates.md index da7dd877b0..639e5eb9c4 100644 --- a/en/asgardeo/docs/references/email-templates.md +++ b/en/asgardeo/docs/references/email-templates.md @@ -1,3 +1,3 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set api_path = "email-template" %} {% include "../../../includes/references/email-templates.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/references/idp-settings/index.md b/en/asgardeo/docs/references/idp-settings/index.md index 8d7d49d28d..99b25d43a0 100644 --- a/en/asgardeo/docs/references/idp-settings/index.md +++ b/en/asgardeo/docs/references/idp-settings/index.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../../includes/references/idp-settings/index.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/references/idp-settings/oidc-settings-for-idp.md b/en/asgardeo/docs/references/idp-settings/oidc-settings-for-idp.md index 82a4b7e89f..d75b6068cf 100644 --- a/en/asgardeo/docs/references/idp-settings/oidc-settings-for-idp.md +++ b/en/asgardeo/docs/references/idp-settings/oidc-settings-for-idp.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% include "../../../../includes/references/idp-settings/oidc-settings-for-idp.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/references/idp-settings/saml-settings-for-idp.md b/en/asgardeo/docs/references/idp-settings/saml-settings-for-idp.md index c3c267ba60..c49db93938 100644 --- a/en/asgardeo/docs/references/idp-settings/saml-settings-for-idp.md +++ b/en/asgardeo/docs/references/idp-settings/saml-settings-for-idp.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set product_url_format = "https://api.asgardeo.io/t/{organization_name}" %} {% set product_url_sample = "https://api.asgardeo.io/t/bifrost" %} {% include "../../../../includes/references/idp-settings/saml-settings-for-idp.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/references/index.md b/en/asgardeo/docs/references/index.md index d72ff8b91a..2fd53b4b86 100644 --- a/en/asgardeo/docs/references/index.md +++ b/en/asgardeo/docs/references/index.md @@ -1,25 +1,25 @@ # References - Overview -See the topics in this section for references that will help you while working with Asgardeo. This includes concepts related to Asgardeo features, configuration details, and other resources. +See the topics in this section for references that will help you while working with WSO2 Identity Platform. This includes concepts related to WSO2 Identity Platform features, configuration details, and other resources. -- [User roles in Asgardeo]({{base_path}}/references/user-management/user-roles/) and their associated permissions. +- [User roles in WSO2 Identity Platform]({{base_path}}/references/user-management/user-roles/) and their associated permissions. - [OpenID Connect and SAML settings]({{base_path}}/references/app-settings/) for applications. -- [OpenID Connect and SAML settings]({{base_path}}/references/idp-settings/) for enterprise identity providers in Asgardeo. +- [OpenID Connect and SAML settings]({{base_path}}/references/idp-settings/) for enterprise identity providers in WSO2 Identity Platform. -- [Grant types]({{base_path}}/references/grant-types/) used in Asgardeo. +- [Grant types]({{base_path}}/references/grant-types/) used in WSO2 Identity Platform. -- [Pushed Authorization Requests]({{base_path}}/references/pushed-authorization-requests/) in Asgardeo. +- [Pushed Authorization Requests]({{base_path}}/references/pushed-authorization-requests/) in WSO2 Identity Platform. - The [API references]({{base_path}}/references/conditional-auth/api-reference/) you need for writing conditional authentication scripts. -- [Remote agent properties]({{base_path}}/references/remote-user-store/remote-user-store-properties/) you need for configuring Asgardeo user store agent. +- [Remote agent properties]({{base_path}}/references/remote-user-store/remote-user-store-properties/) you need for configuring WSO2 Identity Platform user store agent. -- [Email templates]({{base_path}}/references/email-templates/) in Asgardeo. +- [Email templates]({{base_path}}/references/email-templates/) in WSO2 Identity Platform. -- [Accessibility compliance]({{base_path}}/references/accessibility/) in Asgardeo. +- [Accessibility compliance]({{base_path}}/references/accessibility/) in WSO2 Identity Platform. -- [Data residency]({{base_path}}/references/data-residency-in-asgardeo/) in Asgardeo. +- [Data residency]({{base_path}}/references/data-residency-in-asgardeo/) in WSO2 Identity Platform. -- [API resources and scopes required for MCP tools]({{base_path}}/references/mcp-tool-api-resource-access/) in Asgardeo. +- [API resources and scopes required for MCP tools]({{base_path}}/references/mcp-tool-api-resource-access/) in WSO2 Identity Platform. diff --git a/en/asgardeo/docs/references/operational-policies.md b/en/asgardeo/docs/references/operational-policies.md index b7ad3a95e4..757497ed61 100644 --- a/en/asgardeo/docs/references/operational-policies.md +++ b/en/asgardeo/docs/references/operational-policies.md @@ -4,17 +4,17 @@ We at WSO2, are dedicated to delivering reliable, secure, and efficient services to our customers. To achieve this, we have established a comprehensive set of operational policies that define our procedures and standards across various service aspects. These policies ensure transparency, regulatory compliance, and the highest levels of customer satisfaction. They encompass everything from billing and data protection to load and penetration testing, providing clear guidelines and processes for our customers and internal teams. -### 1.1 Asgardeo +### 1.1 WSO2 Identity Platform -Asgardeo is a cloud-native, developer-centric identity-as-a-service (IDaaS) solution managed by WSO2. It is designed to simplify and enhance identity and access management for applications. This solution is hosted on cloud infrastructure operated by WSO2. +WSO2 Identity Platform is a cloud-native, developer-centric identity-as-a-service (IDaaS) solution managed by WSO2. It is designed to simplify and enhance identity and access management for applications. This solution is hosted on cloud infrastructure operated by WSO2. -Asgardeo’s operational policies provide a robust framework to ensure the efficient, secure, and consistent management of its cloud-native identity and access management platform. These policies are designed based on the following governing areas to align with Asgardeo's core principles of delivering developer-friendly, enterprise-grade identity solutions, while upholding the highest standards of security, scalability, and compliance. +WSO2 Identity Platform’s operational policies provide a robust framework to ensure the efficient, secure, and consistent management of its cloud-native identity and access management platform. These policies are designed based on the following governing areas to align with WSO2 Identity Platform's core principles of delivering developer-friendly, enterprise-grade identity solutions, while upholding the highest standards of security, scalability, and compliance. ### 1.2 Governing areas The operational policies are structured around the following areas: -- Asgardeo Endpoints +- WSO2 Identity Platform Endpoints - Data Residency - Load Testing - Penetration Testing @@ -23,66 +23,66 @@ The operational policies are structured around the following areas: - Support -## 2. Asgardeo endpoints +## 2. WSO2 Identity Platform endpoints -### 2.1 Asgardeo URLs +### 2.1 WSO2 Identity Platform URLs -Asgardeo currently operates in two regions, the US and EU, providing a localized and seamless experience for customers. You can access Asgardeo services through the following region-specific URLs: +WSO2 Identity Platform currently operates in two regions, the US and EU, providing a localized and seamless experience for customers. You can access WSO2 Identity Platform services through the following region-specific URLs: #### US Region -- Asgardeo Console - [https://console.asgardeo.io](https://console.asgardeo.io){target="_blank"} +- WSO2 Identity Platform Console - [https://console.asgardeo.io](https://console.asgardeo.io){target="_blank"} - My Account Portal - [https://myaccount.asgardeo.io](https://myaccount.asgardeo.io){target="_blank"} - API - [https://api.asgardeo.io](https://api.asgardeo.io){target="_blank"} #### EU Region -- Asgardeo Console - [https://console.eu.asgardeo.io](https://console.eu.asgardeo.io){target="_blank"} +- WSO2 Identity Platform Console - [https://console.eu.asgardeo.io](https://console.eu.asgardeo.io){target="_blank"} - My Account Portal - [https://myaccount.eu.asgardeo.io](https://myaccount.eu.asgardeo.io){target="_blank"} - API - [https://api.eu.asgardeo.io](https://api.eu.asgardeo.io){target="_blank"} -### 2.2 Asgardeo endpoints +### 2.2 WSO2 Identity Platform endpoints -Asgardeo provides a comprehensive set of REST APIs, organized into the following categories to streamline usage while ensuring security and efficiency. +WSO2 Identity Platform provides a comprehensive set of REST APIs, organized into the following categories to streamline usage while ensuring security and efficiency. -- **Management APIs** allow applications that use Asgardeo as their Identity Provider to perform operations such as user, group, role, application management and authentication. +- **Management APIs** allow applications that use WSO2 Identity Platform as their Identity Provider to perform operations such as user, group, role, application management and authentication. - **Organization APIs** enable the management of organizational hierarchies and resources associated with organizations. - **End User APIs** allow authenticated users to manage their profiles, preferences, and sessions. -Customers can refer to the [Asgardeo documentation](https://wso2.com/asgardeo/docs/apis/){target="_blank"} for detailed instructions on accessing these APIs. By following these guidelines, customers can seamlessly integrate Asgardeo’s capabilities into their systems. +Customers can refer to the [WSO2 Identity Platform documentation](https://wso2.com/asgardeo/docs/apis/){target="_blank"} for detailed instructions on accessing these APIs. By following these guidelines, customers can seamlessly integrate WSO2 Identity Platform’s capabilities into their systems. ## 3. Data residency Data residency refers to the geographical or regulatory boundaries where data is stored and processed. -### 3.1 Data residency in Asgardeo +### 3.1 Data residency in WSO2 Identity Platform -The following diagram shows how data is stored in Asgardeo and how different entities interact with it. +The following diagram shows how data is stored in WSO2 Identity Platform and how different entities interact with it. -{: width="600px"} +{: width="600px"} ### 3.2 Data centers -Asgardeo uses two regional data centers to store data: +WSO2 Identity Platform uses two regional data centers to store data: - United States (US) - Europe (EU) -You can onboard to Asgardeo in your preferred region by using the relevant URL below. Your data will be stored in the corresponding regional data center. +You can onboard to WSO2 Identity Platform in your preferred region by using the relevant URL below. Your data will be stored in the corresponding regional data center. -- Asgardeo Console - US region: [https://console.asgardeo.io/](https://console.asgardeo.io/){target="_blank"} -- Asgardeo Console - EU region: [https://console.eu.asgardeo.io/](https://console.eu.asgardeo.io/){target="_blank"} +- WSO2 Identity Platform Console - US region: [https://console.asgardeo.io/](https://console.asgardeo.io/){target="_blank"} +- WSO2 Identity Platform Console - EU region: [https://console.eu.asgardeo.io/](https://console.eu.asgardeo.io/){target="_blank"} Effective June 27, 2025, all types of are stored in the selected regional data center (US or EU), replacing the previous approach of storing some data types only in the US. See section 3.3 for more details. ### 3.3 Data types -This section outlines the different types of data stored in Asgardeo and their respective storage locations. +This section outlines the different types of data stored in WSO2 Identity Platform and their respective storage locations. #### 3.3.1 Subscription data -When you onboard to Asgardeo, the user account created will automatically function as your subscription account. Billing details are linked to this account and will contain subscription data such as: +When you onboard to WSO2 Identity Platform, the user account created will automatically function as your subscription account. Billing details are linked to this account and will contain subscription data such as: - Billing email - Subscription ID - Tier details @@ -93,7 +93,7 @@ When you onboard to Asgardeo, the user account created will automatically functi #### 3.3.2 Administrator data -Administrator data includes any information that organization administrators enter in their user profiles, and also the login information used to access global WSO2 services such as billing and support. Users who onboard to Asgardeo as organization administrators are automatically granted access to these services. +Administrator data includes any information that organization administrators enter in their user profiles, and also the login information used to access global WSO2 services such as billing and support. Users who onboard to WSO2 Identity Platform as organization administrators are automatically granted access to these services. !!! note "Update" @@ -101,7 +101,7 @@ Administrator data includes any information that organization administrators ent #### 3.3.3 End-user data -Data of your end users are only stored in the regional data center you selected when onboarding to Asgardeo. +Data of your end users are only stored in the regional data center you selected when onboarding to WSO2 Identity Platform. ### 3.4 Data sharing @@ -110,32 +110,32 @@ Some of your data, such as logs, will be accessible outside your selected region Therefore, note that your organization–level logs may include personal information (such as the IP addresses and email addresses) of your end users. ### 3.5 Data privacy -Learn about [Asgardeo's privacy policy](https://wso2.com/asgardeo/privacy-policy/){target="_blank"} to understand how your data privacy is protected. +Learn about [WSO2 Identity Platform's privacy policy](https://wso2.com/asgardeo/privacy-policy/){target="_blank"} to understand how your data privacy is protected. ### 3.6 Get support -If you require more details or have other data residency requirements for your organizations and businesses, contact the Asgardeo support team. +If you require more details or have other data residency requirements for your organizations and businesses, contact the WSO2 Identity Platform support team. ## 4. Load testing -### 4.1 Load Testing in Asgardeo +### 4.1 Load Testing in WSO2 Identity Platform -WSO2 recognizes that customers may occasionally need to perform load tests against its production cloud service. To ensure a successful test and maintain a high quality of service for all customers, WSO2 has established the following guidelines. Any load testing in Asgardeo must be conducted in accordance with this policy. +WSO2 recognizes that customers may occasionally need to perform load tests against its production cloud service. To ensure a successful test and maintain a high quality of service for all customers, WSO2 has established the following guidelines. Any load testing in WSO2 Identity Platform must be conducted in accordance with this policy. ### 4.2 Eligibility -Only customers with an **Enterprise subscription are permitted to conduct load testing**. Customers with this subscription may request one load test (with up to two repeats) per year against one of their Asgardeo production tenants. +Only customers with an **Enterprise subscription are permitted to conduct load testing**. Customers with this subscription may request one load test (with up to two repeats) per year against one of their WSO2 Identity Platform production tenants. ### 4.3 Approval Process -All performance and load testing require Asgardeo's prior written approval. Once approved, testing can only target tenants that Asgardeo has approved. The approval process includes the following steps: +All performance and load testing require WSO2 Identity Platform's prior written approval. Once approved, testing can only target tenants that WSO2 Identity Platform has approved. The approval process includes the following steps: -- **Submission**: Customers must submit a load testing request through the Asgardeo support portal at least **14 days** prior to the desired test date. +- **Submission**: Customers must submit a load testing request through the WSO2 Identity Platform support portal at least **14 days** prior to the desired test date. - **Information Required**: The request must include detailed information about the test, including the specific dates and times, scope, purpose, IP addresses, tools to be used, and expected request rates. -- **Review**: Asgardeo will review the request to ensure it aligns with service capacity and does not disrupt other customers. +- **Review**: WSO2 Identity Platform will review the request to ensure it aligns with service capacity and does not disrupt other customers. ### 4.4 Testing Guidelines @@ -143,13 +143,13 @@ To maintain service integrity and performance, the following guidelines must be - **Timing**: Load tests should be scheduled during **off-peak hours** to minimize impact on other customers. -- **Rate Limits**: Testing must comply with Asgardeo's published rate limits and any specific limits set during the approval process. +- **Rate Limits**: Testing must comply with WSO2 Identity Platform's published rate limits and any specific limits set during the approval process. -- **Notification**: Customers must notify Asgardeo immediately if any issues arise during the test. +- **Notification**: Customers must notify WSO2 Identity Platform immediately if any issues arise during the test. ### 4.5 Restrictions -Please note that any un-informed load testing on Asgardeo will lead to blocking of the traffic originated. And moreover certain types of testing too are restricted to protect the integrity and performance of Asgardeo’s services: +Please note that any un-informed load testing on WSO2 Identity Platform will lead to blocking of the traffic originated. And moreover certain types of testing too are restricted to protect the integrity and performance of WSO2 Identity Platform’s services: - **Denial of Service (DoS) Testing**: Denial of Service and other disruptive tests are not permitted. @@ -163,13 +163,13 @@ Failure to comply with this policy may result in temporary or permanent restrict ### 4.7 Support and Assistance -For any questions or support related to load testing, customers can contact Asgardeo support through our support portal or designated support channels. Our team is available to assist with planning and executing load tests to ensure compliance and success. +For any questions or support related to load testing, customers can contact WSO2 Identity Platform support through our support portal or designated support channels. Our team is available to assist with planning and executing load tests to ensure compliance and success. ## 5. Penetration Testing -### 5.1 Penetration Testing in Asgardeo +### 5.1 Penetration Testing in WSO2 Identity Platform -WSO2 recognizes that customers may occasionally need to perform penetration tests against Asgardeo, their Identity and access management solution. Asgardeo will not lower any of the existing security measures implemented during the approved pentest engagement period. All security measures will adhere to Asgardeo’s standard incident handling process, regardless of the attack source. Any penetration testing in Asgardeo must be conducted in accordance with this policy. +WSO2 recognizes that customers may occasionally need to perform penetration tests against WSO2 Identity Platform, their Identity and access management solution. WSO2 Identity Platform will not lower any of the existing security measures implemented during the approved pentest engagement period. All security measures will adhere to WSO2 Identity Platform’s standard incident handling process, regardless of the attack source. Any penetration testing in WSO2 Identity Platform must be conducted in accordance with this policy. ### 5.2 Eligibility @@ -177,9 +177,9 @@ Only customers with an **Enterprise subscription** are permitted to conduct pene ### 5.3 Approval Process -All penetration testing requires Asgardeo's prior written approval. Once approved, testing can only target tenants that Asgardeo has approved. The approval process includes the following steps: +All penetration testing requires WSO2 Identity Platform's prior written approval. Once approved, testing can only target tenants that WSO2 Identity Platform has approved. The approval process includes the following steps: -- **Submission** - Customers must submit a penetration testing request through the Asgardeo support portal at least 14 days prior to the desired test date. +- **Submission** - Customers must submit a penetration testing request through the WSO2 Identity Platform support portal at least 14 days prior to the desired test date. - **Information Required** - The request must include detailed information about the Specific dates, times of the test, and timezone. @@ -189,7 +189,7 @@ All penetration testing requires Asgardeo's prior written approval. Once approve - Tools intended to be used during the test. - Contact details of two individuals (including phone numbers and email addresses) available during the testing period for immediate communication. -- **Review** - Asgardeo team will review the request to ensure it aligns with service capacity and does not disrupt other customers. +- **Review** - WSO2 Identity Platform team will review the request to ensure it aligns with service capacity and does not disrupt other customers. ### 5.4 Testing guidelines @@ -197,38 +197,38 @@ To maintain service integrity and performance, the following guidelines must be **Timing** - Penetration tests should be scheduled during off-peak hours to minimize impact on other customers. -**Rate Limits** - Testing must comply with Asgardeo's published rate limits and any specific limits set during the approval process. +**Rate Limits** - Testing must comply with WSO2 Identity Platform's published rate limits and any specific limits set during the approval process. -**Notification** - Customers are required to report all identified vulnerabilities to the Asgardeo support portal immediately. -Disclosed vulnerabilities should remain confidential until further notice from Asgardeo. +**Notification** - Customers are required to report all identified vulnerabilities to the WSO2 Identity Platform support portal immediately. +Disclosed vulnerabilities should remain confidential until further notice from WSO2 Identity Platform. ### 5.5 Restrictions -Please note that any un-informed penetration testing on Asgardeo will lead to blocking of the traffic originated. And moreover certain types of testing too are restricted to protect the integrity and performance of Asgardeo’s services: +Please note that any un-informed penetration testing on WSO2 Identity Platform will lead to blocking of the traffic originated. And moreover certain types of testing too are restricted to protect the integrity and performance of WSO2 Identity Platform’s services: - Customers are strictly prohibited from performing load tests or Denial-of-Service (DoS) attacks. -- Any actions outside the approved scope require prior consent from Asgardeo. +- Any actions outside the approved scope require prior consent from WSO2 Identity Platform. ### 5.6 Non-Compliance -Failure to comply with this policy may result in temporary or permanent restrictions on the customer’s ability to conduct future tests. Any unauthorized actions will prompt Asgardeo to take protective measures, which may include suspending or blocking the offending tenant and/or the source of intrusion traffic. WSO2 reserves the right to take immediate action to protect service availability, including suspending the offending test. +Failure to comply with this policy may result in temporary or permanent restrictions on the customer’s ability to conduct future tests. Any unauthorized actions will prompt WSO2 Identity Platform to take protective measures, which may include suspending or blocking the offending tenant and/or the source of intrusion traffic. WSO2 reserves the right to take immediate action to protect service availability, including suspending the offending test. ### 5.7 Support and Assistance -For any questions or support related to load testing, customers can contact Asgardeo support through our support portal or designated support channels. Our team is available to assist with planning and executing penetration tests to ensure compliance and success. +For any questions or support related to load testing, customers can contact WSO2 Identity Platform support through our support portal or designated support channels. Our team is available to assist with planning and executing penetration tests to ensure compliance and success. ## 6. Limits and Constraints ### 6.1 Rate limits -Asgardeo endpoints are subjected to rate limits to maintain smooth and reliable processing of requests, preventing system failures and slowdowns. These rate limits are applied globally across all tiers of Asgardeo subscriptions. Rate limits are calculated on a per IP address basis. Exceeding the rate limit results in a 429 `Too Many Requests` error code. +WSO2 Identity Platform endpoints are subjected to rate limits to maintain smooth and reliable processing of requests, preventing system failures and slowdowns. These rate limits are applied globally across all tiers of WSO2 Identity Platform subscriptions. Rate limits are calculated on a per IP address basis. Exceeding the rate limit results in a 429 `Too Many Requests` error code. -Refer [Asgardeo rate limits](https://wso2.com/asgardeo/docs/references/rate-limits/) for more information regarding the rate limits. +Refer [WSO2 Identity Platform rate limits](https://wso2.com/asgardeo/docs/references/rate-limits/) for more information regarding the rate limits. ### 6.2 Entity limit -This discusses the entity limits that constraints the usage of Asgardeo free of charge. -Asgardeo is free of charge but it constrains certain entities with limiting the usage. And any asgardeo user might encounter such warnings while they try to create entities (can be applications, connections) more than the allowed amount. +This discusses the entity limits that constraints the usage of WSO2 Identity Platform free of charge. +WSO2 Identity Platform is free of charge but it constrains certain entities with limiting the usage. And any asgardeo user might encounter such warnings while they try to create entities (can be applications, connections) more than the allowed amount.  @@ -236,41 +236,41 @@ Asgardeo is free of charge but it constrains certain entities with limiting the ## 7. Billing -Organization owners can access the billing portal from the **Asgardeo Console** by clicking the profile picture in the top right corner and selecting **Billing Portal**. +Organization owners can access the billing portal from the **WSO2 Identity Platform Console** by clicking the profile picture in the top right corner and selecting **Billing Portal**. ### 7.1 Billing cycle -Asgardeo organization owners can choose to be billed monthly or annually for your subscription. However, note that the monthly active users (MAUs) count that exceeds the allowed limit is always charged monthly. Billing cycles start on the 1st day of every month. Depending on the day of the month in which you subscribe, you will be charged a prorated fee for the first month. +WSO2 Identity Platform organization owners can choose to be billed monthly or annually for your subscription. However, note that the monthly active users (MAUs) count that exceeds the allowed limit is always charged monthly. Billing cycles start on the 1st day of every month. Depending on the day of the month in which you subscribe, you will be charged a prorated fee for the first month. ### 7.2 Subscription -Asgardeo is available to use for free, however, it comes with certain limitations like the number of applications, the MAU count, and the connections that can be created. For higher limits on resources, it is necessary to subscribe to a higher-tier plan. Subscribing to a higher-tier plan can be done either through the Asgardeo billing portal or through Azure marketplace. +WSO2 Identity Platform is available to use for free, however, it comes with certain limitations like the number of applications, the MAU count, and the connections that can be created. For higher limits on resources, it is necessary to subscribe to a higher-tier plan. Subscribing to a higher-tier plan can be done either through the WSO2 Identity Platform billing portal or through Azure marketplace. Refer this guideline below for more on [subscription](https://wso2.com/asgardeo/docs/guides/your-asgardeo/subscribe-to-asgardeo/){target="_blank"}. ### 7.3 Subscription Upgrade -Asgardeo organization owners can upgrade the curent tier of their organizations using the billing portal accessible from the **Asgardeo Console**. This [document](https://wso2.com/asgardeo/docs/guides/your-asgardeo/subscribe-to-asgardeo/subscribe-via-billing-portal/){target="_blank"} provides more insight on how to upgrade tiers. +WSO2 Identity Platform organization owners can upgrade the curent tier of their organizations using the billing portal accessible from the **WSO2 Identity Platform Console**. This [document](https://wso2.com/asgardeo/docs/guides/your-asgardeo/subscribe-to-asgardeo/subscribe-via-billing-portal/){target="_blank"} provides more insight on how to upgrade tiers. ### 7.4 Subscription Downgrade -Contact the Asgardeo support team at asgardeo-help@wso2.com for subscription downgrades and cancellations. +Contact the WSO2 Identity Platform support team at asgardeo-help@wso2.com for subscription downgrades and cancellations. ### 7.5 Invoices -Asgardeo organization owners have the capability to view the invoices for the payments made for the subscriptions in the billing portal. +WSO2 Identity Platform organization owners have the capability to view the invoices for the payments made for the subscriptions in the billing portal. ## 8. Support -Asgardeo provides support services to ensure the smooth operation of your organization's identity and access management needs. The level of support varies based on the subscription tier. The support portal is accessible from the [https://cloud-support.wso2.com/](https://cloud-support.wso2.com/) URL. +WSO2 Identity Platform provides support services to ensure the smooth operation of your organization's identity and access management needs. The level of support varies based on the subscription tier. The support portal is accessible from the [https://cloud-support.wso2.com/](https://cloud-support.wso2.com/) URL. ### 8.1 Support tiers -Asgardeo offers multiple support tiers, including community support for free-tier users and Commercial support for paid subscribers. Commercial support provides faster response times, prioritized issue resolution, and access to dedicated support engineers. +WSO2 Identity Platform offers multiple support tiers, including community support for free-tier users and Commercial support for paid subscribers. Commercial support provides faster response times, prioritized issue resolution, and access to dedicated support engineers. ### 8.2 Support channels - Free-tier users can seek assistance via community forums and public documentation. -- Paid subscribers can reach out to WSO2’s support team through the Asgardeo Support Portal, ensuring a structured approach to issue resolution. +- Paid subscribers can reach out to WSO2’s support team through the WSO2 Identity Platform Support Portal, ensuring a structured approach to issue resolution. - Critical production issues can be escalated for faster resolution based on the support plan. ### 8.3 Support availability @@ -282,37 +282,37 @@ Asgardeo offers multiple support tiers, including community support for free-tie To report an issue, follow these steps: -- Navigate to the Asgardeo Support Portal and submit a support ticket. +- Navigate to the WSO2 Identity Platform Support Portal and submit a support ticket. - Provide detailed information, including error logs, reproduction steps, and impact assessment. - For urgent matters, use priority escalation as per the SLA in your plan. -Refer to the [Asgardeo Support Policy](https://wso2.com/asgardeo-support-policy/){target="_blank"} for more details on available support plans, SLAs, and escalation procedures. +Refer to the [WSO2 Identity Platform Support Policy](https://wso2.com/asgardeo-support-policy/){target="_blank"} for more details on available support plans, SLAs, and escalation procedures. ## 9. Monitoring -Monitoring is a critical aspect of maintaining a business-critical application like Asgardeo. It ensures the application performs as expected without outages, identifies trends for operational insights, and supports capacity planning through system metrics. Monitoring also plays a key role in promptly notifying relevant parties if the application fails to meet expected performance levels. +Monitoring is a critical aspect of maintaining a business-critical application like WSO2 Identity Platform. It ensures the application performs as expected without outages, identifies trends for operational insights, and supports capacity planning through system metrics. Monitoring also plays a key role in promptly notifying relevant parties if the application fails to meet expected performance levels. -### 9.1 Asgardeo Monitoring +### 9.1 WSO2 Identity Platform Monitoring -Asgardeo ensures high availability, security, and performance through continuous system monitoring and automated alerting. We maintain a 99.99% SLA, with real-time service status and uptime metrics available at Asgardeo Status Page. Refer to [https://status.asgardeo.io/](https://status.asgardeo.io/){target="_blank"}. +WSO2 Identity Platform ensures high availability, security, and performance through continuous system monitoring and automated alerting. We maintain a 99.99% SLA, with real-time service status and uptime metrics available at WSO2 Identity Platform Status Page. Refer to [https://status.asgardeo.io/](https://status.asgardeo.io/){target="_blank"}. Our infrastructure, application, and security monitoring ensure early detection of potential issues, enabling rapid incident response to minimize disruptions. For details on our incident management and support process, refer to our Support Policy. Refer to [https://wso2.com/asgardeo-support-policy/](https://wso2.com/asgardeo-support-policy/){target="_blank"}. ### 9.2 Organization Monitoring -Asgardeo provides support to monitor organization for any of the changes done in their organization through audit logs. Refer to the [documentation](https://wso2.com/asgardeo/docs/guides/asgardeo-logs/audit-logs/) for more information. +WSO2 Identity Platform provides support to monitor organization for any of the changes done in their organization through audit logs. Refer to the [documentation](https://wso2.com/asgardeo/docs/guides/asgardeo-logs/audit-logs/) for more information. And diagnostic logs will help admins to monitor what has happened during authentication flows [https://wso2.com/asgardeo/docs/guides/asgardeo-logs/diagnostic-logs/](https://wso2.com/asgardeo/docs/guides/asgardeo-logs/diagnostic-logs/){target="_blank"}. -Similarly Asgardeo provides capability to check on organization insights on the user registration and logins. Refer to [https://wso2.com/asgardeo/docs/guides/organization-insights/](https://wso2.com/asgardeo/docs/guides/organization-insights/){target="_blank"}. +Similarly WSO2 Identity Platform provides capability to check on organization insights on the user registration and logins. Refer to [https://wso2.com/asgardeo/docs/guides/organization-insights/](https://wso2.com/asgardeo/docs/guides/organization-insights/){target="_blank"}. -Asgardeo generates events for various user activities. You can publish these events to WSO2's Choreo platform and trigger custom use cases. Learn more in the [Asgardeo events documentation](https://wso2.com/asgardeo/docs/guides/monitoring/asgardeo-events/){target="_blank"}. +WSO2 Identity Platform generates events for various user activities. You can publish these events to WSO2's Choreo platform and trigger custom use cases. Learn more in the [WSO2 Identity Platform events documentation](https://wso2.com/asgardeo/docs/guides/monitoring/asgardeo-events/){target="_blank"}. ## 10. Product life cycle & Migrations ### 10.1 Product Delivery -Asgardeo, as a cloud offering, adheres to agile principles and emphasizes delivering features and fixes iteratively. We strive to deploy updates to production on a daily basis, ensuring faster delivery of new features, enhancements, and critical improvements. Our primary focus is addressing customer concerns, resolving pain points, and introducing enhancements that improve developer-friendliness while also delivering exciting new features. The changelog provides a comprehensive list of updates, innovations, and improvements introduced to the product. Explore the latest changes here: [https://wso2.com/asgardeo/changelog/](https://wso2.com/asgardeo/changelog/){target="_blank"}. +WSO2 Identity Platform, as a cloud offering, adheres to agile principles and emphasizes delivering features and fixes iteratively. We strive to deploy updates to production on a daily basis, ensuring faster delivery of new features, enhancements, and critical improvements. Our primary focus is addressing customer concerns, resolving pain points, and introducing enhancements that improve developer-friendliness while also delivering exciting new features. The changelog provides a comprehensive list of updates, innovations, and improvements introduced to the product. Explore the latest changes here: [https://wso2.com/asgardeo/changelog/](https://wso2.com/asgardeo/changelog/){target="_blank"}. ### 10.2 New Features @@ -324,12 +324,12 @@ To continuously refine the product and gather valuable customer feedback, we oft ### 10.4 Migration -Asgardeo’s cloud architecture enables us to onboard new features, changes, and improvements efficiently. While implementing these updates, we run silent migrations to ensure a seamless experience for customers. These migrations are designed to be non-intrusive, causing no disruptions to customer engagement with the product or their end users' behavior. +WSO2 Identity Platform’s cloud architecture enables us to onboard new features, changes, and improvements efficiently. While implementing these updates, we run silent migrations to ensure a seamless experience for customers. These migrations are designed to be non-intrusive, causing no disruptions to customer engagement with the product or their end users' behavior. In most cases, migrations do not require downtime, as we carefully plan and execute them in a way that maintains the platform's continuous availability. However, in rare scenarios where downtime is necessary, the following steps are taken: - Customers are informed in advance, with clear communication about the timing and duration. -- Downtime is scheduled during off-peak hours to minimize the impact on customers who rely on Asgardeo. +- Downtime is scheduled during off-peak hours to minimize the impact on customers who rely on WSO2 Identity Platform. - The team ensures the process is completed as quickly and efficiently as possible to restore full service promptly. Transparency is a key part of our migration process. Customers are kept informed of planned updates and any potential impact through multiple communication channels, including Emails and notifications. @@ -338,7 +338,7 @@ By prioritizing communication and careful planning, we ensure that migrations en ## 11. Unsupported requests -The Asgardeo Team is committed to providing the best possible assistance. However, we regret to inform you that we are currently unable to accommodate the following requests: +The WSO2 Identity Platform Team is committed to providing the best possible assistance. However, we regret to inform you that we are currently unable to accommodate the following requests: - Restore any deleted information in an organization, including - Database connections and their users and passwords @@ -350,7 +350,7 @@ The Asgardeo Team is committed to providing the best possible assistance. Howeve - Organization logs once the standard retention time has passed - Providing PII information of other customers and consumer details of the given customer. -- Asgardeo infrastructure architecture diagrams and component details. +- WSO2 Identity Platform infrastructure architecture diagrams and component details. diff --git a/en/asgardeo/docs/references/production-checklist/best-practices.md b/en/asgardeo/docs/references/production-checklist/best-practices.md index e5c290c858..b0e71f4a37 100644 --- a/en/asgardeo/docs/references/production-checklist/best-practices.md +++ b/en/asgardeo/docs/references/production-checklist/best-practices.md @@ -2,7 +2,7 @@ We recommend the following best practices to protect your organization in the production environment: -- **Strong authentication for Asgardeo administrators** +- **Strong authentication for WSO2 Identity Platform administrators** It is recommended to enable strong authentication for administrators with access to your admin console. This can be done by users' preference only. Administrators can enable multi-factor authentication for their asgardeo account. [Learn more]({{base_path}}/guides/your-asgardeo/asgardeo-self-service/#enroll-totp-for-asgardeo-users) diff --git a/en/asgardeo/docs/references/production-checklist/index.md b/en/asgardeo/docs/references/production-checklist/index.md index b4e446086f..7c55cfe16c 100644 --- a/en/asgardeo/docs/references/production-checklist/index.md +++ b/en/asgardeo/docs/references/production-checklist/index.md @@ -1,4 +1,4 @@ -# Asgardeo Production Checklist +# WSO2 Identity Platform Production Checklist Before you go live, use the following list to ensure that your organizations are ready for use in a production environment. diff --git a/en/asgardeo/docs/references/production-checklist/readiness-check.md b/en/asgardeo/docs/references/production-checklist/readiness-check.md index 4df6098ba0..475f14ebdb 100644 --- a/en/asgardeo/docs/references/production-checklist/readiness-check.md +++ b/en/asgardeo/docs/references/production-checklist/readiness-check.md @@ -58,7 +58,7 @@ Use the following sections to verify if your applications are ready for producti Verify authorized redirect URL and home page URL of social connections are updated with the production environment's values. ## Branding -By default, Asgardeo interfaces presented to users are themed according to Asgardeo's default branding. Make sure to customize the UIs according to your organization's branding styles. The following is the list of branding changes required. [Learn more]({{base_path}}/guides/branding/configure-ui-branding/) +By default, WSO2 Identity Platform interfaces presented to users are themed according to WSO2 Identity Platform's default branding. Make sure to customize the UIs according to your organization's branding styles. The following is the list of branding changes required. [Learn more]({{base_path}}/guides/branding/configure-ui-branding/) **General** To ensure the readiness of the general branding of your organizations: @@ -72,7 +72,7 @@ To ensure the readiness of the design branding of your organizations: - Configure logo, favicon, and side images. - Configure the heading text. -- Customize branding styles to UIs provided by Asgardeo provided according to your organization's branding guidelines. +- Customize branding styles to UIs provided by WSO2 Identity Platform provided according to your organization's branding guidelines. **Advanced** To ensure the readiness of the advanced branding of your organizations: @@ -83,17 +83,17 @@ To ensure the readiness of the advanced branding of your organizations: - Configure the Self Signup page. ### Using a custom domain -By default, the interfaces provided by Asgardeo (such as the login page) are presented to your end users over Asgardeo domains. You can customize the URL domain to your organization-preferred host. [Learn more]({{base_path}}/guides/branding/configure-custom-domains/) +By default, the interfaces provided by WSO2 Identity Platform (such as the login page) are presented to your end users over WSO2 Identity Platform domains. You can customize the URL domain to your organization-preferred host. [Learn more]({{base_path}}/guides/branding/configure-custom-domains/) !!! note The free-tier users do not have the capability to configure domain branding. ### Customize email template -By default, all the emails triggered by Asgardeo for your end users have Asgardeo's default branding. If you wish to change the branding and content of the emails, you can customize them via the APIs. [Learn more]({{base_path}}/apis/email-template/#/operations/updateEmailTemplate) +By default, all the emails triggered by WSO2 Identity Platform for your end users have WSO2 Identity Platform's default branding. If you wish to change the branding and content of the emails, you can customize them via the APIs. [Learn more]({{base_path}}/apis/email-template/#/operations/updateEmailTemplate) !!! note - Asgardeo rolled out this feature on Sep 20, 2022. Therefore this new feature is only applied to the Asgardeo organizations created after Sep 20, 2022. - If you wish to use that capability for older organizations, you can send a request to the Asgardeo team at `asgardeo-support@wso2.com`. + WSO2 Identity Platform rolled out this feature on Sep 20, 2022. Therefore this new feature is only applied to the WSO2 Identity Platform organizations created after Sep 20, 2022. + If you wish to use that capability for older organizations, you can send a request to the WSO2 Identity Platform team at `asgardeo-support@wso2.com`. ## Manage subscriptions Make sure to check the resource limits to verify the allowed Monthly Active User (MAU) limits, groups, etc., to ensure your scaling requirements are within the range of your subscription. [Learn more]({{base_path}}/guides/your-asgardeo/subscribe-to-asgardeo/) \ No newline at end of file diff --git a/en/asgardeo/docs/references/production-checklist/security-check.md b/en/asgardeo/docs/references/production-checklist/security-check.md index 9b008cb0ee..6707ade872 100644 --- a/en/asgardeo/docs/references/production-checklist/security-check.md +++ b/en/asgardeo/docs/references/production-checklist/security-check.md @@ -4,7 +4,7 @@ Use the following list to ensure your organizations are secure in a production e ## Authentication To ensure the authentication is properly configured in your organizations: -- (Recommended) Configure strong authentication for Asgardeo administrator users. [Learn more]({{base_path}}/guides/your-asgardeo/asgardeo-self-service/#enroll-totp-for-asgardeo-users) +- (Recommended) Configure strong authentication for WSO2 Identity Platform administrator users. [Learn more]({{base_path}}/guides/your-asgardeo/asgardeo-self-service/#enroll-totp-for-asgardeo-users) - Configure strong authentication for your business applications based on the application's sensitivity. [Learn more]({{base_path}}/guides/authentication/mfa/) ## Account Security diff --git a/en/asgardeo/docs/references/push-notification-based-authentication.md b/en/asgardeo/docs/references/push-notification-based-authentication.md index 6de4506966..f06be0bcb7 100644 --- a/en/asgardeo/docs/references/push-notification-based-authentication.md +++ b/en/asgardeo/docs/references/push-notification-based-authentication.md @@ -1,4 +1,4 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% set push_mfa_doc_path = "../guides/authentication/mfa/add-push-auth-login.md" %} {% include "../../../includes/references/concepts/push-notification-based-authentication.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/references/pushed-authorization-requests.md b/en/asgardeo/docs/references/pushed-authorization-requests.md index 52005851d4..048da97cc7 100644 --- a/en/asgardeo/docs/references/pushed-authorization-requests.md +++ b/en/asgardeo/docs/references/pushed-authorization-requests.md @@ -1,2 +1,2 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../includes/references/pushed-authorization-requests.md" %} \ No newline at end of file diff --git a/en/asgardeo/docs/references/rate-limits.md b/en/asgardeo/docs/references/rate-limits.md index f662d01b1c..c588b3e808 100644 --- a/en/asgardeo/docs/references/rate-limits.md +++ b/en/asgardeo/docs/references/rate-limits.md @@ -1,6 +1,6 @@ # Rate limits -Asgardeo endpoints are subjected to rate limits to maintain smooth and reliable processing of requests, preventing system failures and slowdowns. These rate limits are applied globally across all tiers of Asgardeo subscriptions. +WSO2 Identity Platform endpoints are subjected to rate limits to maintain smooth and reliable processing of requests, preventing system failures and slowdowns. These rate limits are applied globally across all tiers of WSO2 Identity Platform subscriptions. Rate limits are calculated on a per IP address basis. For example, if the rate limit for an endpoint is 200, it means that the maximum number of requests you can make to this endpoint from a single IP address is 200 per minute. diff --git a/en/asgardeo/docs/references/remote-user-store/remote-user-store-properties.md b/en/asgardeo/docs/references/remote-user-store/remote-user-store-properties.md index a53fdc00ff..3aa6b7cea0 100644 --- a/en/asgardeo/docs/references/remote-user-store/remote-user-store-properties.md +++ b/en/asgardeo/docs/references/remote-user-store/remote-user-store-properties.md @@ -4,7 +4,7 @@ The following table provides descriptions of the key properties to apply in
@@ -44,16 +44,16 @@ Asgardeo uses two regional data centers to store data: const meta = { what_you_will_learn: [ - "Build and install the Asgardeo MCP Server", - "Configure your Asgardeo organization", - "Set up your code editor with the Asgardeo MCP Server" + "Build and install the WSO2 Identity Platform MCP Server", + "Configure your WSO2 Identity Platform organization", + "Set up your code editor with the WSO2 Identity Platform MCP Server" ], prerequisites: [ "About 15 minutes", - "Asgardeo account", + "WSO2 Identity Platform account", "Install Go on your system.", "You need to have one of the following tools installed: VS Code, Claude Desktop, Cursor, Windsurf or any other MCP-compatible client" ], - source_code: "Asgardeo MCP Server", + source_code: "WSO2 Identity Platform MCP Server", }; diff --git a/en/asgardeo/docs/tutorials/auth-users-into-android-apps.md b/en/asgardeo/docs/tutorials/auth-users-into-android-apps.md index 59442f2600..01893f25a6 100644 --- a/en/asgardeo/docs/tutorials/auth-users-into-android-apps.md +++ b/en/asgardeo/docs/tutorials/auth-users-into-android-apps.md @@ -1,4 +1,4 @@ -# Authenticate users into Android applications using Asgardeo +# Authenticate users into Android applications using WSO2 Identity Platform An Android app is a software application that runs on Android devices or emulators. It is distributed in the form of an APK file, which is a ZIP archive that contains the app code, resources, and metadata. Android apps can be written in Kotlin or Java and are executed within a virtual machine. @@ -14,25 +14,25 @@ If you choose the first option of handling user registration and login within th To avoid these challenges, it is recommended to use an identity provider to handle user registration and authentication. This means that all user identities are managed by the identity provider and that the login data is recorded. In cases of harmful activity, it will be easier to identify who was online and what they did, which makes problem-solving and threat elimination easier. -Asgardeo, a SaaS-based customer identity and access management (CIAM) solution, is a suitable identity provider for Android applications. +WSO2 Identity Platform, a SaaS-based customer identity and access management (CIAM) solution, is a suitable identity provider for Android applications. ## Overview -This tutorial guides you through the process of integrating user authentication capabilities into an Android application using Asgardeo as the CIAM provider. +This tutorial guides you through the process of integrating user authentication capabilities into an Android application using WSO2 Identity Platform as the CIAM provider. ### Authentication flow The high-level flow for the integration is as follows: 1. The user clicks the login button of an Android application. -2. The user is directed to the Asgardeo login page. -3. The user enters their Asgardeo account credentials. -4. The user is authenticated via Asgardeo, and upon successful login, they are redirected to the application's home page. -5. If the user clicks the logout button of the application, they are logged out from Asgardeo and redirected to the relevant page. +2. The user is directed to the WSO2 Identity Platform login page. +3. The user enters their WSO2 Identity Platform account credentials. +4. The user is authenticated via WSO2 Identity Platform, and upon successful login, they are redirected to the application's home page. +5. If the user clicks the logout button of the application, they are logged out from WSO2 Identity Platform and redirected to the relevant page. ### OIDC authentication method -Before you dive into integrating Asgardeo with your mobile application, let's take a closer look at the authentication mechanism you will use for login capabilities. Authentication involves various protocols, but for this example, we'll be using the OIDC protocol, which is widely recognized as the industry standard for mobile applications. +Before you dive into integrating WSO2 Identity Platform with your mobile application, let's take a closer look at the authentication mechanism you will use for login capabilities. Authentication involves various protocols, but for this example, we'll be using the OIDC protocol, which is widely recognized as the industry standard for mobile applications. To ensure a secure authentication process for your Android application, let's use the OIDC protocol with PKCE. Learn more about the [authorization code flow with PKCE]({{base_path}}/guides/authentication/oidc/implement-auth-code-with-pkce/). @@ -40,13 +40,13 @@ To ensure a secure authentication process for your Android application, let's us In the world of software development, an SDK (Software Development Kit) is an essential set of software tools and programs that enable developers to create applications for specific platforms, operating systems, computer systems, or devices. It's like a kit of different items that come with the tools and instructions required for assembling them, similar to putting together a standard car model. -When integrating Asgardeo with your mobile application, you can use any third-party OIDC SDK that supports the protocol. For this tutorial, let's use the [app-auth](https://github.com/openid/AppAuth-Android) Android SDK. With the app-auth Android SDK, you can easily add OIDC-based login and logout capabilities to your Android applications. +When integrating WSO2 Identity Platform with your mobile application, you can use any third-party OIDC SDK that supports the protocol. For this tutorial, let's use the [app-auth](https://github.com/openid/AppAuth-Android) Android SDK. With the app-auth Android SDK, you can easily add OIDC-based login and logout capabilities to your Android applications. ## Sample scenario -In this tutorial, we'll use the example of creating Meal Magic, a food delivery app that requires user authentication for ordering food. You'll begin by building a basic application without integrating Asgardeo authentication. +In this tutorial, we'll use the example of creating Meal Magic, a food delivery app that requires user authentication for ordering food. You'll begin by building a basic application without integrating WSO2 Identity Platform authentication. -Then, you'll integrate Asgardeo authentication into the application. After successful authentication, the user will see their username on the next screen and will be able to select a location to find nearby restaurants. The application will also provide a logout option for users to log out. +Then, you'll integrate WSO2 Identity Platform authentication into the application. After successful authentication, the user will see their username on the next screen and will be able to select a location to find nearby restaurants. The application will also provide a logout option for users to log out. ## Prerequisites @@ -62,19 +62,19 @@ First, you need to create the application. After installing Android Studio, create a new project with a basic activity, and design the application login page and the home page. -## Step 2: Register the application in Asgardeo +## Step 2: Register the application in WSO2 Identity Platform -To integrate Asgardeo as your CIAM provider, you need to register your application in Asgardeo. Since you are building an Android application, it should be registered as a mobile application. See the instructions on [registering a mobile application]({{base_path}}/guides/applications/register-mobile-app/). +To integrate WSO2 Identity Platform as your CIAM provider, you need to register your application in WSO2 Identity Platform. Since you are building an Android application, it should be registered as a mobile application. See the instructions on [registering a mobile application]({{base_path}}/guides/applications/register-mobile-app/). !!! note When registering the application, it's important to specify `com.sample.mealmagic://home` as the authorized redirect URI, which must also match the redirect URL specified in the application configuration. -After registering your application with Asgardeo, you can enable [user attributes for the app]({{base_path}}/guides/authentication/user-attributes/enable-attributes-for-oidc-app/). These attributes correspond to the user's profile information that can be retrieved by the application with the user's consent. +After registering your application with WSO2 Identity Platform, you can enable [user attributes for the app]({{base_path}}/guides/authentication/user-attributes/enable-attributes-for-oidc-app/). These attributes correspond to the user's profile information that can be retrieved by the application with the user's consent. !!! note If you need additional attributes that are not listed in the user's profile section by default, you can [configure new attributes]({{base_path}}/guides/users/attributes/manage-attributes/) and retrieve them through the `profile` scope. -Note that admin users are not allowed to log in to the Android application. Therefore, it is necessary to create a business user in Asgardeo. See the instructions on [managing users in Asgardeo]({{base_path}}/guides/users/manage-users/#onboard-a-user). +Note that admin users are not allowed to log in to the Android application. Therefore, it is necessary to create a business user in WSO2 Identity Platform. See the instructions on [managing users in WSO2 Identity Platform]({{base_path}}/guides/users/manage-users/#onboard-a-user). ## Step 3: Install dependencies @@ -92,7 +92,7 @@ Appauth is an SDK for application authentication, while Okio is a library that s ## Step 4: Configure the Callback URL -Once the authorization flow is completed on the browser, Asgardeo will redirect to the callback URL sent in the authorization request. In order for the app to capture this response, it must register with the Android OS as a handler for this redirect URI as below. +Once the authorization flow is completed on the browser, WSO2 Identity Platform will redirect to the callback URL sent in the authorization request. In order for the app to capture this response, it must register with the Android OS as a handler for this redirect URI as below. Add `RedirectSchema` to the `build.gradle` file. @@ -104,14 +104,14 @@ android.defaultConfig.manifestPlaceholders = [ ## Step 5: Implement sign-in -We have two activities - `MainActivity` and `UserInfoActivity`. The main activity has a sign-in button. Once the user clicks the sign-in button, at the code level, we need to send a call to Asgardeo to get the authorization code. +We have two activities - `MainActivity` and `UserInfoActivity`. The main activity has a sign-in button. Once the user clicks the sign-in button, at the code level, we need to send a call to WSO2 Identity Platform to get the authorization code. As mentioned earlier, it's a best practice for mobile applications to use OpenID Connect (OIDC) with the PKCE option. Since PKCE is being used, the authorization request must include a code challenge and code challenge method. When using the app-auth SDK, these parameters are automatically included in the authorization request via the builder method, so there's no need to manually add them. 1. First, fetch the identity provider metadata information using the `fetchFromIssuer` method and add the information to `AuthorizationServiceConfiguration`. !!! note - You can find the issuer details in the **Info** tab of the application you created in Asgardeo. + You can find the issuer details in the **Info** tab of the application you created in WSO2 Identity Platform. 2. After providing the issuer details, call the `builder` method with the required parameters. @@ -123,7 +123,7 @@ As mentioned earlier, it's a best practice for mobile applications to use OpenID Client id - This is the client ID of the application registered in Asgardeo. Note that client secrets are not issued for mobile apps since they are public clients. However, the PKCE extension is enabled by default as a security measure. + This is the client ID of the application registered in WSO2 Identity Platform. Note that client secrets are not issued for mobile apps since they are public clients. However, the PKCE extension is enabled by default as a security measure. @@ -131,7 +131,7 @@ As mentioned earlier, it's a best practice for mobile applications to use OpenID Redirect URI - This is the URI to which the authorization code is sent upon authentication and where the user is redirected upon logout. This is the callback URL configured in Asgardeo for the Android mobile app. + This is the URI to which the authorization code is sent upon authentication and where the user is redirected upon logout. This is the callback URL configured in WSO2 Identity Platform for the Android mobile app. @@ -148,7 +148,7 @@ As mentioned earlier, it's a best practice for mobile applications to use OpenID Use scopes to define the required access. If you include profile, the user's profile details will be sent in the ID token. To obtain the ID token, you must also send theopenidscope. For our use case, to get the user's name and other profile details, we will request theopenidandprofilescopes. - These scopes should be configured in the Asgardeo application as well. + These scopes should be configured in the WSO2 Identity Platform application as well.@@ -240,7 +240,7 @@ class _MyAppState extends State
@@ -170,7 +170,7 @@ Follow the steps given below to integrate your application with Asgardeo: clientId - This is the client ID of the application registered in Asgardeo. + This is the client ID of the application registered in WSO2 Identity Platform. Note: Client secrets are not issued for mobile apps since they are public clients. However, the PKCE (Proof Key for Code Exchange) extension is enabled by default as a security measure. @@ -181,7 +181,7 @@ Follow the steps given below to integrate your application with Asgardeo:(Required) This is the URI to which the authorization code is sent upon authentication and where the user is redirected upon logout. - Note: This is the URI given as the Authorized redirect URIs (e.g.: wso2.asgardeo.sampleflutterapp://login-callback) when the application in Asgardeo is created. This should be constructed by appending://login-callbackto the callback URI we used when configuring the Callback URL. + Note: This is the URI given as the Authorized redirect URIs (e.g.:wso2.asgardeo.sampleflutterapp://login-callback) when the application in WSO2 Identity Platform is created. This should be constructed by appending://login-callbackto the callback URI we used when configuring the Callback URL.@@ -189,7 +189,7 @@ Follow the steps given below to integrate your application with Asgardeo: discoveryUrl - This is the OpenID Connect Discovery endpoint in Asgardeo, which is used to discover Asgardeo's metadata required to interact with it. + This is the OpenID Connect Discovery endpoint in WSO2 Identity Platform, which is used to discover WSO2 Identity Platform's metadata required to interact with it. @@ -197,7 +197,7 @@ Follow the steps given below to integrate your application with Asgardeo: userInfoEndpoint - This is the endpoint in Asgardeo that is used for retrieving user profile information from Asgardeo. + This is the endpoint in WSO2 Identity Platform that is used for retrieving user profile information from WSO2 Identity Platform. { } ``` -You can change the login method to authenticate application users to the system through Asgardeo. The [authorizeAndExchangeCode()](https://pub.dev/documentation/flutter_appauth/latest/flutter_appauth/FlutterAppAuth/authorizeAndExchangeCode.html) method in the `flutter_appauth` library handles the end-to-end authentication flow. +You can change the login method to authenticate application users to the system through WSO2 Identity Platform. The [authorizeAndExchangeCode()](https://pub.dev/documentation/flutter_appauth/latest/flutter_appauth/FlutterAppAuth/authorizeAndExchangeCode.html) method in the `flutter_appauth` library handles the end-to-end authentication flow. You can replace the current implementation of the `loginFunction()` with the following code snippet: @@ -284,14 +284,14 @@ Here's how the flow works in more detail: - The `AuthorizationTokenRequest` object is then passed into [appAuth.authorizeAndExchangeCode()](https://pub.dev/documentation/flutter_appauth/latest/flutter_appauth/FlutterAppAuth/authorizeAndExchangeCode.html) to start the sign-in process. - The user is directed to Asgardeo's sign-in page for authentication. As a result, [AuthorizationTokenResponse](https://pub.dev/documentation/flutter_appauth_platform_interface/latest/flutter_appauth_platform_interface/AuthorizationTokenResponse-class.html) is received. It contains two token types returned by Asgardeo. + The user is directed to WSO2 Identity Platform's sign-in page for authentication. As a result, [AuthorizationTokenResponse](https://pub.dev/documentation/flutter_appauth_platform_interface/latest/flutter_appauth_platform_interface/AuthorizationTokenResponse-class.html) is received. It contains two token types returned by WSO2 Identity Platform. - **Access Token**: A token represents access delegated to the client application by the user to access the user's protected resources. It has a specific scope and duration. - - **ID Token**: A security token represented as a JSON Web Token (JWT) that proves the user's successful authentication with Asgardeo. Furthermore, it contains other requested user profile information. + - **ID Token**: A security token represented as a JSON Web Token (JWT) that proves the user's successful authentication with WSO2 Identity Platform. Furthermore, it contains other requested user profile information. ## Step 7: Retrieve user information -Once the user has logged in to the system, there is a section that shows the user's profile information. To get this information from Asgardeo, we will implement the `retrieveUserDetails()` method. This method uses the access token received in the login flow and includes it in the header section of the request as a bearer token to access the `/userinfo` endpoint. +Once the user has logged in to the system, there is a section that shows the user's profile information. To get this information from WSO2 Identity Platform, we will implement the `retrieveUserDetails()` method. This method uses the access token received in the login flow and includes it in the header section of the request as a bearer token to access the `/userinfo` endpoint. Then, the retrieved profile information response is parsed and set to the corresponding variables. @@ -365,13 +365,13 @@ Let's walk through the end-to-end flow of the application we built in this tutor {: width="300" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} - You will be redirected to Asgardeo's login page, where you will enter valid user credentials. + You will be redirected to WSO2 Identity Platform's login page, where you will enter valid user credentials. -3. Use the credentials of the user created when you registered the application in Asgardeo. +3. Use the credentials of the user created when you registered the application in WSO2 Identity Platform. {: width="300" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} - Upon the first login attempt, Asgardeo prompts for consent to share the configured attributes with the Flutter application. + Upon the first login attempt, WSO2 Identity Platform prompts for consent to share the configured attributes with the Flutter application. 4. Give your consent accordingly, allowing the application to access your profile information. @@ -393,8 +393,8 @@ Let's walk through the end-to-end flow of the application we built in this tutor ## Summary -In this tutorial, we demonstrated how to add authentication to a Flutter application using Asgardeo as the CIAM provider. The integration of authentication and authorization capabilities was made possible with the use of the Flutter AppAuth plugin. +In this tutorial, we demonstrated how to add authentication to a Flutter application using WSO2 Identity Platform as the CIAM provider. The integration of authentication and authorization capabilities was made possible with the use of the Flutter AppAuth plugin. -We also provided a detailed guide on how to configure the application on Asgardeo. Starting with a sample Flutter application without user authentication implemented, we modified the sign-in, sign-out, and user info retrieval methods to successfully integrate authentication and profile info retrieval capabilities using Asgardeo. +We also provided a detailed guide on how to configure the application on WSO2 Identity Platform. Starting with a sample Flutter application without user authentication implemented, we modified the sign-in, sign-out, and user info retrieval methods to successfully integrate authentication and profile info retrieval capabilities using WSO2 Identity Platform. The [completed source code](https://github.com/asgardeo-samples/asgardeo-flutter-samples/tree/main/asgardeo-flutter-integration-demo) of the application. \ No newline at end of file diff --git a/en/asgardeo/docs/tutorials/connect-asgardeo-with-ms-entra.md b/en/asgardeo/docs/tutorials/connect-asgardeo-with-ms-entra.md index 987a022611..34f64e5506 100644 --- a/en/asgardeo/docs/tutorials/connect-asgardeo-with-ms-entra.md +++ b/en/asgardeo/docs/tutorials/connect-asgardeo-with-ms-entra.md @@ -1,13 +1,13 @@ -# Connect Asgardeo as an OIDC attribute provider for verifiable credentials (VC) with Microsoft Entra Verified ID +# Connect WSO2 Identity Platform as an OIDC attribute provider for verifiable credentials (VC) with Microsoft Entra Verified ID [Microsoft Entra Verified ID](https://www.microsoft.com/en-us/security/business/identity-access/microsoft-entra-verified-id) is a verifiable credential issuance and verification service provided by Microsoft Azure. It allows users to generate, present, and verify their digital identities. -Microsoft allows configuring an IDP (such as Asgardeo) as an OpenID Connect (OIDC) attribute provider for verifiable credentials using their `idTokens` attestation in which the claims provided through the OIDC id token is used to generate the verifiable credential. +Microsoft allows configuring an IDP (such as WSO2 Identity Platform) as an OpenID Connect (OIDC) attribute provider for verifiable credentials using their `idTokens` attestation in which the claims provided through the OIDC id token is used to generate the verifiable credential. -This tutorial explains how this is done using Asgardeo and Microsoft Entra. Given below are the high-level steps you will follow: +This tutorial explains how this is done using WSO2 Identity Platform and Microsoft Entra. Given below are the high-level steps you will follow: 1. Configure Microsoft Entra Verified ID to issue verifiable credentials. -2. Configure Asgardeo as an OIDC attribute provider. +2. Configure WSO2 Identity Platform as an OIDC attribute provider. 3. Try out the Microsoft Verified ID Node JS sample. ## Sample scenario @@ -16,7 +16,7 @@ Consider the sample use case given below. Krusty Krab is a fast-food restaurant owned and operated by Mr. Krabs. Krusty Krab has an employee management system where employees can log in and perform their employee-related operations, such as payroll handling, expense reimbursement, etc. -Krusty Krab utilizes Asgardeo as their identity provider and has created an organization named **krustykrab**. Every Krusty Krab employee has an account in the Asgardeo organization. +Krusty Krab utilizes WSO2 Identity Platform as their identity provider and has created an organization named **krustykrab**. Every Krusty Krab employee has an account in the WSO2 Identity Platform organization. Recently Mr. Krabs decided to issue employee credentials to their employees using Verifiable Credentials, which the employees can then use to prove their employment at Krusty Krab. @@ -207,15 +207,15 @@ With that, you have completed setting up the Entra Verified ID instance. Now you {: style="display: block; margin: 0; border: 0.3px solid lightgrey;"} -## Step 2: Configure Asgardeo as the OIDC attribute provider +## Step 2: Configure WSO2 Identity Platform as the OIDC attribute provider -In this step, you will configure the connection between Asgardeo and the Microsoft Verified ID service. Here, we need to create an application in Asgardeo with the Mobile template. +In this step, you will configure the connection between WSO2 Identity Platform and the Microsoft Verified ID service. Here, we need to create an application in WSO2 Identity Platform with the Mobile template. -1. On the [Asgardeo Console](https://console.asgardeo.io/), go to **Applications**. +1. On the [WSO2 Identity Platform Console](https://console.asgardeo.io/), go to **Applications**. 2. Click **New Application** and select **Mobile Application**: - {: style="display: block; margin: 0; border: 0.3px solid lightgrey;"} + {: style="display: block; margin: 0; border: 0.3px solid lightgrey;"} 3. Enter the following details: @@ -251,10 +251,10 @@ In this step, you will configure the connection between Asgardeo and the Microso - PKCE is disabled as it is not required for the tutorial. - The listed configurations in the **Guide** tab are needed for the next step of the tutorial. -7. Go to **User Management** > **Users** on the Asgardeo Console and add a new user from there. +7. Go to **User Management** > **Users** on the WSO2 Identity Platform Console and add a new user from there. !!! note - This step is required to ensure you can log in to the application. You need a business user registered in the Asgardeo organization to be able to perform user login. + This step is required to ensure you can log in to the application. You need a business user registered in the WSO2 Identity Platform organization to be able to perform user login. {: style="display: block; margin: 0; border: 0.3px solid lightgrey;"} @@ -286,7 +286,7 @@ Now, let's create a credential for the Verified ID service with the id token att } }, "consent": { - "instructions": "Sign in with your Asgardeo account to get your card.", + "instructions": "Sign in with your WSO2 Identity Platform account to get your card.", "title": "Do you want to get your Krusty Krab Verified Credential?" }, "claims": [ @@ -317,9 +317,9 @@ Now, let's create a credential for the Verified ID service with the id token att 5. Configure the **Rules definition**. !!! note - This is the most important part, where we add configurations for the connection with Asgardeo. The rules definition determines what the user should do to get the credential. + This is the most important part, where we add configurations for the connection with WSO2 Identity Platform. The rules definition determines what the user should do to get the credential. - Here, the attestation should be an `idTokens` attestation, and the rules definition should contain the Asgardeo application's client ID, openid configuration url, scopes, and claim mappings. See the below table to learn how to retrieve these values on Asgardeo. + Here, the attestation should be an `idTokens` attestation, and the rules definition should contain the WSO2 Identity Platform application's client ID, openid configuration url, scopes, and claim mappings. See the below table to learn how to retrieve these values on WSO2 Identity Platform. @@ -560,9 +560,9 @@ To get the KrustyKrab verifiable credential: {: width="500" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} -3. Scan the QR and you'll see an option to sign in with Asgardeo. +3. Scan the QR and you'll see an option to sign in with WSO2 Identity Platform. -4. Click **Sign In with Asgardeo**, and you are redirected to the login page provided by Asgardeo. +4. Click **Sign In with WSO2 Identity Platform**, and you are redirected to the login page provided by WSO2 Identity Platform. 5. Sign in with the user account you added previously. @@ -574,7 +574,7 @@ To get the KrustyKrab verifiable credential: {: width="500" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} -You can view the user details you received from Asgardeo by clicking the verifiable credential card inside the wallet. +You can view the user details you received from WSO2 Identity Platform by clicking the verifiable credential card inside the wallet. ### Step 5.3: Verify the credential @@ -596,4 +596,4 @@ The sample website now receives the user details from the KrustyKrab credential. {: width="500" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} -Now that you have successfully configured Asgardeo as an OIDC attribute provider for Microsoft Entra verifiable credentials, you can continue to harness the full capabilities that Asgardeo provides by customizing the sign-in flow, enhancing application security, etc. \ No newline at end of file +Now that you have successfully configured WSO2 Identity Platform as an OIDC attribute provider for Microsoft Entra verifiable credentials, you can continue to harness the full capabilities that WSO2 Identity Platform provides by customizing the sign-in flow, enhancing application security, etc. \ No newline at end of file diff --git a/en/asgardeo/docs/tutorials/end-to-end-mcp-authorization-with-asgardeo.md b/en/asgardeo/docs/tutorials/end-to-end-mcp-authorization-with-asgardeo.md index 707490a348..108b30cb44 100644 --- a/en/asgardeo/docs/tutorials/end-to-end-mcp-authorization-with-asgardeo.md +++ b/en/asgardeo/docs/tutorials/end-to-end-mcp-authorization-with-asgardeo.md @@ -108,7 +108,7 @@ To configure the MCP client, you need to register a new MCP client application i ##### Register a new MCP client application -We need to have the Vet Assist AI application registered in Asgardeo, so that the registered MCP server can be authorized to the AI application and the application can securely access the MCP server on behalf of the authenticated user. +We need to have the Vet Assist AI application registered in WSO2 Identity Platform, so that the registered MCP server can be authorized to the AI application and the application can securely access the MCP server on behalf of the authenticated user. To register the MCP client, diff --git a/en/asgardeo/docs/tutorials/index.md b/en/asgardeo/docs/tutorials/index.md index 9b5926af76..266fc386e4 100644 --- a/en/asgardeo/docs/tutorials/index.md +++ b/en/asgardeo/docs/tutorials/index.md @@ -4,14 +4,14 @@ pageClass: intro-page # Tutorials - Overview -See the topics listed below for end-to-end tutorials on how to use Asgardeo with different technologies and different use cases. +See the topics listed below for end-to-end tutorials on how to use WSO2 Identity Platform with different technologies and different use cases. -- [Authenticate users into Android applications using Asgardeo]({{base_path}}/tutorials/auth-users-into-android-apps/) -- [Authenticate users into Flutter applications using Asgardeo]({{base_path}}/tutorials/auth-users-into-flutter-apps/) -- [Connect Asgardeo as an OIDC attribute provider for verifiable credentials (VC) with Microsoft Entra Verified ID]({{base_path}}/tutorials/connect-asgardeo-with-ms-entra/) -- [Connect Asgardeo as an OIDC attribute provider for verifiable credentials (VC) with MATTR]({{base_path}}/tutorials/connect-asgardeo-with-mattr/) -- [Secure Spring Boot API with Asgardeo]({{base_path}}/tutorials/secure-spring-boot-api/) -- [Integrate Asgardeo with SMART on FHIR healthcare apps]({{base_path}}/tutorials/smart-on-fhir/) -- [Secure Agentic AI Systems with Asgardeo]({{base_path}}/tutorials/secure-agentic-ai-systems/) -- [Integrating Asgardeo With WSO2 AI Gateway for Agent Identity-Aware Access Control]({{base_path}}/tutorials/wso2-ai-gateway-with-agent-identity-aware-access-control/) -- [Integrating Asgardeo With Kong AI Gateway for Agent Identity-Aware Access Control]({{base_path}}/tutorials/kong-ai-gateway-with-agent-identity-aware-access-control/) +- [Authenticate users into Android applications using WSO2 Identity Platform]({{base_path}}/tutorials/auth-users-into-android-apps/) +- [Authenticate users into Flutter applications using WSO2 Identity Platform]({{base_path}}/tutorials/auth-users-into-flutter-apps/) +- [Connect WSO2 Identity Platform as an OIDC attribute provider for verifiable credentials (VC) with Microsoft Entra Verified ID]({{base_path}}/tutorials/connect-asgardeo-with-ms-entra/) +- [Connect WSO2 Identity Platform as an OIDC attribute provider for verifiable credentials (VC) with MATTR]({{base_path}}/tutorials/connect-asgardeo-with-mattr/) +- [Secure Spring Boot API with WSO2 Identity Platform]({{base_path}}/tutorials/secure-spring-boot-api/) +- [Integrate WSO2 Identity Platform with SMART on FHIR healthcare apps]({{base_path}}/tutorials/smart-on-fhir/) +- [Secure Agentic AI Systems with WSO2 Identity Platform]({{base_path}}/tutorials/secure-agentic-ai-systems/) +- [Integrating WSO2 Identity Platform With WSO2 AI Gateway for Agent Identity-Aware Access Control]({{base_path}}/tutorials/wso2-ai-gateway-with-agent-identity-aware-access-control/) +- [Integrating WSO2 Identity Platform With Kong AI Gateway for Agent Identity-Aware Access Control]({{base_path}}/tutorials/kong-ai-gateway-with-agent-identity-aware-access-control/) diff --git a/en/asgardeo/docs/tutorials/kong-ai-gateway-with-agent-identity-aware-access-control.md b/en/asgardeo/docs/tutorials/kong-ai-gateway-with-agent-identity-aware-access-control.md index 0706c3d087..a04c4b4d05 100644 --- a/en/asgardeo/docs/tutorials/kong-ai-gateway-with-agent-identity-aware-access-control.md +++ b/en/asgardeo/docs/tutorials/kong-ai-gateway-with-agent-identity-aware-access-control.md @@ -1,3 +1,3 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../includes/tutorials/kong-ai-gateway-with-agent-identity-aware-access-control.md" %} diff --git a/en/asgardeo/docs/tutorials/react-authentication-tutorial.md b/en/asgardeo/docs/tutorials/react-authentication-tutorial.md index 2e8c39c9a7..7db39331a7 100644 --- a/en/asgardeo/docs/tutorials/react-authentication-tutorial.md +++ b/en/asgardeo/docs/tutorials/react-authentication-tutorial.md @@ -9,7 +9,7 @@ date: "March 2026" reading_time: "12 min read" seo: - description: "Learn how to add secure user authentication to a React app using Asgardeo — login, logout, user profile, protected routes, and API calls." + description: "Learn how to add secure user authentication to a React app using WSO2 Identity Platform — login, logout, user profile, protected routes, and API calls." keywords: "react authentication, oauth 2.0, openid connect, wso2, asgardeo, react sdk, passkeys, mfa, secure routes" author: "Sagara Gunathunga" robots: "index, follow" @@ -99,7 +99,7 @@ If the setup completes successfully, access the application at [http://localhost ## Install the React SDK -The next step is to install the React SDK, which provides the components and hooks required to integrate Asgardeo into your application. Make sure to stop the development server started in the previous step, then run the following command to add the React SDK to your project. +The next step is to install the React SDK, which provides the components and hooks required to integrate WSO2 Identity Platform into your application. Make sure to stop the development server started in the previous step, then run the following command to add the React SDK to your project. === "npm" ```bash @@ -114,13 +114,13 @@ The next step is to install the React SDK, which provides the components and hoo pnpm add @asgardeo/react ``` -## Connect React to Asgardeo +## Connect React to WSO2 Identity Platform -Now that we’ve installed the React SDK in our project, the next step is to connect the React application to Asgardeo. This involves two steps. +Now that we’ve installed the React SDK in our project, the next step is to connect the React application to WSO2 Identity Platform. This involves two steps. -First, create an application in Asgardeo that represents the React application we just built. +First, create an application in WSO2 Identity Platform that represents the React application we just built. -- In the Asgardeo Console, navigate to **Applications > New Application**. +- In the WSO2 Identity Platform Console, navigate to **Applications > New Application**. - Select **React as** the template and complete the wizard by providing: 1. A suitable **name** ( *e.g - asgardeo-react*) @@ -133,14 +133,14 @@ First, create an application in Asgardeo that represents the React application w **The authorized redirect URL determines where {{ product_name }} should send users after they successfully log in. Typically, this will be the web address where your app is hosted**. For this guide, we'll use `http://localhost:5173`, as the sample app will be accessible at this URL. -Once you have created the application in Asgardeo console, copy the following values from the **Guide tab**. You will need them to configure the React SDK. +Once you have created the application in WSO2 Identity Platform console, copy the following values from the **Guide tab**. You will need them to configure the React SDK. -- **Client ID** – A unique ID for your application. Asgardeo uses this to identify login requests coming from your React application. +- **Client ID** – A unique ID for your application. WSO2 Identity Platform uses this to identify login requests coming from your React application. -- **Base URL** – The base URL of your Asgardeo organization. It usually looks like: `https://api.asgardeo.io/t/
@@ -335,7 +335,7 @@ Now, let's create a credential for the Verified ID service with the id token att clientId - The OAuth 2.0 Client ID received from the created Asgardeo application. + The OAuth 2.0 Client ID received from the created WSO2 Identity Platform application. @@ -343,7 +343,7 @@ Now, let's create a credential for the Verified ID service with the id token att configuration - The OpenID Connect identity provider metadata discovery endpoint of the Asgardeo organization. + The OpenID Connect identity provider metadata discovery endpoint of the WSO2 Identity Platform organization. @@ -359,7 +359,7 @@ Now, let's create a credential for the Verified ID service with the id token att scope - The scopes requested from the Asgardeo application. + The scopes requested from the WSO2 Identity Platform application. @@ -367,7 +367,7 @@ Now, let's create a credential for the Verified ID service with the id token att mapping - The output and input claim mappings for VC and Asgardeo. You'll be able to find the identifier for the inputClaimfrom the User Attributes tab of the created Asgardeo application. + The output and input claim mappings for VC and WSO2 Identity Platform. You'll be able to find the identifier for theinputClaimfrom the User Attributes tab of the created WSO2 Identity Platform application.` . The React SDK uses this URL to send login requests to the correct organization. +- **Base URL** – The base URL of your WSO2 Identity Platform organization. It usually looks like: `https://api.asgardeo.io/t/ ` . The React SDK uses this URL to send login requests to the correct organization. Next, configure the ` ` for your application to act as the context provider for the React SDK. To integrate it, wrap your root component in the main.jsx file with ` `. This makes the context created by the provider available throughout your application, so any component can access authentication state and related functions. -You also need to pass the Client ID and Base URL values you copied in the previous step to ` `, as shown in the code below. This completes the connection between your React application and the Asgardeo cloud. +You also need to pass the Client ID and Base URL values you copied in the previous step to ` `, as shown in the code below. This completes the connection between your React application and the WSO2 Identity Platform cloud. ```javascript title="src/main.jsx" import { StrictMode } from 'react' @@ -164,7 +164,7 @@ createRoot(document.getElementById('root')).render( ## Implement user login -In this step, we use the drop-in components provided by the Asgardeo React SDK to add user login and logout functionality. +In this step, we use the drop-in components provided by the WSO2 Identity Platform React SDK to add user login and logout functionality. Simply replace the contents of your `App.jsx` file with the following code. @@ -191,11 +191,11 @@ export default App ``` In the above code, we first import the drop-in components ` `, ` ` -, ` `, and ` ` from the Asgardeo React SDK. +, ` `, and ` ` from the WSO2 Identity Platform React SDK. -We then use the ` ` control component to check whether the current user is authenticated. If the user is signed in, we render the ` ` component to display a logout button. When the user clicks it, the component automatically handles the logout process by sending the logout request to Asgardeo and removing the stored tokens behind the scenes. +We then use the ` ` control component to check whether the current user is authenticated. If the user is signed in, we render the ` ` component to display a logout button. When the user clicks it, the component automatically handles the logout process by sending the logout request to WSO2 Identity Platform and removing the stored tokens behind the scenes. -Next, we use the ` ` control component to check whether the user is not authenticated. If so, we render the ` ` component. This component constructs the login request and redirects the user to Asgardeo using the configured Client ID and Base URL. Once authentication is successful, Asgardeo redirects the user back to your application with the required tokens, which the SDK processes automatically to establish the authenticated user context without any additional code from you. +Next, we use the ` ` control component to check whether the user is not authenticated. If so, we render the ` ` component. This component constructs the login request and redirects the user to WSO2 Identity Platform using the configured Client ID and Base URL. Once authentication is successful, WSO2 Identity Platform redirects the user back to your application with the required tokens, which the SDK processes automatically to establish the authenticated user context without any additional code from you. Now you can understand what happens behind the scenes when using these components, but the key takeaway is that this is essentially all the code required to implement fully functional login and logout capabilities in your application @@ -203,7 +203,7 @@ You’re completely free to style these components using Tailwind or any other C ## Display user profile -Before we test our application, let’s also add some code to render the user profile of the logged-in user. Again, simply import and add ` ` component from Asgardeo React SDK as highlighted in the following code. +Before we test our application, let’s also add some code to render the user profile of the logged-in user. Again, simply import and add ` ` component from WSO2 Identity Platform React SDK as highlighted in the following code. ```javascript title="src/App.jsx" hl_lines="1 15-17" @@ -234,7 +234,7 @@ In the above code, we added the ` ` component, which provides a de Alternatively, you can use ` `, which shows a dropdown menu with built-in user details and sign-out functionality. The ` ` component offers a render-prop pattern, allowing you to access user profile information programmatically. -Now, we are ready to try-out our React application secured with Asgardeo. Let’s start the application again by running the following code. +Now, we are ready to try-out our React application secured with WSO2 Identity Platform. Let’s start the application again by running the following code. === "npm" ```bash @@ -251,7 +251,7 @@ Now, we are ready to try-out our React application secured with Asgardeo. Let’ Now, if you visit [http://localhost:5173](http://localhost:5173) in your browser, you should see your application, which will look like the screenshot below. For simplicity, we haven’t added any CSS styles yet. -Now, if you click the `Login` button, you will be redirected to the Asgardeo cloud, where you can sign in using a test user account. If you haven’t created a test user yet, you can follow [this guide]({{ base_path }}/guides/users/manage-users/#onboard-single-user) to set one up. +Now, if you click the `Login` button, you will be redirected to the WSO2 Identity Platform cloud, where you can sign in using a test user account. If you haven’t created a test user yet, you can follow [this guide]({{ base_path }}/guides/users/manage-users/#onboard-single-user) to set one up. Once you authenticate with your test user credentials, you will be redirected back to the application, and your test user profile will be displayed, as shown in the screenshot below. @@ -267,19 +267,19 @@ Since React is a client-side framework, your application is downloaded and runs The de-facto standard for securing these APIs is OAuth2 access tokens and that is the right security mechanism that you should use to secure your backend APIs. This also means your application must obtain an OAuth2 access token for the currently logged-in user and include it when making secure API calls. -To give you a quick idea of what happens behind the scenes, although you don’t need to worry about it too much. The Asgardeo React SDK retrieves two tokens after a user successfully authenticates: +To give you a quick idea of what happens behind the scenes, although you don’t need to worry about it too much. The WSO2 Identity Platform React SDK retrieves two tokens after a user successfully authenticates: - **OpenID ID token** – Meant for the application. It helps determine authentication state and retrieve user attributes. - **OAuth2 access token** – This token is sent with API requests when your application calls protected resources on behalf of the user. -As a React developer, you’re already familiar with the browser’s `fetch API` for calling HTTP endpoints. The Asgardeo React SDK allows you to access the OAuth2 access token and attach it as the Authorization header when making API calls. +As a React developer, you’re already familiar with the browser’s `fetch API` for calling HTTP endpoints. The WSO2 Identity Platform React SDK allows you to access the OAuth2 access token and attach it as the Authorization header when making API calls. However, you don’t even need to handle this manually. The SDK provides a utility HTTP client that automatically attaches the current OAuth2 access token to outgoing requests. This way, token handling is managed securely by the SDK. -Ideally, we would call a backend API that you created and secured with Asgardeo. To keep things simple, we’ll take a shortcut and call an endpoint exposed by Asgardeo itself. +Ideally, we would call a backend API that you created and secured with WSO2 Identity Platform. To keep things simple, we’ll take a shortcut and call an endpoint exposed by WSO2 Identity Platform itself. -In this section, we’ll use the SCIM 2.0 /Me endpoint, which returns the profile details of the logged-in user. The same approach applies when calling your own backend APIs, as long as they are secured with Asgardeo. +In this section, we’ll use the SCIM 2.0 /Me endpoint, which returns the profile details of the logged-in user. The same approach applies when calling your own backend APIs, as long as they are secured with WSO2 Identity Platform. Following React best practices, let’s first create a new component called MyProfile.jsx and add the following code. ```javascript title="src/MyProfile.jsx" @@ -325,7 +325,7 @@ export default MyProfile; ``` -In the above code apart from `useState` hook we have imported `useAsgardeo` hook which is provided by the Asgardeo React SDK and gives us access to authentication state and a built-in HTTP client. +In the above code apart from `useState` hook we have imported `useAsgardeo` hook which is provided by the WSO2 Identity Platform React SDK and gives us access to authentication state and a built-in HTTP client. Then we have received two important constants by calling the `useAsgardeo` hook. @@ -370,7 +370,7 @@ After revisiting your application and logging in successfully, you should see th In real-world React applications, it’s common to secure certain routes while keeping others public. Some paths should only be accessible to authenticated users. -The Asgardeo React SDK provides pluggable utilities that work with popular routing libraries such as React Router and TanStack Router. In this section, we’ll look at how to secure a route in our application using React Router. +The WSO2 Identity Platform React SDK provides pluggable utilities that work with popular routing libraries such as React Router and TanStack Router. In this section, we’ll look at how to secure a route in our application using React Router. First, install the following additional packages in your application. @@ -461,6 +461,6 @@ Once you authenticate, you’ll be redirected back, and clicking the “My Profi ## Conclusion -This guide showed how to secure a React application using Asgardeo and its React SDK without building custom authentication from scratch. By using ready-to-use components like ` `, ` `, and ` `, you can quickly integrate authentication into any React project. +This guide showed how to secure a React application using WSO2 Identity Platform and its React SDK without building custom authentication from scratch. By using ready-to-use components like ` `, ` `, and ` `, you can quickly integrate authentication into any React project. With the SDK, you can implement a complete authentication flow, securely call protected APIs via the `useAsgardeo` hook’s built-in HTTP client, and protect routes using ` `. This approach delivers a production-ready authentication system while letting developers focus on building application features instead of dealing with security boilerplate. diff --git a/en/asgardeo/docs/tutorials/secure-agentic-ai-systems.md b/en/asgardeo/docs/tutorials/secure-agentic-ai-systems.md index d9482aa870..45933a9f12 100644 --- a/en/asgardeo/docs/tutorials/secure-agentic-ai-systems.md +++ b/en/asgardeo/docs/tutorials/secure-agentic-ai-systems.md @@ -1,3 +1,3 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../includes/tutorials/secure-agentic-ai-systems.md" %} diff --git a/en/asgardeo/docs/tutorials/secure-spring-boot-api.md b/en/asgardeo/docs/tutorials/secure-spring-boot-api.md index 06905149e3..e00d89f002 100644 --- a/en/asgardeo/docs/tutorials/secure-spring-boot-api.md +++ b/en/asgardeo/docs/tutorials/secure-spring-boot-api.md @@ -1,8 +1,8 @@ -# Secure Your Spring Boot API with Asgardeo +# Secure Your Spring Boot API with WSO2 Identity Platform Spring Boot is a Java framework that simplifies the development of robust applications by offering a production-ready environment with minimal configurations. Spring security provides comprehensive tools to facilitate authentication and authorization for REST APIs. Spring Security seamlessly integrates with Spring Boot and allows developers to focus on business logic rather than boilerplate code. -The goal of this tutorial is to explore how we can enhance API security by integrating Asgardeo, a comprehensive identity and access management solution, with Spring Security. This combination will handle authentication and authorization processes effectively. +The goal of this tutorial is to explore how we can enhance API security by integrating WSO2 Identity Platform, a comprehensive identity and access management solution, with Spring Security. This combination will handle authentication and authorization processes effectively. Let's look at the following example scenario. @@ -20,7 +20,7 @@ The application users are divided into the following two roles with different le - `Reporters` can create and list issues. - `Fix-Verifiers` have full access to the application and can perform all operations. -You are tasked with delegating access to the application so that users are given appropriate levels of access based on their roles. Let's use Asgardeo to achieve this. +You are tasked with delegating access to the application so that users are given appropriate levels of access based on their roles. Let's use WSO2 Identity Platform to achieve this. ## Step 1: Create a simple CRUD API @@ -30,17 +30,17 @@ You can find a sample implementation in the following [repository](https://githu -## Step 2: Integrate your service with Asgardeo +## Step 2: Integrate your service with WSO2 Identity Platform - Follow the instructions below to connect your Issue Management service with Asgardeo. + Follow the instructions below to connect your Issue Management service with WSO2 Identity Platform. -### Step 2.1: Register your API resources in Asgardeo +### Step 2.1: Register your API resources in WSO2 Identity Platform -First, let's register your issue management REST API with Asgardeo. To do so, +First, let's register your issue management REST API with WSO2 Identity Platform. To do so, -1. Go to your organization from the [Asgardeo Console](https://console.asgardeo.io/). +1. Go to your organization from the [WSO2 Identity Platform Console](https://console.asgardeo.io/). -2. [Register your API in Asgardeo]({{base_path}}/guides/api-authorization/#register-an-api-resource). +2. [Register your API in WSO2 Identity Platform]({{base_path}}/guides/api-authorization/#register-an-api-resource). 3. [Define permissions for the API resource]({{base_path}}/guides/api-authorization/#define-permissions-for-an-api-resource) with the following permissions. @@ -49,11 +49,11 @@ First, let's register your issue management REST API with Asgardeo. To do so, - issues:update-issues:delete-### Step 2.2 Register your application in Asgardeo +### Step 2.2 Register your application in WSO2 Identity Platform -You need to register your application in Asgardeo and connect your API resources to it. To do so, +You need to register your application in WSO2 Identity Platform and connect your API resources to it. To do so, -1. [Create a standard-based application in Asgardeo]({{base_path}}/guides/applications/register-standard-based-app/) by selecting the grant type as `Code` and the access token type as `JWT`. +1. [Create a standard-based application in WSO2 Identity Platform]({{base_path}}/guides/applications/register-standard-based-app/) by selecting the grant type as `Code` and the access token type as `JWT`. 2. [Connect the API resources]({{base_path}}/guides/api-authorization/#authorize-the-api-resources-for-an-app) with the application that you created in Step 1 above. @@ -66,34 +66,34 @@ To do so, [create roles and associate to the application]({{base_path}}/guides/a - Reporter - Assign `create:isses` and `view:issues` permissions. - Fix-Verifier - Assign all permissions. -### Step 2.4 Assign roles to user groups in Asgardeo +### Step 2.4 Assign roles to user groups in WSO2 Identity Platform -For the application roles defined in Step 2.3 above to take effect, we need to assign those roles to users in Asgardeo. The best way to do this is to create user groups and assign the relevant roles to each group. +For the application roles defined in Step 2.3 above to take effect, we need to assign those roles to users in WSO2 Identity Platform. The best way to do this is to create user groups and assign the relevant roles to each group. To do so, -1. [Create user groups in Asgardeo]({{base_path}}/guides/users/manage-groups/). For this scenario, let's create two groups and name them `Reporter` and `Fix-Verifier`. +1. [Create user groups in WSO2 Identity Platform]({{base_path}}/guides/users/manage-groups/). For this scenario, let's create two groups and name them `Reporter` and `Fix-Verifier`. 2. [Assign application roles]({{base_path}}/guides/api-authorization/#assign-roles-to-groups) created in step 2.3 above to the relevant groups. -### Step 2.5 Assign users to groups in Asgardeo +### Step 2.5 Assign users to groups in WSO2 Identity Platform -Now that you have assigned the application roles to the relevant user groups in Asgardeo, let's add users to these groups so that they can access the API resources. +Now that you have assigned the application roles to the relevant user groups in WSO2 Identity Platform, let's add users to these groups so that they can access the API resources. To do so, -1. [Onboard users to Asgardeo]({{base_path}}/guides/users/manage-users/#onboard-a-user). +1. [Onboard users to WSO2 Identity Platform]({{base_path}}/guides/users/manage-users/#onboard-a-user). 2. [Assign users to relevant groups]({{base_path}}/guides/users/manage-users/#assign-groups). ## Step 3: Configure Spring Security -In your Spring project, do the following configurations so that it is correctly integrated with Asgardeo.: +In your Spring project, do the following configurations so that it is correctly integrated with WSO2 Identity Platform.: -1. Create a security configuration file and include the following JWT decoder to validate Asgardeo issued tokens. +1. Create a security configuration file and include the following JWT decoder to validate WSO2 Identity Platform issued tokens. !!! note - Asgardeo issues access tokens of `at+jwt` type. + WSO2 Identity Platform issues access tokens of `at+jwt` type. ``` java NimbusJwtDecoder jwtDecoder = NimbusJwtDecoder.withJwkSetUri(jwkSetUri).jwtProcessorCustomizer(customizer -> { @@ -130,7 +130,7 @@ Let's try to access the API resources of the sample application as a `Reporter` &scope=issues:create+issues:delete+issues:update+issues:view ``` -2. Log in as a `Reporter` user to Asgardeo and provide consent to the application to access the shown scopes. +2. Log in as a `Reporter` user to WSO2 Identity Platform and provide consent to the application to access the shown scopes. {: width="400" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} diff --git a/en/asgardeo/docs/tutorials/smart-on-fhir.md b/en/asgardeo/docs/tutorials/smart-on-fhir.md index e05f81b8c9..626ccff320 100644 --- a/en/asgardeo/docs/tutorials/smart-on-fhir.md +++ b/en/asgardeo/docs/tutorials/smart-on-fhir.md @@ -1,6 +1,6 @@ -# Integrate Asgardeo with SMART on FHIR +# Integrate WSO2 Identity Platform with SMART on FHIR -Follow the tutorial below to learn how you can leverage Asgardeo as an identity provider, to implement a robust authentication and authorization mechanism for your healthcare applications built on SMART on FHIR. +Follow the tutorial below to learn how you can leverage WSO2 Identity Platform as an identity provider, to implement a robust authentication and authorization mechanism for your healthcare applications built on SMART on FHIR. ## What is FHIR? @@ -14,25 +14,25 @@ Follow the tutorial below to learn how you can leverage Asgardeo as an identity - Security - The framework uses open standards such as OAuth2 and OpenID Connect for authorization and authentication to ensure EHR systems are accessed securely and in compliance with privacy regulations such as HIPAA. -## How can Asgardeo help? +## How can WSO2 Identity Platform help? -Asgardeo, a cloud-native Identity and Access Management (IAM) solution, is equipped with support for open standards such as OpenID Connect and Oauth 2.0 that developers can simply integrate right into their SMART on FHIR applications. This helps developers to safeguard patient information, comply with privacy regulations, and manage access to FHIR resources based on user roles. +WSO2 Identity Platform, a cloud-native Identity and Access Management (IAM) solution, is equipped with support for open standards such as OpenID Connect and Oauth 2.0 that developers can simply integrate right into their SMART on FHIR applications. This helps developers to safeguard patient information, comply with privacy regulations, and manage access to FHIR resources based on user roles. -Asgardeo simplifies and automates identity and permission management, making it an ideal solution for integrating third-party applications securely within the healthcare ecosystem. +WSO2 Identity Platform simplifies and automates identity and permission management, making it an ideal solution for integrating third-party applications securely within the healthcare ecosystem. -## How do I integrate Asgardeo into my app? +## How do I integrate WSO2 Identity Platform into my app? -This guide outlines how Asgardeo can be integrated into your healthcare apps. We have created a Postman collection to automate this process so that it enhances efficiency and ensures consistency in configurations. +This guide outlines how WSO2 Identity Platform can be integrated into your healthcare apps. We have created a Postman collection to automate this process so that it enhances efficiency and ensures consistency in configurations. ### Prerequisite -You need to have an Asgardeo account. If you do not have one, create one for free in Asgardeo(https://asgardeo.io/signup){target="_blank"}. Follow the [documentation]({{base_path}}/get-started/) to learn how to get started. +You need to have an WSO2 Identity Platform account. If you do not have one, create one for free in WSO2 Identity Platform(https://asgardeo.io/signup){target="_blank"}. Follow the [documentation]({{base_path}}/get-started/) to learn how to get started. -### Step 1: Register an application in Asgardeo +### Step 1: Register an application in WSO2 Identity Platform -Follow the steps below to register an application in Asgardeo. +Follow the steps below to register an application in WSO2 Identity Platform. -1. Log in to the [Asgardeo Console](https://console.asgardeo.io/){target="_blank"} and go to **Applications**. +1. Log in to the [WSO2 Identity Platform Console](https://console.asgardeo.io/){target="_blank"} and go to **Applications**. 2. Click **New Application** and select **Standard-Based Application**. @@ -46,7 +46,7 @@ Follow the steps below to register an application in Asgardeo. ### Step 2: Authorize application to access REST APIs -Now that you have registered an application in Asgardeo, the next step is to provide it authorization to perform the following actions on the listed REST APIs, +Now that you have registered an application in WSO2 Identity Platform, the next step is to provide it authorization to perform the following actions on the listed REST APIs,@@ -152,7 +152,7 @@ Now that you have registered an application in Asgardeo, the next step is to pro To do so, -1. On the [Asgardeo Console](https://console.asgardeo.io/), go to **Applications**. +1. On the [WSO2 Identity Platform Console](https://console.asgardeo.io/), go to **Applications**. 2. Select the created application and go to its **API Authorization** tab. @@ -174,13 +174,13 @@ To do so, ### Step 3: Configure the Postman collection -Now that you have registered and configured an application in Asgardeo, you are able to use its credentials to obtain an access token and access Asgardeo's REST APIs. +Now that you have registered and configured an application in WSO2 Identity Platform, you are able to use its credentials to obtain an access token and access WSO2 Identity Platform's REST APIs. !!! abstract "" We have created a Postman collection to automate the following process: - - Get a bearer token to access Asgardeo REST APIs. + - Get a bearer token to access WSO2 Identity Platform REST APIs. - Create the `fhirUser` user attribute. This will be used as the identity of a user accessing FHIR resources. @@ -202,7 +202,7 @@ Follow the steps below to download and run the Postman collection: 1. Download the Postman collection from [GitHub](https://github.com/wso2-enterprise/open-healthcare/blob/main/scripts/postman-collections/smartonfhir-asgardeo.postman_collection.json){target="_blank"} and import it to Postman. -2. In the Postman collection named **Asgardeo**, go to the **Authorization** tab and do the following: +2. In the Postman collection named **WSO2 Identity Platform**, go to the **Authorization** tab and do the following: 1. Under **Auth Type**, select **Basic Auth**. @@ -230,9 +230,9 @@ Follow the steps below to download and run the Postman collection: 4. Once the Postman collection is configured, you are ready to run it. To do so, - 1. Navigate to the **Asgardeo** > **Asgardeo-configs** folder. + 1. Navigate to the **WSO2 Identity Platform** > **WSO2 Identity Platform-configs** folder. - 2. Click the three dots corresponding to **Asgardeo-configs** and click **Run folder**. + 2. Click the three dots corresponding to **WSO2 Identity Platform-configs** and click **Run folder**. 3. Ensure no errors occur and troubleshoot any errors that arise. @@ -240,11 +240,11 @@ Follow the steps below to download and run the Postman collection: ### Step 4: Verify that everything works -Now that you have created the `fhirUser` user attribute and registered your SMART on FHIR app in Asgardeo, let's try to log into your application as the user and obtain the ID token. If everything has worked, the ID token should contain the `fhirUser` attribute. +Now that you have created the `fhirUser` user attribute and registered your SMART on FHIR app in WSO2 Identity Platform, let's try to log into your application as the user and obtain the ID token. If everything has worked, the ID token should contain the `fhirUser` attribute. To do so, -1. In the same Postman collection, navigate to the **Asgardeo** > **authorization-code-grant-flow** folder. +1. In the same Postman collection, navigate to the **WSO2 Identity Platform** > **authorization-code-grant-flow** folder. 2. Open the **get-token** request and go to its **Authorization** tab. @@ -254,7 +254,7 @@ To do so, {: width="600" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} -5. You will be directed to the Asgardeo login page. Enter the user's credentials and click **Sign In**. If prompted, provide permission for the application to read the `fhirUser` attribute. +5. You will be directed to the WSO2 Identity Platform login page. Enter the user's credentials and click **Sign In**. If prompted, provide permission for the application to read the `fhirUser` attribute. 6. Once authenticated, you will be redirected back to Postman. Copy the `id_token` value and decode it to find the following data. diff --git a/en/asgardeo/docs/tutorials/wso2-ai-gateway-with-agent-identity-aware-access-control.md b/en/asgardeo/docs/tutorials/wso2-ai-gateway-with-agent-identity-aware-access-control.md index 7810616bd4..40163702c0 100644 --- a/en/asgardeo/docs/tutorials/wso2-ai-gateway-with-agent-identity-aware-access-control.md +++ b/en/asgardeo/docs/tutorials/wso2-ai-gateway-with-agent-identity-aware-access-control.md @@ -1,3 +1,3 @@ -{% set product_name = "Asgardeo" %} +{% set product_name = "WSO2 Identity Platform" %} {% include "../../../includes/tutorials/wso2-ai-gateway-with-agent-identity-aware-access-control.md" %} diff --git a/en/asgardeo/mkdocs.yml b/en/asgardeo/mkdocs.yml index 4d9a27f8a3..dc7ed92659 100644 --- a/en/asgardeo/mkdocs.yml +++ b/en/asgardeo/mkdocs.yml @@ -17,17 +17,17 @@ INHERIT: ../base.yml # Project information -site_name: &site_name Asgardeo -site_description: Asgardeo Learning Center +site_name: &site_name WSO2 Identity Platform +site_description: WSO2 Identity Platform Learning Center site_url: https://wso2.com/asgardeo/docs/ edit_uri: https://github.com/wso2/docs-is/edit/master/en/asgardeo/docs/ # Configuration theme: custom_dir: ../theme/material - logo: assets/images/asgardeo-docs-logo-dark.svg - logo_light: assets/images/asgardeo-docs-logo.svg - favicon: assets/images/asgardeo-favicon.svg + logo: assets/images/IP-docs-logo-dark.svg + logo_light: assets/images/IP-docs-logo-white.svg + favicon: assets/images/pulse.svg extra: base_path: /asgardeo/docs @@ -101,7 +101,7 @@ extra: - title: Tutorials url: Tutorials|Tutorials - Overview - title: SDKs and Integrations - url: Developer Tools|SDKs|Integrate Asgardeo into your application + url: Developer Tools|SDKs|Integrate WSO2 Identity Platform into your application - title: Community and Support icon: octicons/light-bulb-16 icon_color: icon-color-2 @@ -213,8 +213,8 @@ nav: - Create Account: get-started/create-asgardeo-account.md # TODO: Clean this once we revist the navigation structure again # - Try login with sample: get-started/try-it-application.md - # - Start integrating Asgardeo into apps: - # - Start integrating Asgardeo into apps: get-started/start-integrating-apps/index.md + # - Start integrating WSO2 Identity Platform into apps: + # - Start integrating WSO2 Identity Platform into apps: get-started/start-integrating-apps/index.md # - Try for a sample app: # - Try for a sample app: get-started/try-samples/index.md # - Single Page apps: @@ -435,8 +435,8 @@ nav: - Group-based provisioning: guides/users/outbound-provisioning/group-based-provisioning.md - Configure an outbound connector: - SCIM2: guides/users/outbound-provisioning/outbound-connectors/scim2.md - - Migrate users to Asgardeo: - - Migrate users to Asgardeo: guides/users/migrate-users/index.md + - Migrate users to WSO2 Identity Platform: + - Migrate users to WSO2 Identity Platform: guides/users/migrate-users/index.md - Migrate user accounts: guides/users/migrate-users/migrate-users.md - Migrate user passwords: guides/users/migrate-users/migrate-passwords.md - Manage attributes and mappings: @@ -566,7 +566,7 @@ nav: - Configure custom domains: guides/branding/configure-custom-domains.md - Customize email templates: guides/branding/customize-email-templates.md - Customize SMS templates: guides/branding/customize-sms-templates.md - - Localization in Asgardeo: guides/branding/localization.md + - Localization in WSO2 Identity Platform: guides/branding/localization.md - Extend with service extensions: - Understanding service extensions: guides/service-extensions/understanding-service-extensions.md - In-flow extensions: @@ -581,8 +581,8 @@ nav: - Understanding webhooks: guides/webhooks/understanding-webhooks.md - Setup webhooks: guides/webhooks/setup-webhooks.md - Webhook events and payloads: guides/webhooks/webhook-events-and-payloads.md - - Your Asgardeo: - - Your Asgardeo: guides/your-asgardeo/index.md + - Your WSO2 Identity Platform: + - Your WSO2 Identity Platform: guides/your-asgardeo/index.md - Manage root organizations: guides/your-asgardeo/manage-root-organizations.md - Manage environments: - Manage environments: guides/your-asgardeo/manage-environments/index.md @@ -590,12 +590,12 @@ nav: - Self-service: guides/your-asgardeo/asgardeo-self-service.md - Recover your password: guides/your-asgardeo/recover-password.md - Delete your user account: guides/your-asgardeo/delete-your-user-account.md - - Subscribe to Asgardeo: - - Subscribe to Asgardeo: guides/your-asgardeo/subscribe-to-asgardeo/index.md + - Subscribe to WSO2 Identity Platform: + - Subscribe to WSO2 Identity Platform: guides/your-asgardeo/subscribe-to-asgardeo/index.md - via Billing Portal: guides/your-asgardeo/subscribe-to-asgardeo/subscribe-via-billing-portal.md - via Azure Marketplace: guides/your-asgardeo/subscribe-to-asgardeo/subscribe-via-azure-marketplace.md - - Asgardeo logs: - - Asgardeo logs: guides/asgardeo-logs/index.md + - WSO2 Identity Platform logs: + - WSO2 Identity Platform logs: guides/asgardeo-logs/index.md - Diagnostic logs: guides/asgardeo-logs/diagnostic-logs.md - Audit logs: - Audit logs: guides/asgardeo-logs/audit-logs/index.md @@ -603,8 +603,8 @@ nav: - Remote log publish: guides/asgardeo-logs/remote-log-publish.md - Monitoring: - Monitoring: guides/monitoring/index.md - - PII in Asgardeo logs: guides/monitoring/pii-in-asgardeo-logs.md - - Asgardeo events: guides/monitoring/asgardeo-events.md + - PII in WSO2 Identity Platform logs: guides/monitoring/pii-in-asgardeo-logs.md + - WSO2 Identity Platform events: guides/monitoring/asgardeo-events.md - Organization insights: guides/organization-insights.md - Agentic AI: - MCP Authorization: @@ -624,14 +624,14 @@ nav: - Tutorials - Overview: tutorials/index.md - Authenticate users into Android applications: tutorials/auth-users-into-android-apps.md - Authenticate users into Flutter applications: tutorials/auth-users-into-flutter-apps.md - - Connect Asgardeo as an OIDC attribute provider (with Microsoft Entra Verified ID): tutorials/connect-asgardeo-with-ms-entra.md - - Connect Asgardeo as an OIDC attribute provider (with MATTR): tutorials/connect-asgardeo-with-mattr.md - - Secure Spring Boot API with Asgardeo: tutorials/secure-spring-boot-api.md - - Integrate Asgardeo with Smart on FHIR healthcare apps: tutorials/smart-on-fhir.md - - Secure Agentic AI Systems with Asgardeo: tutorials/secure-agentic-ai-systems.md + - Connect WSO2 Identity Platform as an OIDC attribute provider (with Microsoft Entra Verified ID): tutorials/connect-asgardeo-with-ms-entra.md + - Connect WSO2 Identity Platform as an OIDC attribute provider (with MATTR): tutorials/connect-asgardeo-with-mattr.md + - Secure Spring Boot API with WSO2 Identity Platform: tutorials/secure-spring-boot-api.md + - Integrate WSO2 Identity Platform with Smart on FHIR healthcare apps: tutorials/smart-on-fhir.md + - Secure Agentic AI Systems with WSO2 Identity Platform: tutorials/secure-agentic-ai-systems.md - Implement End-to-End Authorization for MCP servers: tutorials/end-to-end-mcp-authorization-with-asgardeo.md - SDKs: - - Integrate Asgardeo into your application: sdks/index.md + - Integrate WSO2 Identity Platform into your application: sdks/index.md - SDK Documentation: - React SDK: - Overview: sdks/react/overview.md @@ -697,7 +697,7 @@ nav: - Guides: - Accessing Protected APIs: sdks/nextjs/guides/accessing-protected-apis.md - Protecting Routes: sdks/nextjs/guides/protecting-routes.md - - Asgardeo MCP Server: sdks/asgardeo-mcp-server.md + - WSO2 Identity Platform MCP Server: sdks/asgardeo-mcp-server.md - APIs: - APIs - Overview: apis/index.md - Management APIs: @@ -804,8 +804,8 @@ nav: - References: - References - Overview: references/index.md - Operational policies: references/operational-policies.md - - Asgardeo outbound IP addresses: references/asgardeo-outbound-ip-addresses.md - - Asgardeo user roles: references/user-management/user-roles.md + - WSO2 Identity Platform outbound IP addresses: references/asgardeo-outbound-ip-addresses.md + - WSO2 Identity Platform user roles: references/user-management/user-roles.md - SCIM2 Custom User Schema Support: references/user-management/add-scim2-custom-user-schema-support.md - App configurations: - App configurations: references/app-settings/index.md @@ -845,14 +845,14 @@ nav: - Version 1.x: - API v1.0 contract to implement: references/service-extensions/pre-flow-extensions/pre-update-profile-action/pre-update-profile-action-v1.0.md - Accessibility compliance: references/accessibility.md - - Data residency in Asgardeo: references/data-residency-in-asgardeo.md + - Data residency in WSO2 Identity Platform: references/data-residency-in-asgardeo.md - API resources and scopes required for MCP tools: references/mcp-tool-api-resource-access.md - Production checklist: - references/production-checklist/index.md - Readiness check: references/production-checklist/readiness-check.md - Security check: references/production-checklist/security-check.md - Best practices: references/production-checklist/best-practices.md - - Asgardeo rate limits: references/rate-limits.md + - WSO2 Identity Platform rate limits: references/rate-limits.md - Tutorials: - Build your own push authenticator app: references/tutorials/build-your-own-push-authenticator-app.md - IAM concepts: @@ -886,7 +886,7 @@ nav: - Prerequisite: complete-guides/react/prerequisite.md - Configure an application: complete-guides/react/register-an-application.md - Create a React app: complete-guides/react/create-a-react-app.md - - Configure Asgardeo SDK: complete-guides/react/install-asgardeo-sdk.md + - Configure WSO2 Identity Platform SDK: complete-guides/react/install-asgardeo-sdk.md - Add login and logout: complete-guides/react/add-login-and-logout.md - Display user details: complete-guides/react/display-logged-in-user-details.md - Securing Routes: complete-guides/react/securing-routes-within-the-app.md @@ -911,7 +911,7 @@ nav: - Prerequisite: complete-guides/nextjs/prerequisite.md - Register an application: complete-guides/nextjs/register-an-application.md - Create a Next.js app: complete-guides/nextjs/create-app.md - - Configure Asgardeo SDK: complete-guides/nextjs/install-asgardeo-sdk.md + - Configure WSO2 Identity Platform SDK: complete-guides/nextjs/install-asgardeo-sdk.md - Add login and logout: complete-guides/nextjs/add-login-and-logout.md - Display user details: complete-guides/nextjs/display-logged-in-user-details.md - Securing Routes: complete-guides/nextjs/securing-routes-within-the-app.md @@ -923,7 +923,7 @@ nav: - Prerequisites: complete-guides/app-native/prerequisites.md - Register an application: complete-guides/app-native/register-an-application.md - Create an app for app-native authentication: complete-guides/app-native/create-app.md - - Configure Asgardeo SDK: complete-guides/app-native/configure-provider.md + - Configure WSO2 Identity Platform SDK: complete-guides/app-native/configure-provider.md - Add login and logout: complete-guides/app-native/add-login-and-logout.md - Add MFA using app-native APIs: complete-guides/app-native/add-mfa.md - Add Social Login using app-native APIs: complete-guides/app-native/add-social-login.md @@ -934,7 +934,7 @@ nav: - Prerequisite: complete-guides/expressjs/prerequisite.md - Configure an application: complete-guides/expressjs/register-an-application.md - Create an Express.js app: complete-guides/expressjs/create-an-expressjs-app.md - - Configure Passport Asgardeo: complete-guides/expressjs/install-passport-asgardeo.md + - Configure Passport WSO2 Identity Platform: complete-guides/expressjs/install-passport-asgardeo.md - Add login and logout: complete-guides/expressjs/add-login-and-logout.md - Persist user sessions: complete-guides/expressjs/persist-user-sessions.md - Display user details: complete-guides/expressjs/display-logged-in-user-details.md @@ -946,7 +946,7 @@ nav: - Prerequisite: complete-guides/angular/prerequisite.md - Register an application: complete-guides/angular/register-an-application.md - Create an Angular app: complete-guides/angular/create-app.md - - Configure Asgardeo provider: complete-guides/angular/install-asgardeo-sdk.md + - Configure WSO2 Identity Platform provider: complete-guides/angular/install-asgardeo-sdk.md - Add login and logout: complete-guides/angular/add-login-and-logout.md - Display user details: complete-guides/angular/display-logged-in-user-details.md - Securing Routes: complete-guides/angular/securing-routes-within-the-app.md @@ -958,7 +958,7 @@ nav: - Prerequisite: complete-guides/javascript/prerequisite.md - Register an application: complete-guides/javascript/register-an-application.md - Create a JavaScript app: complete-guides/javascript/create-app.md - - Configure Asgardeo SDK: complete-guides/javascript/install-asgardeo-sdk.md + - Configure WSO2 Identity Platform SDK: complete-guides/javascript/install-asgardeo-sdk.md - Add login and logout: complete-guides/javascript/add-login-and-logout.md - Display user details: complete-guides/javascript/display-logged-in-user-details.md - Accessing protected API : complete-guides/javascript/accessing-protected-api.md diff --git a/en/base.yml b/en/base.yml index 9e4de89e9e..2514922e27 100644 --- a/en/base.yml +++ b/en/base.yml @@ -195,7 +195,7 @@ extra: Setup: icon: octicons/gear-16 level: 1 - Asgardeo MCP Server: + WSO2 Identity Platform MCP Server: icon: assets/libs/custom-icons/mcp.svg level: 1 React SDK: diff --git a/en/includes/complete-guides/actions/introduction.md b/en/includes/complete-guides/actions/introduction.md index ffff3e4209..0b00125fc3 100644 --- a/en/includes/complete-guides/actions/introduction.md +++ b/en/includes/complete-guides/actions/introduction.md @@ -1,15 +1,15 @@ WSO2 Identity Server (WSO2 IS) is widely recognized as a powerful, open-source identity and access management solution -that offers a high degree of extensibility to meet diverse business requirements. Asgardeo, which is built on the same +that offers a high degree of extensibility to meet diverse business requirements. WSO2 Identity Platform, which is built on the same robust core technology as WSO2 IS, inherits this extensibility, providing users the flexibility to adapt and extend the platform according to their specific needs. -With the introduction of the new service-based extension model, both WSO2 IS and Asgardeo now offer a streamlined, +With the introduction of the new service-based extension model, both WSO2 IS and WSO2 Identity Platform now offer a streamlined, service-oriented approach to extend core functionalities. This model allows developers to implement custom logic externally without modifying the core product, thereby ensuring maintainability, scalability, and ease of upgrades. In this guide, we provide sample Pre-Flow Extensions that demonstrate how to use the service-based extension model to customize the behavior of various authentication and user management actions. Whether you are working with WSO2 IS or -Asgardeo, the samples and approaches detailed here will help you understand how to build and deploy your own service +WSO2 Identity Platform, the samples and approaches detailed here will help you understand how to build and deploy your own service extensions effectively. We will cover the following extensions and use cases: @@ -24,7 +24,7 @@ We will cover the following extensions and use cases: ## Learning Objectives By the end of this guide, you will have a clear understanding of how to implement service-based extensions in both WSO2 -Identity Server (WSO2 IS) and Asgardeo. You will be equipped to enhance and tailor your identity management workflows to +Identity Server (WSO2 IS) and WSO2 Identity Platform. You will be equipped to enhance and tailor your identity management workflows to better suit your organization's requirements by integrating custom logic into key parts of the authentication and user management flows. Specifically, this guide will help you: diff --git a/en/includes/complete-guides/actions/pre-issue-access-token-action-in-choreo.md b/en/includes/complete-guides/actions/pre-issue-access-token-action-in-choreo.md index adbd5f3a66..dd2c41835f 100644 --- a/en/includes/complete-guides/actions/pre-issue-access-token-action-in-choreo.md +++ b/en/includes/complete-guides/actions/pre-issue-access-token-action-in-choreo.md @@ -511,7 +511,7 @@ securely.  -The API key will be generated along with an application in Asgardeo. Copy and save the key securely for later use in +The API key will be generated along with an application in WSO2 Identity Platform. Copy and save the key securely for later use in your API calls. ### Test Deployed Service diff --git a/en/includes/complete-guides/actions/pre-issue-access-token-action-use-case.md b/en/includes/complete-guides/actions/pre-issue-access-token-action-use-case.md index ca177637b8..f3d00dfe9a 100644 --- a/en/includes/complete-guides/actions/pre-issue-access-token-action-use-case.md +++ b/en/includes/complete-guides/actions/pre-issue-access-token-action-use-case.md @@ -1,4 +1,4 @@ -The Pre-Issue Access Token action in Asgardeo allows you to execute custom logic just before an access token is issued +The Pre-Issue Access Token action in WSO2 Identity Platform allows you to execute custom logic just before an access token is issued during the OAuth2 flow. This is useful in real-world scenarios that require token customization or additional validation. Once the token is modified, the changes are stored as transactional data and persist throughout the token’s lifecycle. These modifications are reflected in subsequent flows, such as the refresh token flow, and are available to @@ -33,7 +33,7 @@ enhancing security posture and minimizing unauthorized access. ## Request and Response Handling -When an access token request is made, Asgardeo or WSO2 Identity Server (WSO2 IS) will send a request to your configured +When an access token request is made, WSO2 Identity Platform or WSO2 Identity Server (WSO2 IS) will send a request to your configured extension service containing the information of the access token request and the allowed operations. Your service will process this request and respond with an appropriate status: diff --git a/en/includes/complete-guides/actions/pre-update-password-action-in-choreo.md b/en/includes/complete-guides/actions/pre-update-password-action-in-choreo.md index b19f0e3708..3f4be8ed51 100644 --- a/en/includes/complete-guides/actions/pre-update-password-action-in-choreo.md +++ b/en/includes/complete-guides/actions/pre-update-password-action-in-choreo.md @@ -372,7 +372,7 @@ securely.  -The API key will be generated along with an application in Asgardeo. Copy and save the key securely for later use in +The API key will be generated along with an application in WSO2 Identity Platform. Copy and save the key securely for later use in your API calls. ### Test Deployed Service diff --git a/en/includes/complete-guides/actions/pre-update-password-action-use-case.md b/en/includes/complete-guides/actions/pre-update-password-action-use-case.md index 85e99a341f..beee33fdaf 100644 --- a/en/includes/complete-guides/actions/pre-update-password-action-use-case.md +++ b/en/includes/complete-guides/actions/pre-update-password-action-use-case.md @@ -35,7 +35,7 @@ hygiene and strengthening overall account security. ## Request and Response Handling -When a password update request is made, Asgardeo or WSO2 Identity Server (WSO2 IS) will send a request to your +When a password update request is made, WSO2 Identity Platform or WSO2 Identity Server (WSO2 IS) will send a request to your configured extension service containing the updated password information. Your service will process this request and respond with an appropriate status: diff --git a/en/includes/complete-guides/actions/pre-update-profile-action-in-choreo.md b/en/includes/complete-guides/actions/pre-update-profile-action-in-choreo.md index 430342fc58..8ef30e7e44 100644 --- a/en/includes/complete-guides/actions/pre-update-profile-action-in-choreo.md +++ b/en/includes/complete-guides/actions/pre-update-profile-action-in-choreo.md @@ -385,7 +385,7 @@ securely.  -The API key will be generated along with an application in Asgardeo. Copy and save the key securely for later use in +The API key will be generated along with an application in WSO2 Identity Platform. Copy and save the key securely for later use in your API calls. ### Test Deployed Service diff --git a/en/includes/complete-guides/actions/pre-update-profile-action-use-case.md b/en/includes/complete-guides/actions/pre-update-profile-action-use-case.md index 4bf5f5013a..198d07483f 100644 --- a/en/includes/complete-guides/actions/pre-update-profile-action-use-case.md +++ b/en/includes/complete-guides/actions/pre-update-profile-action-use-case.md @@ -25,7 +25,7 @@ improving data integrity and operational security. ## Request and Response Handling -When a profile update request is made, Asgardeo or WSO2 Identity Server (WSO2 IS) will send a request to your configured +When a profile update request is made, WSO2 Identity Platform or WSO2 Identity Server (WSO2 IS) will send a request to your configured extension service containing the updated attribute information. Your service will process this request and respond with an appropriate status: diff --git a/en/includes/complete-guides/angular/accessing-protected-api.md b/en/includes/complete-guides/angular/accessing-protected-api.md index c35ae61fd9..e56e6123a9 100644 --- a/en/includes/complete-guides/angular/accessing-protected-api.md +++ b/en/includes/complete-guides/angular/accessing-protected-api.md @@ -39,7 +39,7 @@ export const appConfig: ApplicationConfig = { You need to construct the '
' value as per the following instructions: - For Asgardeo: + For WSO2 Identity Platform: ` = https://api.asgardeo.io/t/ ` @@ -80,7 +80,7 @@ export class DashboardComponent { You need to construct the ` ` value as per the following instructions: - For Asgardeo: + For WSO2 Identity Platform: ` = https://api.asgardeo.io/t/ ` @@ -125,7 +125,7 @@ export class DashboardComponent { You need to construct the ` ` value as per the following instructions: - For Asgardeo: + For WSO2 Identity Platform: ` = https://api.asgardeo.io/t/ ` diff --git a/en/includes/complete-guides/app-native/add-login-and-logout.md b/en/includes/complete-guides/app-native/add-login-and-logout.md index 749b03e99c..5ecc597965 100644 --- a/en/includes/complete-guides/app-native/add-login-and-logout.md +++ b/en/includes/complete-guides/app-native/add-login-and-logout.md @@ -1,5 +1,5 @@ -Asgardeo SDK provides `SignInButton`, `SignOutButton` components to handle user sign-in and sign-out. You can use these components along side `SignedIn` and `SignedOut` components to conditionally render content based on the user's logged in state. +WSO2 Identity Platform SDK provides `SignInButton`, `SignOutButton` components to handle user sign-in and sign-out. You can use these components along side `SignedIn` and `SignedOut` components to conditionally render content based on the user's logged in state. Replace the existing content of the `app/page.tsx` file with following content. @@ -41,7 +41,7 @@ export default function Home() { This code snippet adds a login button in the application as well as displays user profile and a dropdown when the user is signed in. -However since app native authentication needs to be used, the following can be done to integrate the Asgardeo Next SDK with {{product_name}}. Since you have already enabled app-native authentication in the {{product_name}} side during step 3, you can add the below logic to the application. +However since app native authentication needs to be used, the following can be done to integrate the WSO2 Identity Platform Next SDK with {{product_name}}. Since you have already enabled app-native authentication in the {{product_name}} side during step 3, you can add the below logic to the application. First, create an app route for the sign-in page. Create a new file called `app/sign-in/page.tsx` and add the following code: diff --git a/en/includes/complete-guides/app-native/add-mfa.md b/en/includes/complete-guides/app-native/add-mfa.md index 5084843972..7a37356786 100644 --- a/en/includes/complete-guides/app-native/add-mfa.md +++ b/en/includes/complete-guides/app-native/add-mfa.md @@ -3,9 +3,9 @@ Multi-factor authentication (MFA) is a security mechanism that requires users to In this guide, we will look into enabling Email OTP as an MFA factor in your Next.js application. Email OTP is a simple and effective MFA method that sends a one-time passcode to the user's email address, which they must enter to complete the login process. -{% if product_name == 'Asgardeo' %} +{% if product_name == 'WSO2 Identity Platform' %} -You can configure SMTP settings in the {{product_name}} Console by navigating to the **Notification Channels** tab > **Email Provider** section. In Asgardeo you can simply use default Asgardeo SMTP settings available out of the box without configuring an **Email Provider**. +You can configure SMTP settings in the {{product_name}} Console by navigating to the **Notification Channels** tab > **Email Provider** section. In WSO2 Identity Platform you can simply use default WSO2 Identity Platform SMTP settings available out of the box without configuring an **Email Provider**. {% else %} diff --git a/en/includes/complete-guides/app-native/configure-provider.md b/en/includes/complete-guides/app-native/configure-provider.md index 5adc28e974..88448c07f5 100644 --- a/en/includes/complete-guides/app-native/configure-provider.md +++ b/en/includes/complete-guides/app-native/configure-provider.md @@ -1,6 +1,6 @@ ## Install `@asgardeo/nextjs` -Asgardeo Next.js SDK provides all the components and hooks you need to integrate {{ product_name }} into your app. To get started, simply add the Asgardeo Next.js SDK to the project. Make sure to stop the dev server started in the previous step. +WSO2 Identity Platform Next.js SDK provides all the components and hooks you need to integrate {{ product_name }} into your app. To get started, simply add the WSO2 Identity Platform Next.js SDK to the project. Make sure to stop the dev server started in the previous step. === "npm" @@ -22,7 +22,7 @@ Asgardeo Next.js SDK provides all the components and hooks you need to integrate ## Set up environment variables -Create a `.env` or an appropriate environment configuration file in the root of your Next.js project. This file will store all the configuration values required for the Asgardeo Next.js SDK to function properly. +Create a `.env` or an appropriate environment configuration file in the root of your Next.js project. This file will store all the configuration values required for the WSO2 Identity Platform Next.js SDK to function properly. ```bash title=".env" NEXT_PUBLIC_ASGARDEO_BASE_URL="{{content.sdkconfig.baseUrl}}" @@ -32,7 +32,7 @@ ASGARDEO_CLIENT_SECRET=" " !!! danger "Warning" - There is a Secret used for signing JWT session cookies. If this is not defined, it will use the default one configured in the Asgardeo SDK. However it is mandatory to change this in a production environment. + There is a Secret used for signing JWT session cookies. If this is not defined, it will use the default one configured in the WSO2 Identity Platform SDK. However it is mandatory to change this in a production environment. Please generate a random key with the following. @@ -47,9 +47,9 @@ ASGARDEO_CLIENT_SECRET=" " ## Setup the middleware -Create a file called `middleware.ts` in the root of your Next.js project and integrate the `asgardeoMiddleware` from the Asgardeo Next.js SDK. +Create a file called `middleware.ts` in the root of your Next.js project and integrate the `asgardeoMiddleware` from the WSO2 Identity Platform Next.js SDK. -The `asgardeoMiddleware` helper integrates Asgardeo authentication into your Next.js application and supports both the App and Pages routers. +The `asgardeoMiddleware` helper integrates WSO2 Identity Platform authentication into your Next.js application and supports both the App and Pages routers. ```bash title="middleware.ts" import {asgardeoMiddleware} from '@asgardeo/nextjs/server'; diff --git a/en/includes/complete-guides/app-native/configure-utility-functions.md b/en/includes/complete-guides/app-native/configure-utility-functions.md index a4d8bb5f41..ea16df5629 100644 --- a/en/includes/complete-guides/app-native/configure-utility-functions.md +++ b/en/includes/complete-guides/app-native/configure-utility-functions.md @@ -187,7 +187,7 @@ export const logoutFromAsgardeo = async (idToken: string) => { }); if (!response.ok) { - throw new Error('Failed to log out from Asgardeo'); + throw new Error('Failed to log out from WSO2 Identity Platform'); } } catch (error) { console.error("Logout request failed:", error); diff --git a/en/includes/complete-guides/app-native/introduction.md b/en/includes/complete-guides/app-native/introduction.md index 5e42f9fc28..ebf75d6e69 100644 --- a/en/includes/complete-guides/app-native/introduction.md +++ b/en/includes/complete-guides/app-native/introduction.md @@ -13,7 +13,7 @@ By the end of this guide, you will be able to: - Register an application in {{product_name}} to enable authentication. - Set up a Next.js application with authentication capabilities. -- Install and configure the Asgardeo SDK, enabling seamless authentication. +- Install and configure the WSO2 Identity Platform SDK, enabling seamless authentication. - Implement login and logout functionality to allow users to authenticate within the app using app native authentication. - Retrieve and display user details after a successful login. - Add Multi Factor Authentication with app native authentication diff --git a/en/includes/complete-guides/app-native/manage-tokens-in-apps.md b/en/includes/complete-guides/app-native/manage-tokens-in-apps.md index efbe09ae4c..d07b17d35c 100644 --- a/en/includes/complete-guides/app-native/manage-tokens-in-apps.md +++ b/en/includes/complete-guides/app-native/manage-tokens-in-apps.md @@ -1,9 +1,9 @@ ## Token Validation -A key principle of security tokens is that the receiver must first validate the token. This involves checking the authenticity of the token issuer, ensuring the token meets validity criteria such as expiration time, and confirming that the receiver is authorized to use the token. The Asgardeo SDK handles token validation automatically as part of its authentication and session management process to ensure that users have valid and unexpired tokens when accessing protected resources. +A key principle of security tokens is that the receiver must first validate the token. This involves checking the authenticity of the token issuer, ensuring the token meets validity criteria such as expiration time, and confirming that the receiver is authorized to use the token. The WSO2 Identity Platform SDK handles token validation automatically as part of its authentication and session management process to ensure that users have valid and unexpired tokens when accessing protected resources. -When a user signs in, the Asgardeo SDK acquires an access token (and often an ID token) from {{product_name}}. The access token is by default an opaque token and the ID token is in the form of JSON Web Tokens (JWTs). The SDK automatically validates the token when it is obtained. This involves several checks: +When a user signs in, the WSO2 Identity Platform SDK acquires an access token (and often an ID token) from {{product_name}}. The access token is by default an opaque token and the ID token is in the form of JSON Web Tokens (JWTs). The SDK automatically validates the token when it is obtained. This involves several checks: - **Signature Validation:** The SDK verifies the JWT's signature using the public key retrieved from {{product_name}} JWKS endpoint. This ensures that the token has been issued by a trusted authority and has not been tampered with. @@ -15,11 +15,11 @@ When a user signs in, the Asgardeo SDK acquires an access token (and often an I ## Token Persistence -In the Asgardeo SDK, by default, an in memory token storage is used to store access tokens. +In the WSO2 Identity Platform SDK, by default, an in memory token storage is used to store access tokens. ## Initiate Logout -The Asgardeo SDK provides a simple approach to handle user logout from your app. When a user logs out, the SDK ensures that both the local session and the session on the {{product_name}} are terminated, ensuring a complete and secure logout process and you don’t need to worry on cleanup activities +The WSO2 Identity Platform SDK provides a simple approach to handle user logout from your app. When a user logs out, the SDK ensures that both the local session and the session on the {{product_name}} are terminated, ensuring a complete and secure logout process and you don’t need to worry on cleanup activities When a user initiates log out, the following steps typically occur. diff --git a/en/includes/complete-guides/app-native/next-steps.md b/en/includes/complete-guides/app-native/next-steps.md index a0cecfa699..78798cf2b4 100644 --- a/en/includes/complete-guides/app-native/next-steps.md +++ b/en/includes/complete-guides/app-native/next-steps.md @@ -1,5 +1,5 @@ -This guide you just completed covered how to add user authentication to a Next.js application using Next Asgardeo SDK and an Identity Provider (IdP) like **{{product_name}}**. It also explored making authenticated requests to an OAuth2-protected API. +This guide you just completed covered how to add user authentication to a Next.js application using Next WSO2 Identity Platform SDK and an Identity Provider (IdP) like **{{product_name}}**. It also explored making authenticated requests to an OAuth2-protected API. --- diff --git a/en/includes/complete-guides/dotnet/configure-authentication-properties.md b/en/includes/complete-guides/dotnet/configure-authentication-properties.md index be3f22003b..2db997538d 100644 --- a/en/includes/complete-guides/dotnet/configure-authentication-properties.md +++ b/en/includes/complete-guides/dotnet/configure-authentication-properties.md @@ -42,7 +42,7 @@ An example configuration is shown below (placeholders have to be replaced with t ## Add authentication package -As the next step we have to add `Microsoft.AspNetCore.Authentication.OpenIdConnect` package to our application. This package allows your .NET app to authenticate users using an OIDC identity providers such as Asgardeo and WSO2 Identity Server and also manage authentication tokens. +As the next step we have to add `Microsoft.AspNetCore.Authentication.OpenIdConnect` package to our application. This package allows your .NET app to authenticate users using an OIDC identity providers such as WSO2 Identity Platform and WSO2 Identity Server and also manage authentication tokens. When adding `Microsoft.AspNetCore.Authentication.OpenIdConnect` package, make sure to pick the right version as per your .Net SDK installation. diff --git a/en/includes/complete-guides/dotnet/securing-routes-within-the-app.md b/en/includes/complete-guides/dotnet/securing-routes-within-the-app.md index a046d80410..707d1e26ef 100644 --- a/en/includes/complete-guides/dotnet/securing-routes-within-the-app.md +++ b/en/includes/complete-guides/dotnet/securing-routes-within-the-app.md @@ -188,7 +188,7 @@ Clicking on the login button will initiate an OIDC request. {{product_name}} wil !!! tip "Tip" - The OpenID Connect specification offers several functions, known as grant types, to obtain an access token in exchange for user credentials. This example uses the authorization code grant type. In this process, the app first requests a unique code from the authentication server, which can later be used to obtain an access token. For more details on the authorization code grant type, please refer to the [Asgardeo documentation.](https://wso2.com/asgardeo/docs/guides/authentication/oidc/implement-auth-code-with-pkce/){:target="_blank"} + The OpenID Connect specification offers several functions, known as grant types, to obtain an access token in exchange for user credentials. This example uses the authorization code grant type. In this process, the app first requests a unique code from the authentication server, which can later be used to obtain an access token. For more details on the authorization code grant type, please refer to the [WSO2 Identity Platform documentation.](https://wso2.com/asgardeo/docs/guides/authentication/oidc/implement-auth-code-with-pkce/){:target="_blank"} At this stage, you should have already created a test user in {{product_name}}, as outlined in the [prerequisites]({{ base_path }}/complete-guides/dotnet/prerequisites) section. Now can enter the username and password of the test user to the login screen. diff --git a/en/includes/complete-guides/expressjs/add-login-and-logout.md b/en/includes/complete-guides/expressjs/add-login-and-logout.md index a8f359580f..356423d77d 100644 --- a/en/includes/complete-guides/expressjs/add-login-and-logout.md +++ b/en/includes/complete-guides/expressjs/add-login-and-logout.md @@ -226,7 +226,7 @@ Start the server: npm start ``` -Open `http://localhost:3000` and click the "Login with Asgardeo" button. You will be redirected to the {{product_name}} login page. Enter the user credentials and click "Sign In". You will be redirected back to the index page. +Open `http://localhost:3000` and click the "Login with WSO2 Identity Platform" button. You will be redirected to the {{product_name}} login page. Enter the user credentials and click "Sign In". You will be redirected back to the index page. {: width="800" style="display: block; margin: 0;"} diff --git a/en/includes/complete-guides/expressjs/display-logged-in-user-details.md b/en/includes/complete-guides/expressjs/display-logged-in-user-details.md index 13cc18a8f7..8ef270f305 100644 --- a/en/includes/complete-guides/expressjs/display-logged-in-user-details.md +++ b/en/includes/complete-guides/expressjs/display-logged-in-user-details.md @@ -1,7 +1,7 @@ -At this point, we’ve successfully implemented login and logout capabilities using the Passport Asgardeo strategy. The next step is to explore how to access and display logged-in user details within the app. +At this point, we’ve successfully implemented login and logout capabilities using the Passport WSO2 Identity Platform strategy. The next step is to explore how to access and display logged-in user details within the app. -If you observe the `routes/auth.js` file, you can see that the Asgardeo strategy loads the basic user attribute details in the id token, and these attributes are accessible through the `uiProfile` object in the `verify` callback. +If you observe the `routes/auth.js` file, you can see that the WSO2 Identity Platform strategy loads the basic user attribute details in the id token, and these attributes are accessible through the `uiProfile` object in the `verify` callback. ```javascript function verify( @@ -95,7 +95,7 @@ Now, let's modify the `views/index.ejs` file to display the user details.