The AEM V2 connector supports the following:
* Full crawling and recrawling of pages and assets in Adobe Experience Manager
* Basic authentication
4. Go to AEM to log in and access CRXDE Lite. In the CRXDE Lite UI, select a path to crawl. Enter this path into Fusion. Click ***Add*** to crawl multiple paths.
5. Optional: To exclude paths from the crawl, in Fusion, enter a Java Regular Expression (regex) that represents paths to exclude in the indexed content.
6. In Fusion, enter the AEM type to crawl. In the CRXDE Lite UI, this is the `jcr:primaryType`. In this example, the AEM connector is configured to crawl the AEM Type `cq:Page`, which represents web content pages.
7. To index assets with a particular file extension, locate a file type in CRXDE Lite and enter the value of the `jcr:primaryType` into Fusion. In this example, the value of NY\_FairHealth.pdf is `dam:Asset`.
8. You can choose which content properties to include and exclude from the index. These parameter values are represented by Java regex. For example, to only include properties that start with “jcr” enter `jcr:(.*)`.
9. In Fusion, click ***Save*** when you’re done configuring the AEM datasource.
### Configuration settings
| Setting | Notes |
| -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| AEM URL | Required. This is the URL used to access the AEM Admin UI. |
| AEM Username | Required. The user should have sufficient permissions to read content paths and access Users/Group APIs in case Security Trimming is needed. |
| AEM Password | Required. |
| Page Batch Size | Number of documents to fetch per page request. A higher value can increase crawling speed but also increases memory usage. |
| Thread wait (ms) | Number of milliseconds to wait between fetch requests. This property can be used to throttle a crawl if necessary. |
| Paths to search | Required. |
| Paths that should not be fetched | Java regex for paths that should not be fetched. |
| AEM Types | Required. AEM document type `jcr:primaryType` to include in the index. Examples: `cq:Page`, `dam:Asset`. |
| Attachment types | File extensions to index. |
| Content Property Include Regexes | A list of regex strings of content properties to include in indexed documents. Example: `jcr:.*`. |
| Content Property Exlude Regexes | A list of regex strings of content properties to exclude from indexed documents. Example: `sling:.*` |
| Enable Security Trimming | Enable this setting for content filtering of results based on the user’s id passed in during query. |
| Group Mappings | AEM user groups mapped to indexed values in the security trimming field which are used to filter content based on user id passed in query. |
| Cache Expire Time (m) | Specifies how long a query is cached in minutes. |
## Field data population
There are multiple sources where AEM data is indexed. The `/bin/querybuilder.json` endpoint data is mandatory and must exist in order for a document to be indexed.
Note the list of fields that can appear in an indexed document:
| Field | Source | Comments |
| --------------- | -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| `id` | `
Other settings: `Client Id`, `Client Secret`, and `Redirect Uri` can be found in the AEM admin page under **Security > Oauth Clients**:
## Getting Access Token
1. Open this URL in a browser:
```html theme={"dark"}
http://HOST:PORT/oauth/authorize?response_type=code&client_id=placeholderClientId&client_secret=CLIENT_SECRET&username=admin&password=PASSWORD&scope=offline_access&redirect_uri=REDIRECT_URI
```
2. You are redirected to login page (if you are not logged in):
3. Logging in redirects you to confirm the authorization. Click **Yes, I authorize this request**.
4. You are redirected to the URL provided in `redirect_uri` with parameter `code`: `REDIRECT_URI?code=AUTHORIZATION_CODE`.
5. Copy the value of the `code` parameter. This is your Authorization Code.
6. Execute the request to get Access Token:
```bash theme={"dark"}
curl --location --request POST 'http://HOST:PORT/oauth/token?code=AUTHORIZATION_CODE&client_id=CLIENT_ID&client_secret=CLIENT_SECRET&grant_type=authorization_code&redirect_uri=REDIRECT_URI' --header 'Content-Type: application/x-www-form-urlencoded' --header 'Accept: application/json'
```
Example:
```bash theme={"dark"}
curl --location --request POST 'http://34.71.168.50:4502/oauth/token?code=AUTHORIZATION_CODE&client_id=CLIENT_ID&client_secret=CLIENT_SECRET&grant_type=authorization_code&redirect_uri=http://localhost:8080/test' --header 'Content-Type: application/x-www-form-urlencoded' --header 'Accept: application/json'
```
Response:
```bash theme={"dark"}
"access_token":"{placeholderAccessToken}","refresh_token":"{placeholderRefreshToken}","expires_in":3600
```
## Getting Refresh Token
To get Refresh Token, follow the same proccess for Access Token, but:
1. You must include `offline_access` in the scope list.
2. You must revoke all the previously obtained token. It can be done by clicking **Revoke All Tokens**.
## Getting JWT Bearer Token
1. **Download Private Key** from the AEM Oauth client section. You should have downloaded file **store.p12**.
2. Run:
```bash theme={"dark"}
openssl pkcs12 -in store.p12 -out store.crt.pem -clcerts -nokeys
```
When asked about password type `notasecret`. You should have generated file named **store.crt.pem**.
3. Run:
```bash theme={"dark"}
openssl pkcs12 -in store.p12 -passin pass:notasecret -nocerts -nodes -out store.private.key.txt
```
You should have generated file named **store.private.key.txt**.
4. Create JWT token with the below payload and encrypt it with the private key using RS256:
```json theme={"dark"}
{
"aud": "http://HOST:PORT/oauth/token",
"iss": "CLIENT_ID",
"sub": "USERNAME",
"exp":