Skip to content

Commit

Permalink
Update common instructions
Browse files Browse the repository at this point in the history
  • Loading branch information
ThaminduDilshan committed Nov 20, 2024
1 parent a11b188 commit 1c16e7e
Show file tree
Hide file tree
Showing 3 changed files with 5 additions and 1 deletion.
4 changes: 3 additions & 1 deletion user-migration-samples/README.md
Original file line number Diff line number Diff line change
@@ -1,11 +1,13 @@
# User Migration Samples

This directory contains samples for migrating users from one identity provider to WSO2 Identity Server or Asgardeo.
This directory contains samples for migrating users from an existing identity provider to WSO2 Identity Server or Asgardeo.

## Directory tree of Samples

```
SAMPLES_HOME
├── is
└── external-authentication-service
├── asgardeo
└── external-authentication-service
```
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,7 @@ This sample demonstrates how to implement an external authentication service in

> [!NOTE]
> - This guide provides a sample authentication service which satisfies only the basic functional requirement.
> - In this example, authentication results are stored in an in-memory map and hence supports only single-replica deployments. This is not recommended for production use. You need to replace this with a high available implementation that suits your requirement (i.e. DB or cache service).
> [!WARNING]
> - We recommend adding necessary logs for audit purposes when developing the REST service. However be cautious on the information you log, especially DO NOT log any sensitive information including PII.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,7 @@ This sample demonstrates how to implement an external authentication service in

> [!NOTE]
> - This guide provides a sample authentication service which satisfies only the basic functional requirement.
> - In this example, authentication results are stored in an in-memory map and hence supports only single-replica deployments. This is not recommended for production use. You need to replace this with a high available implementation that suits your requirement (i.e. DB or cache service).
> [!WARNING]
> - We recommend adding necessary logs for audit purposes when developing the REST service. However be cautious on the information you log, especially DO NOT log any sensitive information including PII.
Expand Down

0 comments on commit 1c16e7e

Please sign in to comment.