Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-04-23 14:37:17 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 117
fleet/server/service/testdata/profiles/windows-user-scep.xml

140 lines
4 KiB
XML
Raw Normal View History

DCSW: Add integration test for Windows SCEP profile (#35428) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #34708 A followup task to create an integration test, that uploads a profile with CA variables, and verifies it, + makes a final request to the SCEP server. Also cought the should instantly verified from MDM response, so added it here.
2025-11-12 19:59:09 +00:00
<Add>
<Item>
<Target>
<LocURI>
DUSW: Allow user-scoped SCEP profiles on Windows (#35672) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #35503 For this one I opted for a simple approach of just duplicating the arrays one for user, and one for device, then with the first loc uri that checks in of either device or user, sets the respective arrays, I thought while this was more LOC's it was easier to look at and maintain compared to regex matches etc, let me know if you think otherwise. # Checklist for submitter If some of the following don't apply, delete the relevant line. - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files) for more information. ## Testing - [x] Added/updated automated tests - [x] QA'd all new/changed functionality manually
2025-11-14 15:44:14 +00:00
./User/Vendor/MSFT/ClientCertificateInstall/SCEP/$FLEET_VAR_SCEP_WINDOWS_CERTIFICATE_ID</LocURI>
DCSW: Add integration test for Windows SCEP profile (#35428) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #34708 A followup task to create an integration test, that uploads a profile with CA variables, and verifies it, + makes a final request to the SCEP server. Also cought the should instantly verified from MDM response, so added it here.
2025-11-12 19:59:09 +00:00
</Target>
<Meta>
<Format xmlns="syncml:metinf">node</Format>
</Meta>
</Item>
</Add>
<Add>
<Item>
<Target>
<LocURI>
DUSW: Allow user-scoped SCEP profiles on Windows (#35672) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #35503 For this one I opted for a simple approach of just duplicating the arrays one for user, and one for device, then with the first loc uri that checks in of either device or user, sets the respective arrays, I thought while this was more LOC's it was easier to look at and maintain compared to regex matches etc, let me know if you think otherwise. # Checklist for submitter If some of the following don't apply, delete the relevant line. - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files) for more information. ## Testing - [x] Added/updated automated tests - [x] QA'd all new/changed functionality manually
2025-11-14 15:44:14 +00:00
./User/Vendor/MSFT/ClientCertificateInstall/SCEP/$FLEET_VAR_SCEP_WINDOWS_CERTIFICATE_ID/Install/RetryCount</LocURI>
DCSW: Add integration test for Windows SCEP profile (#35428) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #34708 A followup task to create an integration test, that uploads a profile with CA variables, and verifies it, + makes a final request to the SCEP server. Also cought the should instantly verified from MDM response, so added it here.
2025-11-12 19:59:09 +00:00
</Target>
<Meta>
<Format xmlns="syncml:metinf">int</Format>
</Meta>
<Data>3</Data>
</Item>
</Add>
<Add>
<Item>
<Target>
<LocURI>
DUSW: Allow user-scoped SCEP profiles on Windows (#35672) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #35503 For this one I opted for a simple approach of just duplicating the arrays one for user, and one for device, then with the first loc uri that checks in of either device or user, sets the respective arrays, I thought while this was more LOC's it was easier to look at and maintain compared to regex matches etc, let me know if you think otherwise. # Checklist for submitter If some of the following don't apply, delete the relevant line. - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files) for more information. ## Testing - [x] Added/updated automated tests - [x] QA'd all new/changed functionality manually
2025-11-14 15:44:14 +00:00
./User/Vendor/MSFT/ClientCertificateInstall/SCEP/$FLEET_VAR_SCEP_WINDOWS_CERTIFICATE_ID/Install/RetryDelay</LocURI>
DCSW: Add integration test for Windows SCEP profile (#35428) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #34708 A followup task to create an integration test, that uploads a profile with CA variables, and verifies it, + makes a final request to the SCEP server. Also cought the should instantly verified from MDM response, so added it here.
2025-11-12 19:59:09 +00:00
</Target>
<Meta>
<Format xmlns="syncml:metinf">int</Format>
</Meta>
<Data>10</Data>
</Item>
</Add>
<Add>
<Item>
<Target>
<LocURI>
DUSW: Allow user-scoped SCEP profiles on Windows (#35672) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #35503 For this one I opted for a simple approach of just duplicating the arrays one for user, and one for device, then with the first loc uri that checks in of either device or user, sets the respective arrays, I thought while this was more LOC's it was easier to look at and maintain compared to regex matches etc, let me know if you think otherwise. # Checklist for submitter If some of the following don't apply, delete the relevant line. - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files) for more information. ## Testing - [x] Added/updated automated tests - [x] QA'd all new/changed functionality manually
2025-11-14 15:44:14 +00:00
./User/Vendor/MSFT/ClientCertificateInstall/SCEP/$FLEET_VAR_SCEP_WINDOWS_CERTIFICATE_ID/Install/KeyUsage</LocURI>
DCSW: Add integration test for Windows SCEP profile (#35428) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #34708 A followup task to create an integration test, that uploads a profile with CA variables, and verifies it, + makes a final request to the SCEP server. Also cought the should instantly verified from MDM response, so added it here.
2025-11-12 19:59:09 +00:00
</Target>
<Meta>
<Format xmlns="syncml:metinf">int</Format>
</Meta>
<Data>160</Data>
</Item>
</Add>
<Add>
<Item>
<Target>
<LocURI>
DUSW: Allow user-scoped SCEP profiles on Windows (#35672) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #35503 For this one I opted for a simple approach of just duplicating the arrays one for user, and one for device, then with the first loc uri that checks in of either device or user, sets the respective arrays, I thought while this was more LOC's it was easier to look at and maintain compared to regex matches etc, let me know if you think otherwise. # Checklist for submitter If some of the following don't apply, delete the relevant line. - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files) for more information. ## Testing - [x] Added/updated automated tests - [x] QA'd all new/changed functionality manually
2025-11-14 15:44:14 +00:00
./User/Vendor/MSFT/ClientCertificateInstall/SCEP/$FLEET_VAR_SCEP_WINDOWS_CERTIFICATE_ID/Install/KeyLength</LocURI>
DCSW: Add integration test for Windows SCEP profile (#35428) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #34708 A followup task to create an integration test, that uploads a profile with CA variables, and verifies it, + makes a final request to the SCEP server. Also cought the should instantly verified from MDM response, so added it here.
2025-11-12 19:59:09 +00:00
</Target>
<Meta>
<Format xmlns="syncml:metinf">int</Format>
</Meta>
<Data>1024</Data>
</Item>
</Add>
<Add>
<Item>
<Target>
<LocURI>
DUSW: Allow user-scoped SCEP profiles on Windows (#35672) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #35503 For this one I opted for a simple approach of just duplicating the arrays one for user, and one for device, then with the first loc uri that checks in of either device or user, sets the respective arrays, I thought while this was more LOC's it was easier to look at and maintain compared to regex matches etc, let me know if you think otherwise. # Checklist for submitter If some of the following don't apply, delete the relevant line. - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files) for more information. ## Testing - [x] Added/updated automated tests - [x] QA'd all new/changed functionality manually
2025-11-14 15:44:14 +00:00
./User/Vendor/MSFT/ClientCertificateInstall/SCEP/$FLEET_VAR_SCEP_WINDOWS_CERTIFICATE_ID/Install/HashAlgorithm</LocURI>
DCSW: Add integration test for Windows SCEP profile (#35428) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #34708 A followup task to create an integration test, that uploads a profile with CA variables, and verifies it, + makes a final request to the SCEP server. Also cought the should instantly verified from MDM response, so added it here.
2025-11-12 19:59:09 +00:00
</Target>
<Meta>
<Format xmlns="syncml:metinf">chr</Format>
</Meta>
<Data>SHA-1</Data>
</Item>
</Add>
<Add>
<Item>
<Target>
<LocURI>
DUSW: Allow user-scoped SCEP profiles on Windows (#35672) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #35503 For this one I opted for a simple approach of just duplicating the arrays one for user, and one for device, then with the first loc uri that checks in of either device or user, sets the respective arrays, I thought while this was more LOC's it was easier to look at and maintain compared to regex matches etc, let me know if you think otherwise. # Checklist for submitter If some of the following don't apply, delete the relevant line. - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files) for more information. ## Testing - [x] Added/updated automated tests - [x] QA'd all new/changed functionality manually
2025-11-14 15:44:14 +00:00
./User/Vendor/MSFT/ClientCertificateInstall/SCEP/$FLEET_VAR_SCEP_WINDOWS_CERTIFICATE_ID/Install/SubjectName</LocURI>
DCSW: Add integration test for Windows SCEP profile (#35428) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #34708 A followup task to create an integration test, that uploads a profile with CA variables, and verifies it, + makes a final request to the SCEP server. Also cought the should instantly verified from MDM response, so added it here.
2025-11-12 19:59:09 +00:00
</Target>
<Meta>
<Format xmlns="syncml:metinf">chr</Format>
</Meta>
ARCW: Add Renewal ID verification and support in windows profiles (#37179) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves no linked ticket as it was a miss # Checklist for submitter ## Testing - [x] Added/updated automated tests - [x] QA'd all new/changed functionality manually
2025-12-12 17:14:59 +00:00
<Data>CN=$FLEET_VAR_SCEP_WINDOWS_CERTIFICATE_ID,OU=$FLEET_VAR_SCEP_RENEWAL_ID</Data>
DCSW: Add integration test for Windows SCEP profile (#35428) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #34708 A followup task to create an integration test, that uploads a profile with CA variables, and verifies it, + makes a final request to the SCEP server. Also cought the should instantly verified from MDM response, so added it here.
2025-11-12 19:59:09 +00:00
</Item>
</Add>
<Add>
<Item>
<Target>
<LocURI>
DUSW: Allow user-scoped SCEP profiles on Windows (#35672) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #35503 For this one I opted for a simple approach of just duplicating the arrays one for user, and one for device, then with the first loc uri that checks in of either device or user, sets the respective arrays, I thought while this was more LOC's it was easier to look at and maintain compared to regex matches etc, let me know if you think otherwise. # Checklist for submitter If some of the following don't apply, delete the relevant line. - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files) for more information. ## Testing - [x] Added/updated automated tests - [x] QA'd all new/changed functionality manually
2025-11-14 15:44:14 +00:00
./User/Vendor/MSFT/ClientCertificateInstall/SCEP/$FLEET_VAR_SCEP_WINDOWS_CERTIFICATE_ID/Install/EKUMapping</LocURI>
DCSW: Add integration test for Windows SCEP profile (#35428) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #34708 A followup task to create an integration test, that uploads a profile with CA variables, and verifies it, + makes a final request to the SCEP server. Also cought the should instantly verified from MDM response, so added it here.
2025-11-12 19:59:09 +00:00
</Target>
<Meta>
<Format xmlns="syncml:metinf">chr</Format>
</Meta>
<Data>1.3.6.1.5.5.7.3.2</Data>
</Item>
</Add>
<Add>
<CmdID>10</CmdID>
<Item>
<Target>
<LocURI>
DUSW: Allow user-scoped SCEP profiles on Windows (#35672) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #35503 For this one I opted for a simple approach of just duplicating the arrays one for user, and one for device, then with the first loc uri that checks in of either device or user, sets the respective arrays, I thought while this was more LOC's it was easier to look at and maintain compared to regex matches etc, let me know if you think otherwise. # Checklist for submitter If some of the following don't apply, delete the relevant line. - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files) for more information. ## Testing - [x] Added/updated automated tests - [x] QA'd all new/changed functionality manually
2025-11-14 15:44:14 +00:00
./User/Vendor/MSFT/ClientCertificateInstall/SCEP/$FLEET_VAR_SCEP_WINDOWS_CERTIFICATE_ID/Install/ServerURL</LocURI>
DCSW: Add integration test for Windows SCEP profile (#35428) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #34708 A followup task to create an integration test, that uploads a profile with CA variables, and verifies it, + makes a final request to the SCEP server. Also cought the should instantly verified from MDM response, so added it here.
2025-11-12 19:59:09 +00:00
</Target>
<Meta>
<Format xmlns="syncml:metinf">chr</Format>
</Meta>
<Data>$FLEET_VAR_CUSTOM_SCEP_PROXY_URL_INTEGRATION</Data>
</Item>
</Add>
<Add>
<Item>
<Target>
<LocURI>
DUSW: Allow user-scoped SCEP profiles on Windows (#35672) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #35503 For this one I opted for a simple approach of just duplicating the arrays one for user, and one for device, then with the first loc uri that checks in of either device or user, sets the respective arrays, I thought while this was more LOC's it was easier to look at and maintain compared to regex matches etc, let me know if you think otherwise. # Checklist for submitter If some of the following don't apply, delete the relevant line. - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files) for more information. ## Testing - [x] Added/updated automated tests - [x] QA'd all new/changed functionality manually
2025-11-14 15:44:14 +00:00
./User/Vendor/MSFT/ClientCertificateInstall/SCEP/$FLEET_VAR_SCEP_WINDOWS_CERTIFICATE_ID/Install/Challenge</LocURI>
DCSW: Add integration test for Windows SCEP profile (#35428) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #34708 A followup task to create an integration test, that uploads a profile with CA variables, and verifies it, + makes a final request to the SCEP server. Also cought the should instantly verified from MDM response, so added it here.
2025-11-12 19:59:09 +00:00
</Target>
<Meta>
<Format xmlns="syncml:metinf">chr</Format>
</Meta>
<Data>$FLEET_VAR_CUSTOM_SCEP_CHALLENGE_INTEGRATION</Data>
</Item>
</Add>
<Add>
<Item>
<Target>
<LocURI>
DUSW: Allow user-scoped SCEP profiles on Windows (#35672) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #35503 For this one I opted for a simple approach of just duplicating the arrays one for user, and one for device, then with the first loc uri that checks in of either device or user, sets the respective arrays, I thought while this was more LOC's it was easier to look at and maintain compared to regex matches etc, let me know if you think otherwise. # Checklist for submitter If some of the following don't apply, delete the relevant line. - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files) for more information. ## Testing - [x] Added/updated automated tests - [x] QA'd all new/changed functionality manually
2025-11-14 15:44:14 +00:00
./User/Vendor/MSFT/ClientCertificateInstall/SCEP/$FLEET_VAR_SCEP_WINDOWS_CERTIFICATE_ID/Install/CAThumbprint</LocURI>
DCSW: Add integration test for Windows SCEP profile (#35428) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #34708 A followup task to create an integration test, that uploads a profile with CA variables, and verifies it, + makes a final request to the SCEP server. Also cought the should instantly verified from MDM response, so added it here.
2025-11-12 19:59:09 +00:00
</Target>
<Meta>
<Format xmlns="syncml:metinf">chr</Format>
</Meta>
<Data>2133EC6A3CFB8418837BB395188D1A62CA2B96A6</Data>
</Item>
</Add>
<Exec>
<Item>
<Target>
<LocURI>
DUSW: Allow user-scoped SCEP profiles on Windows (#35672) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #35503 For this one I opted for a simple approach of just duplicating the arrays one for user, and one for device, then with the first loc uri that checks in of either device or user, sets the respective arrays, I thought while this was more LOC's it was easier to look at and maintain compared to regex matches etc, let me know if you think otherwise. # Checklist for submitter If some of the following don't apply, delete the relevant line. - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files) for more information. ## Testing - [x] Added/updated automated tests - [x] QA'd all new/changed functionality manually
2025-11-14 15:44:14 +00:00
./User/Vendor/MSFT/ClientCertificateInstall/SCEP/$FLEET_VAR_SCEP_WINDOWS_CERTIFICATE_ID/Install/Enroll</LocURI>
DCSW: Add integration test for Windows SCEP profile (#35428) <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #34708 A followup task to create an integration test, that uploads a profile with CA variables, and verifies it, + makes a final request to the SCEP server. Also cought the should instantly verified from MDM response, so added it here.
2025-11-12 19:59:09 +00:00
</Target>
</Item>
</Exec>
Reference in a new issue Copy permalink