> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/documentation/crates/existing-crate-documentation/alert-on-expiring-app-reg-secrets-crate.md).
# Alert on Expiring App Reg Secrets Crate
{% hint style="info" %}
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.
{% endhint %}
## What does the Alert on Expiring App Reg Secrets Crate do?
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.
## Crate prerequisites
* The [Microsoft Cloud Integration Bundle](/documentation/integrations/integration-guides/microsoft-cloud-integration-bundle.md) must be set up before unpacking this Crate, to enable the Microsoft Graph integration with Rewst.
* Your [PSA](/documentation/integrations/top-5-integration-types-get-started-with-integrations-in-rewst.md#psa-integrations) must be integrated with Rewst.
* The `psa_default_board_id` [organization variable](/documentation/integrations/organization-variables.md#what-is-an-organization-variable) must be added
* The `default_psa` organization variable must be added
## Unpack the Alert on Expiring App Reg Secrets Crate
1. Navigate to **Marketplace** **> Crates** in the left side menu of the Rewst Platform.
2. Search for `Alert on Expiring App Reg Secrets`.
\
3. Click **Unpack Crate**.
4. Click **Continue.**
5. Enter your **Time Saved**.
6. Click **Unpack**.
7. Navigate to **Automations > Workflows**.
8. Search for `Alert on Expiring App Client Secrets [Part 1]`.
9. Click on the workflow to open it in the workflow builder.
10. 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.
11. Navigate to **Automations > Workflows**.
12. Search for `Alert on Expiring App Client Secrets [Part 1]`.
13. Click on the workflow to open it in the workflow builder.
14. 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.
### Update the cron trigger schedule
{% hint style="info" %}
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. Tickets will be created if expiring secrets are found.
{% endhint %}
The Crate runs on a cron trigger, and will execute the workflow to generate the ticket at the same time each day. You can adjust the chosen time for execution in the workflow itself. Edit a cron trigger in the workflow to change the timing of when it will routinely run.
1. Navigate to **Automations > Workflows**.
2. Search for `Alert on Expiring App Client Secrets [Part 1]`.
3. Click on the workflow to open it in the Workflow Builder.
4. Click on the trigger to open its settings in the right side menu.
5. Update the timing of the cron trigger as desired. Note that when entering the time into the **Cron Schedule** field, the correct format is minutes followed by hour. For example, 18 3, not 3 18.
6. If necessary, enable [Critical Timing](/documentation/automations/intro-to-triggers.md#critical-timing).
7. Click **Save Trigger**.
{% hint style="info" %}
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).
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.rewst.help/documentation/crates/existing-crate-documentation/alert-on-expiring-app-reg-secrets-crate.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.