Merge pull request #384 from kinde-oss/Fix/remove-note-about-EC-via-API

Fix/remove note about ec via api

Author: clairekinde11

src/content/docs/authenticate/enterprise-connections/provision-users-enterprise.mdx

@@ -49,7 +49,9 @@ It’s possible that you manage users who can sign in via multiple enterprise co
 
 This method of provisioning requires you to add the enterprise connection as part of the user’s identity in Kinde.
 
-**Add the enterprise connection identity via API (coming soon)**
+**Add the enterprise connection identity via API**
+
+Post identity details to this endpoint `POST /api/v1/users/{user_id}/identities` with `enterprise` as the type and the `connection_id`. For more information, see [Create identity](https://docs.kinde.com/kinde-apis/management/#tag/users/post/api/v1/users/{user_id}/identities).
 
 **Add the enterprise connection identity manually**
 
@@ -76,3 +78,11 @@ When the user signs in with an SSO connection that provides an email that matche
 **We can’t find your account**
 
 If a user goes to sign in and encounters the ’We can’t find your account’ message, it could be because **Self-joining** for the organization is switched off. This is the right behaviour if you don’t want users without the `org_id` to join the org, but the message is confusing. Switch this on via  **Organization > Policies**.
+
+**Duplicate identities**
+
+If duplicate identities are created for users in Kinde, it may because the **Trust email addresses provided by this connection** option is not switched on in the connection configuration.
+
+**Customer's SSO auth not working**
+
+Some B2B businesses allow their customers to sign in using their own enterprise SSO. When setting this up, a common mistake is that they supply incorrect values for the Client ID and Client Secret, based on the identity provider information. Double check these if you come across connection issues.