Fix: #AR-5919 review fixes

Author: shaloo

an_dictionary.txt

@@ -200,6 +200,7 @@ HDWallet
 HTML
 Hashicorp
 HighwayHash
+IAM
 IBFT
 ID1
 IPFS
@@ -256,6 +257,7 @@ OAuth2
 OTP
 Okta
 Onboarding
+OpenID
 OpenSea
 OtpLoginResponse
 P1
@@ -271,13 +273,15 @@ Polyfill
 Polygon_Mainnet
 Polygon_Mumbai_Testnet
 Pre
+Pre-configured
 Programmatically
 ProviderEngine
 PublicKeyOutput
 PvtBetaGHBranchText
 Pwdless
 PwdlessAuthConfigText
 QoS
+README
 RFP
 RHS
 RPC
@@ -426,6 +430,7 @@ Vn
 Vue
 Vue-CLI
 Wagmi
+WagmiConfig
 WalletConfigWarningText
 WalletConnect
 WalletConnectProvider
@@ -594,6 +599,7 @@ faq_nftviewer
 faq_storage
 faq_validator
 fb
+fedidmauth
 fontawesome-brands-aws
 fontawesome-brands-discord
 fontawesome-brands-github
@@ -723,6 +729,7 @@ idfaqgen
 idfaqnftviewer
 idfaqstorage
 idfaqvalidator
+idfedidmauth
 idgeneratedelegatekey
 idgithuboauth
 idgoogleoauth

docs/concepts/anwallet/walletuimodes.md

@@ -33,7 +33,7 @@ Once the user takes action, the request disappears and the user cannot access th
 
 ## Summary
 
-The table below summarizes how `alwaysVisible` parameter specified during Auth SDK initialization in the application code controls the user experience. For step-by-step instructions see [how to configure Arcana wallet visibility mode]({{page.meta.arcana.root_rel_path}}/howto/arcana_wallet/config_wallet_modes.md) guide.
+The table below summarizes how `alwaysVisible` parameter specified during Auth SDK initialization in the application code controls the user experience. For step-by-step instructions see [how to configure Arcana wallet visibility mode]({{page.meta.arcana.root_rel_path}}/howto/arcana_wallet/config_walletvisibility.md) guide.
 
 | Wallet UI Mode | Flag | User Experience|
 | :------ | :----- | :----------- |

docs/concepts/authtype/arcanaauth.md

@@ -10,19 +10,22 @@ arcana:
 
 # Authentication
 
-Authentication in the Web3 ecosystem is more complex than in traditional Web2 applications. Users must have a private key to interact with blockchain and cryptographic systems. This can be cumbersome for users, as generating and managing private keys can be difficult and there is no central authority for recovery if a key is lost. Web3 wallets can make this process easier, but they are a new concept for many Web2 users and managing secrets for the wallet can be an additional burden. This can make it difficult for new users to onboard Web3 applications and the onboarding experience is different from that of Web2 applications.
+Authentication in the Web3 ecosystem is more complex than in traditional Web2 applications. Users must have a private key to interact with the blockchain networks and cryptographic systems. This can be cumbersome for users, as generating and managing private keys can be difficult and there is no central authority for recovery if a key is lost. Web3 wallets can make this process easier, but they are a new concept for many Web2 users and managing secrets for the wallet can be an additional burden. This can make it difficult for new users to onboard Web3 applications and the onboarding experience is different from that of Web2 applications.
 
-**Arcana's [Auth SDK]({{page.meta.arcana.root_rel_path}}/concepts/authsdk.md) significantly reduces the barriers to user authentication and simplifies the process of signing blockchain transactions by eliminating the need for key management.** 
+**The [{{config.extra.arcana.sdk_name}}]({{page.meta.arcana.root_rel_path}}/concepts/authsdk.md) significantly reduces the barriers to Web3 user onboarding and enables authenticated app users to easily sign blockchain transactions by eliminating the need for complex key management without sacrificing security and privacy.** 
 
 ## Authentication Mechanisms
 
-Web3 application developers can [plug in default UI]({{page.meta.arcana.root_rel_path}}/concepts/plugnplayauth.md) for user login or build their own UI and call Auth SDK functions to enable one or more authentication mechanisms:
+Web3 app developers can use {{config.extra.arcana.sdk_name}} [plug-and-play login UI]({{page.meta.arcana.root_rel_path}}/concepts/plugnplayauth.md) to add user onboarding code in the app. Or they can also build a custom UI for user login and call the {{config.extra.arcana.sdk_name}} user onboarding functions to enable user authentication.
 
-* [Social authentication]({{page.meta.arcana.root_rel_path}}/concepts/authtype/socialauth.md)
-* [Passwordless authentication]({{page.meta.arcana.root_rel_path}}/concepts/authtype/pwdless.md)
+The {{config.extra.arcana.sdk_name}} allows developers to configure multiple user authentication providers and onboard users. The following authentication mechanisms are supported:
 
-!!! note
+* [Passwordless Login]({{page.meta.arcana.root_rel_path}}/concepts/authtype/pwdless.md)
+* [Social Providers]({{page.meta.arcana.root_rel_path}}/concepts/authtype/socialauth.md)
+* [Custom IAM Providers]({{page.meta.arcana.root_rel_path}}/concepts/authtype/customauth.md)
 
-      Arcana's [Auth SDK]({{page.meta.arcana.root_rel_path}}/concepts/authsdk.md) allows developers to enable authenticated users to sign blockchain transactions. 
+!!! note "Associating Web3 Keys with Authenticated Users"
+
+    The {{config.extra.arcana.sdk_name}} allows developers to plug in user onboarding in the Web3 apps and enable authenticated users to sign blockchain transactions. 
       
-      It includes the [Arcana wallet]({{page.meta.arcana.root_rel_path}}/concepts/anwallet/index.md), which provides a standard Ethereum provider interface for securely enabling blockchain transactions. Arcana's `AuthProvider` encapsulates a decentralized key generated by Arcana's asynchronous, distributed key generation ([DKG]({{page.meta.arcana.root_rel_path}}/concepts/dkg/index.md)) protocol. After users are authenticated through social or passwordless login mechanisms, developers can use the provider to enable them to securely sign blockchain transactions.
+      The [{{config.extra.arcana.wallet_name}}]({{page.meta.arcana.root_rel_path}}/concepts/anwallet/index.md), is part of the {{config.extra.arcana.sdk_name}} and available to all authenticated users. It is a non-custodial wallet that provides a standard Ethereum provider interface for securely enabling blockchain transactions. The `{{config.extra.arcana.auth_sdk_pkg_name}}` provides `AuthProvider` that abstracts decentralized keys generated by the asynchronous, distributed key generation ([ADKG]({{page.meta.arcana.root_rel_path}}/concepts/dkg/index.md)) protocol in the Arcana Network.

docs/concepts/authtype/customauth.md

@@ -0,0 +1,15 @@
+---
+slug: /fedidmauth
+id: idfedidmauth
+title: Custom IAM Providers
+sidebar_custom_props:
+  cardIcon: ▶️
+arcana:
+  root_rel_path: ../..
+---
+
+# Custom IAM Providers
+
+Custom IAM providers allow various user authentication mechanisms including authentication via social providers and authentication standards such as OpenID. The {{config.extra.arcana.sdk_name}} supports the following Custom IAM providers for user authentication:
+
+{% include "./text-snippets/custom_idm_supported.md" %}

docs/concepts/authtype/index.md

@@ -1,7 +1,20 @@
+---
+arcana:
+  root_rel_path: ../..
+---
+
 # Authentication Types
 
-The Arcana Auth SDK supports the following authentication types:
+The {{config.extra.arcana.sdk_name}} supports the following authentication providers:
+
+[Social Providers :fontawesome-solid-users-gear:](./socialauth.md){ .md-button }
+
+[Custom IAM Providers :fontawesome-solid-users-gear:](./customauth.md){ .md-button }
+
+[Passwordless Login :material-card-account-mail:](./pwdless.md){ .md-button }
+
+!!! info  "Aggregate Logins"
 
-[Social Authentication :fontawesome-solid-users-gear:](./socialauth.md){ .md-button }
+    The {{config.extra.arcana.sdk_name}} supports [aggregate login]({{page.meta.arcana.root_rel_path}}/concepts/authtype/aggregatelogin.md) feature. With aggregate login, application users can be identified even if they use multiple authentication mechanisms to onboard an app. An authenticated user is identified and associated with the same key shares and does not have to juggle multiple wallet addresses. Aggregate login ensures there are no duplicate user identities or {{config.extra.arcana.wallet_name}} addresses assigned to the same user.  
 
-[Passwordless Login :material-card-account-mail:](./pwdless.md){ .md-button }
+    The aggregate login feature works **only if** the user specifies the **same** email ID to register with different authentication providers or via the passwordless login option.

docs/concepts/authtype/pwdless.md

@@ -1,20 +1,18 @@
 ---
 slug: /pwdless
 id: idpwdless
-title: passwordless Login
+title: Passwordless Login
 sidebar_custom_props:
   cardIcon: ▶️
+arcana:
+  root_rel_path: ../..
 ---
 
-# Passwordless Authentication
+# Passwordless Login
 
 <img src="/img/icons/i_an_pwdless_light.png#only-light" width="50"/>
 <img src="/img/icons/i_an_pwdless_dark.png#only-dark" width="50"/>
 
-With Arcana Auth, users can easily onboard any Web3 application with passwordless authentication simply by providing an email ID. 
+With the {{config.extra.arcana.sdk_name}}, users can easily onboard any Web3 app in a passwordless manner by simply providing an email ID. 
 
-Application users receive an email verification link or a time-sensitive OTP that can be used to log in to the application. This passwordless approach eliminates the need to remember passwords or share social account identifiers with the application provider, making the onboarding process completely friction-free. 
-
-!!! note
-
-      After passwordless authentication, developers can enable users access the embedded Web3 Arcana wallet included with the Auth SDK to sign blockchain transactions.
+App users receive an email verification link or a time-sensitive OTP that can be used to log in to the application. This passwordless approach eliminates the need to remember passwords or share social account identifiers to onboard an app, making the onboarding process completely frictionless. 

docs/concepts/authtype/socialauth.md

@@ -1,30 +1,24 @@
 ---
 slug: /socialauth
 id: idsocialauth
-title: Social Authentication
+title: Social Providers
 sidebar_custom_props:
   cardIcon: ▶️
 arcana:
   root_rel_path: ../..
 ---
 
-# Social Authentication
+# Social Providers
 
 <img src="/img/icons/i_an_socialauth_light.png#only-light" width="50"/>
 <img src="/img/icons/i_an_socialauth_dark.png#only-dark" width="50"/>
 
-Social authentication allows applications to onboard users and validate their identity through popular Web2 authentication provider. Arcana Auth SDK supports social authentication in Web3 applications for the following providers:
+Social providers are popular Web2 identity providers that allow apps to onboard users and validate the user identity. The {{config.extra.arcana.sdk_name}} supports user authentication in Web3 applications via the following social providers:
 
 {% include "./text-snippets/auth_supported.md" %}
 
-In Web2 applications, social authentication is typically triggered by a pop-up or redirect to a provider chosen by the user. This is a familiar and easy way for users to onboard new applications without managing multiple identities. However, a centralized system with a few organizations controls user authentication. 
+In Web2 applications, user authentication is typically triggered by a pop-up or via a redirect to a selected provider's web page. This is a familiar and comfortable way for users to onboard a new application without bothering to manage multiple identities. However, this is a centralized authentication system controlled by the social provider. 
 
-In the Web3 ecosystem, decentralized systems of actors use trustless protocols and cryptography to verify user identity in a decentralized manner. These systems use encrypted, sharded keys that are not stored with any single entity, but users must manage their own secret keys, which can be a barrier to entry for Web3 applications. 
+In the Web3 ecosystem, distributed systems of actors use trustless protocols and cryptography to verify user identity in a decentralized manner. These systems use encrypted, key shares that are not stored with any single entity, but users are required to generate, manage and secure their secret keys. This complexity is a big barrier to entry into the Web3 app ecosystem. 
 
-Auth SDK lowers this barrier by providing a convenient and secure way for users to onboard Web3 applications in a decentralized manner.
-
-!!! info  "Aggregate Logins"
-
-    Arcana supports the [aggregate login]({{page.meta.arcana.root_rel_path}}/concepts/authtype/aggregatelogin.md) feature that can identify application users even if they use different authentication mechanisms to log in. Aggregate login ensures there are no duplicate user identities or Arcana Web3 wallet addresses assigned to the same user.  
-
-    Aggregate login feature works **only if** the user specifies the **same** email ID to register with different social authentication providers and passwordless login.
+The {{config.extra.arcana.sdk_name}} lowers this barrier to entry into the Web3 app ecosystem by providing a convenient yet fully secure and privacy-preserving way for users to onboard Web3 apps and sign blockchain transactions.