|
| 1 | +#  Alert on Expiring App Reg Secrets Crate |
| 2 | + |
| 3 | +{% hint style="info" %} |
| 4 | +If you’re new to Crates, read through our introductory Crate documentation [here](https://docs.rewst.help/prebuilt-automations/crates). Find the Crate in our Crate Marketplace. |
| 5 | +{% endhint %} |
| 6 | + |
| 7 | +## What does the Alert on Expiring App Reg Secrets Crate do? |
| 8 | + |
| 9 | +Our Alert on Expiring App Reg Secrets Crate identifies any expiring client secrets in your application registrations and logs individual tickets for each client, as well as a detailed overall summary ticket. Reduce disruptions by getting notified on expiring application registration secrets. |
| 10 | + |
| 11 | +## Crate prerequisites |
| 12 | + |
| 13 | +* The [Microsoft Graph integration](../../documentation/integrations/individual-integration-documentation/cloud/microsoft-cloud-integration-bundle/microsoft-graph/microsoft-graph-integration-setup.md) must be set up before unpacking this Crate |
| 14 | +* psa\_default\_board\_id organization variable |
| 15 | +* default\_psa organization variable |
| 16 | + |
| 17 | +## Unpack the Alert on Expiring App Reg Secrets Crate |
| 18 | + |
| 19 | +1. Navigate to **Crates > Crate Marketplace** in the left side menu of the Rewst Platform. |
| 20 | +2. Search for `Alert on Expiring App Reg Secrets`.\ |
| 21 | + \ |
| 22 | +  |
| 23 | +3. Click **Unpack Crate**. |
| 24 | +4. Click **Continue.** |
| 25 | +5. Enter your **Time Saved**.\ |
| 26 | + \ |
| 27 | + |
| 28 | + |
| 29 | + <figure><img src="../../.gitbook/assets/Screenshot 2025-04-10 at 4.52.39 PM.png" alt="Screenshot of the Rewst platform showing the unpacking screen for a workflow crate titled "[Rewst Master v3] Azure: Alert on Expiring App Secrets [Part 1]". The page displays a description: "Identify any Application Registrations that have expiring certificates and log a ticket per client, with an overall ticket with all detailed information." Below that, there's a "Crate Configuration" section with fields for "Workflow Name" (pre-filled), "Time Saved (seconds)" (set to 0), and a trigger configuration showing a Cron Job marked as "Enabled". Buttons for "Previous" and "Unpack" appear at the bottom right."><figcaption></figcaption></figure> |
| 30 | +6. Click **Unpack**. |
| 31 | + |
| 32 | +## Test the Crate |
| 33 | + |
| 34 | +To test this Crate, you'll need to adjust the cron trigger's schedule to a few minutes in the future, then adjust it back to your regular schedule after the test. Alternatively, you could wait until the regularly scheduled run occurs and check your result, which would not require you to update the cron trigger schedule. |
| 35 | + |
| 36 | +1. Navigate to **Automations > Workflows**. |
| 37 | +2. Search for `Alert on Expiring App Client Secrets [Part 1]`.\ |
| 38 | + \ |
| 39 | + |
| 40 | + |
| 41 | + <figure><img src="../../.gitbook/assets/image (57) (2).png" alt="Screenshot of the Workflows page in the Rewst platform with a search for "expiring" applied. One workflow is listed: [ROC] Azure: Alert on Expiring App Client Secrets [Part 1], last updated on 2025-03-29 at 17:28. The row includes options to Configure, view Triggers (1), and Clone (Sync). A linked crate labeled Alert on Expiring App Reg Sec... is also visible. Filter icons appear under the "Updated By," "Attributes," and "Tags" columns. On the right, there are additional controls including a three-dot menu and a right-arrow for further actions."><figcaption></figcaption></figure> |
| 42 | +3. Click on the workflow to open it in the workflow builder.\ |
| 43 | + \ |
| 44 | + |
| 45 | + |
| 46 | + <figure><img src="../../.gitbook/assets/image (58) (2).png" alt="Screenshot of the Cron Trigger configuration for the workflow [ROC] Azure: Alert on Expiring App Client Secrets [Part 1] in the Rewst platform. The trigger type is fixed as Cron Trigger. Under Integration Overrides, three integration UUIDs are shown, with an indicator that 6 more items are hidden. The External Status section confirms "No errors detected" with a green checkmark. In the Trigger Parameters section: Timezone Canonical Names is set to UTC. Cron Schedule is 0 7 1 * *. The parsed output for the cron expression is displayed as: "At 07:00 AM, on day 1 of the month." Various top-bar icons are also visible for editing, syncing, and settings."><figcaption></figcaption></figure> |
| 47 | +4. Adjust the cron trigger's schedule to five minutes from your current time. The workflow will run on its own, and tickets will be created if expiring secrets are found. |
| 48 | + |
| 49 | +{% hint style="info" %} |
| 50 | +Got an idea for a new Crate? Rewst is constantly adding new Crates to our Crate Marketplace. Submit your idea or upvote existing ideas here in our [Canny feedback collector](https://rewst.canny.io/crates). |
| 51 | +{% endhint %} |
0 commit comments