TIcket #901 : Update the documentation

Author: habarthierry-hue

website/docs/scim/persistence/entityframework.md

@@ -130,4 +130,54 @@ app.UseScim();
 app.Run();
 ```
 
-This setup shows how to accommodate SQLite’s limitations while still benefitting from Entity Framework’s powerful migration and connection capabilities.
+This setup shows how to accommodate SQLite’s limitations while still benefitting from Entity Framework’s powerful migration and connection capabilities.
+
+## Running the EF Migration
+
+Once your SCIM server is configured and ready to use a database, you can trigger the EF Core migration by calling the `EnsureEfStoreMigrated` function in your `Program.cs` file.
+
+```csharp title="Program.cs"
+var app = builder.Build();
+app.Services.EnsureEfStoreMigrated(new List<SCIMSchema>(), new List<SCIMAttributeMapping>(), new List<Realm>());;
+```
+
+This function takes three input parameters:
+
+1. **List of SCIM Schemas** : You can use the `SCIMSchemaExtractor` class to extract SCIM schemas from a JSON file. For example:
+
+```
+var userSchema = SimpleIdServer.Scim.SCIMSchemaExtractor.Extract(Path.Combine(basePath, "UserSchema.json"), SCIMResourceTypes.User, true);
+```
+
+2. **List of attribute mappings** : These mappings define parent-child relationships between two types of representations—for example, between a `Group` and a `User`.
+
+The code snippet below sets up the relationship from a `Group` to a `User`, where the `members` property of a `group` contains a list of `users`:
+
+```csharp
+new SCIMAttributeMapping
+{
+    Id = Guid.NewGuid().ToString(),
+    SourceAttributeId = groupSchema.Attributes.First(a => a.Name == "members").Id,
+    SourceResourceType = StandardSchemas.GroupSchema.ResourceType,
+    SourceAttributeSelector = "members",
+    TargetResourceType = StandardSchemas.UserSchema.ResourceType,
+    TargetAttributeId = userSchema.Attributes.First(a => a.Name == "groups").Id,
+    Mode = Mode.PROPAGATE_INHERITANCE
+}
+```
+
+The following code snippet sets up the inverse relationship from a `User` to a `Group`, where the `groups` property of a `user` contains a list of `groups` :
+
+```
+new SCIMAttributeMapping
+{
+    Id = Guid.NewGuid().ToString(),
+    SourceAttributeId = userSchema.Attributes.First(a => a.Name == "groups").Id,
+    SourceResourceType = StandardSchemas.UserSchema.ResourceType,
+    SourceAttributeSelector = "groups",
+    TargetResourceType = StandardSchemas.GroupSchema.ResourceType,
+    TargetAttributeId = groupSchema.Attributes.First(a => a.Name == "members").Id
+}
+```
+
+3. **List of realms** : The third parameter defines the list of realms to be created. For more information, refer to the dedicated section on realms.

website/docs/scim/persistence/mongodb.md

@@ -43,4 +43,54 @@ Several properties can be customized during the configuration process. Understan
 | CollectionRealms | Used for storing realms if your SCIM server segregates data based on different domains or contexts. |
 | SupportTransaction | Boolean flag indicating if your MongoDB deployment supports transactions. When set to true, the application can take advantage of atomic operations, which are essential in environments requiring strong consistency. |
 
-For more detailed reference, you can check out the example project available on GitHub: [SimpleIdServer Sample](https://github.com/simpleidserver/SimpleIdServer/tree/master/samples/ScimMongodb).
+For more detailed reference, you can check out the example project available on GitHub: [SimpleIdServer Sample](https://github.com/simpleidserver/SimpleIdServer/tree/master/samples/ScimMongodb).
+
+## Creating MongoDB Collections
+
+Once your SCIM server is configured and ready to use MongoDB, you can create the necessary collections by calling the `EnsureMongoStoreDataMigrated` function in your `Program.cs` file.
+
+```csharp title="Program.cs"
+var app = builder.Build();
+app.Services.EnsureMongoStoreDataMigrated(new List<SCIMSchema>(), new List<SCIMAttributeMapping>(), new List<Realm>());;
+```
+
+This function takes three input parameters:
+
+1. **List of SCIM Schemas** : You can use the `SCIMSchemaExtractor` class to extract a SCIM schema from a JSON file. For example:
+
+```
+var userSchema = SimpleIdServer.Scim.SCIMSchemaExtractor.Extract(Path.Combine(basePath, "UserSchema.json"), SCIMResourceTypes.User, true);
+```
+
+2. **List of attribute mappings** : These mappings define parent-child relationships between different representation types. For instance, between a `Group` and a `User`.
+
+The following code snippet defines the relationship from a `Group` to a `User`. The `members` property of a `group` contains a list of `users`:
+
+```csharp
+new SCIMAttributeMapping
+{
+    Id = Guid.NewGuid().ToString(),
+    SourceAttributeId = groupSchema.Attributes.First(a => a.Name == "members").Id,
+    SourceResourceType = StandardSchemas.GroupSchema.ResourceType,
+    SourceAttributeSelector = "members",
+    TargetResourceType = StandardSchemas.UserSchema.ResourceType,
+    TargetAttributeId = userSchema.Attributes.First(a => a.Name == "groups").Id,
+    Mode = Mode.PROPAGATE_INHERITANCE
+}
+```
+
+The next snippet defines the reverse relationship, from a `User` to a `Group`. The `groups` property of a `user` contains a list of `groups`:
+
+```
+new SCIMAttributeMapping
+{
+    Id = Guid.NewGuid().ToString(),
+    SourceAttributeId = userSchema.Attributes.First(a => a.Name == "groups").Id,
+    SourceResourceType = StandardSchemas.UserSchema.ResourceType,
+    SourceAttributeSelector = "groups",
+    TargetResourceType = StandardSchemas.GroupSchema.ResourceType,
+    TargetAttributeId = groupSchema.Attributes.First(a => a.Name == "members").Id
+}
+```
+
+3. **List of realms** : The third parameter specifies the list of realms to initialize. For more details, refer to the dedicated chapter on realms.