Skip to content

Remove mentions to real credentials #5132

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 3, 2025
Merged

Remove mentions to real credentials #5132

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
af89f2e
Remove mentions to real credentials
yleiferman Mar 3, 2025
8595ec9
Update docs/send-data/hosted-collectors/cloud-to-cloud-integration-fr…
kimsauce Mar 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions ...hosted-collectors/cloud-to-cloud-integration-framework/cyberark-audit-source.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,9 +54,9 @@ To configure a CyberArk Audit source, follow the steps below:
1. (Optional) **Fields**. Click the **+Add** button to define the fields you want to associate. Each field needs a name (key) and value.
* ![green check circle.png](/img/reuse/green-check-circle.png) A green circle with a check mark is shown when the field exists in the Fields table schema.
* ![orange exclamation point.png](/img/reuse/orange-exclamation-point.png) An orange triangle with an exclamation point is shown when the field doesn't exist in the Fields table schema. In this case, an option to automatically add the nonexistent fields to the Fields table schema is provided. If a field is sent to Sumo Logic that does not exist in the Fields schema is ignored, known as dropped.
1. **Identity ID**. Enter your identity ID collected from the [Vendor configuration](#vendor-configuration) section. For example, `abr4338`.
1. **Identity ID**. Enter your identity ID collected from the [Vendor configuration](#vendor-configuration) section. For example, `ac212`.
1. **Web Application ID**. Enter your application ID collected from the [Vendor configuration](#vendor-configuration) section. For example, `sumologic`.
1. **Username**. Enter your username(client-id) collected from the [Vendor configuration](#vendor-configuration) section. For example, `c2c@cyberark.cloud.30488`.
1. **Username**. Enter your username(client-id) collected from the [Vendor configuration](#vendor-configuration) section. For example, `user@cyberark.cloud.1234`.
1. **Password**. Enter your password(client-secret) collected from the [Vendor configuration](#vendor-configuration) section.
1. **Tenant URL**. Enter your tenant URL collected from the [Vendor configuration](#vendor-configuration) section. For example, `https://sumologic.audit.cyberark.cloud`.
1. **API Key**. Enter your API key collected from the [Vendor configuration](#vendor-configuration) section.
Expand Down Expand Up @@ -85,9 +85,9 @@ Sources can be configured using UTF-8 encoded JSON files with the Collector Ma
| description | String | No | `null` | Type a description of the source. | `"Testing source"` |
| category | String | No | `null` | Type a category of the source. This value is assigned to the [metadata](/docs/search/get-started-with-search/search-basics/built-in-metadata) field `_sourceCategory`. See [best practices](/docs/send-data/best-practices) for details. | `"mySource/test"` |
| fields | JSON Object | No | `null` | JSON map of key-value fields (metadata) to apply to the collector or source. Use the boolean field `_siemForward` to enable forwarding to SIEM.| `{"_siemForward": false, "fieldA": "valueA"}` |
| identityId | String | Yes | `null` | Identity ID for your CyberArk account. | `abr4338` |
| identityId | String | Yes | `null` | Identity ID for your CyberArk account. | `ac212` |
| appId | String | Yes | `null` | App ID for your CyberArk account. | `sumologic` |
| username | String | Yes | `null` | Username(Client ID) for your configured server. | `c2c@cyberark.cloud.30488` |
| username | String | Yes | `null` | Username(Client ID) for your configured server. | `myuser@cyberark.cloud.1234` |
| password | String | Yes | `null` | Password for your configured server. | |
| tenantURL | String | Yes | `null` | Tenant URL for your configured server. | `https://sumologic.audit.cyberark.cloud` |
| apiKey | String | Yes | `null` | API key for your configured server. | |
Expand Down
8 changes: 4 additions & 4 deletions static/files/c2c/cyberark-audit/example.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,12 +3,12 @@
"source": {
"config": {
"name": "CyberArkAudit",
"identityId": "abr43969",
"identityId": "ac212",
"appId": "sumologic",
"username": "c2c@cyberark.cloud.43969",
"password": "rECxxxx__4_xxxx_G4n6",
"username": "user@cyberark.cloud.1234",
"password": "******",
"tenantURL": "https://sumologic.audit.cyberark.cloud",
"apiKey": "JxxxxxxS9gFJv96LcKcxxxxxxxxxxxxxYqP09OGxxxY",
"apiKey": "*******",
"serviceType": [],
"statusType": [],
"actionType": [],
Expand Down
8 changes: 4 additions & 4 deletions static/files/c2c/cyberark-audit/example.tf
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,12 +5,12 @@ resource "sumologic_cloud_to_cloud_source" "cyberark_audit_test_source" {
}
config = jsonencode({
"name": "CyberArkAudit",
"identityId": "abr43969",
"identityId": "ac212",
"appId": "sumologic",
"username": "c2c@cyberark.cloud.43969",
"password": "rECxxxx__4_xxxx_G4n6",
"username": "user@cyberark.cloud.1234",
"password": "******",
"tenantURL": "https://sumologic.audit.cyberark.cloud",
"apiKey": "JxxxxxxS9gFJv96LcKcxxxxxxxxxxxxxYqP09OGxxxY",
"apiKey": "*******",
"serviceType": [],
"statusType": [],
"actionType": [],
Expand Down