Deploy saml2aws to Microsoft Intune
VersentWindowsversion 2.36.19, 13 March 2025
saml2aws is in the PatchBee catalog as a Windows app from Versent, synced from the Windows Package Manager community repository (winget). Pick it in the App Library and PatchBee writes the deployment plan below, builds the package, publishes it to your Intune tenant and assigns it to the Entra groups you choose. New versions then follow through your update rings.
The plan PatchBee writes
saml2aws as an Intune app
The standard form for a MSI (WiX) (x64, scope decided at plan time). The real plan is generated from the installer when you package, and shown in full before anything is published; every field can be changed.
- Intune app type
- Windows app (Win32), .intunewin
- Install
- msiexec /i "saml2aws.msi" /qn /norestart
- Uninstall
- msiexec /x {5D33608C-E3F3-43A2-8FF5-5B2B209E0E7E} /qn /norestart
- Detection
- MSI product code. Product code {5D33608C-E3F3-43A2-8FF5-5B2B209E0E7E}, version 2.36.19 or newer.
- Requirements
- x64, ARM, ARM64
Installers in version 2.36.19
| Architecture | Type | Scope | Hash |
|---|---|---|---|
| x64 | MSI (WiX) | scope decided at plan time | SHA-256 published |
| x64 | Zip archive | scope decided at plan time | SHA-256 published |
| ARM | Zip archive | scope decided at plan time | SHA-256 published |
| ARM64 | Zip archive | scope decided at plan time | SHA-256 published |
PatchBee downloads the installer from the publisher's own URL and verifies its SHA-256 against the catalog before packaging. "None published" means the source carries no hash for this download, so that check has nothing to compare against; packaging still works.
Silent install switches
Recorded for saml2aws in its winget manifest. PatchBee uses them as the installer's unattended switches, so the package installs without a click.
- Install location
- APPLICATIONROOTDIRECTORY="<INSTALLPATH>"
About saml2aws
CLI tool which enables you to login and retrieve AWS temporary credentials using with ADFS or PingFederate Identity Providers.
This is based on python code from How to Implement a General Solution for Federated API/CLI Access Using SAML 2.0.
The process goes something like this:
- Setup an account alias, either using the default or given a name
- Prompt user for credentials
- Log in to Identity Provider using form based authentication
- Publisher
- Versent
- Homepage
- github.com/Versent/saml2aws
- License
- MIT
- Source
- winget · Versent.saml2aws
- Versions in catalog
- 1
How this becomes an app in your tenant
Sign in with your Microsoft work account and connect your Intune tenant once. Find saml2aws in the App Library, open its plan (the commands, detection rule and requirements above, editable) and publish: PatchBee downloads and verifies the installer, builds the package, creates the Intune app and assigns your groups. When Versent ships a new version, PatchBee detects it and rolls it out through your rings, with supersedence and rollback.
Read the step-by-step guideMore Windows apps
Catalog data as of 11 October 2026, from the Windows Package Manager community repository (winget). The product re-reads the source every night and plans against the live catalog, so the version here may already be one behind. Nothing is published to a tenant without an administrator approving the plan.