# SAML Certificate Expiration Notice (Workflows template) **URL:** \ **Category:** Templates\ **Created:** [September 11, 2024, 7:32pm UTC](https://devforum.okta.com/t/saml-certificate-expiration-notice-workflows-template/30523 "2024-09-11T19:32:00Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Dave\_Okta](https://avatars.discourse-cdn.com/v4/letter/d/da6949/32.png) [@Dave\_Okta](https://devforum.okta.com/u/Dave_Okta)\ **Post date:** [September 11, 2024, 7:32pm UTC](https://devforum.okta.com/t/saml-certificate-expiration-notice-workflows-template/30523/1 "2024-09-11T19:32:00Z")
Hey all, Dave from Okta here - I wrote this template a few years back to notify admins of any soon-to-expire SAML certificates in their org. In its current form, it will work for up to 2000 apps, but it’s easily modifiable to process as many as you need. Attached are the template notes and the flowpack folder. Enjoy! [dcCertificateExpirationNotice.folder](https://devforum.okta.com/uploads/short-url/hUcOetFTaamv9SxU30rW2xsKiRI.folder) (295.7 KB) [Workflows Discovery - Certificate Expiration Notice.pdf.zip](https://devforum.okta.com/uploads/short-url/9YP12pp99GUckFqqNmrAIblRnKo.zip) (38.2 KB) ---
**Author:** ![Mockup4521](https://avatars.discourse-cdn.com/v4/letter/m/59ef9b/32.png) [@Mockup4521](https://devforum.okta.com/u/Mockup4521)\ **Post date:** [September 12, 2024, 8:31pm UTC](https://devforum.okta.com/t/saml-certificate-expiration-notice-workflows-template/30523/2 "2024-09-12T20:31:00Z")
Hi Dave. Thanks for sharing! When I try to import the flow I’m getting an error. Attached a screenshot. ‘The Flow contains Accounts not accessible to the requesting client.’ Will this also report on SAML encryption certs? ---
**Author:** ![Dave\_Okta](https://avatars.discourse-cdn.com/v4/letter/d/da6949/32.png) [@Dave\_Okta](https://devforum.okta.com/u/Dave_Okta)\ **Post date:** [September 13, 2024, 2:42pm UTC](https://devforum.okta.com/t/saml-certificate-expiration-notice-workflows-template/30523/3 "2024-09-13T14:42:04Z")
Hmm, not 100% sure, but my flow is built with Okta, Google and O365 Mail connections - maybe you don’t have those in your environment (Gmail or O365)? ---
**Author:** ![maxkatz](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/maxkatz/32/5624_2.png) [@maxkatz](https://devforum.okta.com/u/maxkatz)\ **Post date:** [September 13, 2024, 8:04pm UTC](https://devforum.okta.com/t/saml-certificate-expiration-notice-workflows-template/30523/4 "2024-09-13T20:04:27Z")
Hi @Mockup4521 - Could you share the error screenshot? ---
**Author:** ![Mockup4521](https://avatars.discourse-cdn.com/v4/letter/m/59ef9b/32.png) [@Mockup4521](https://devforum.okta.com/u/Mockup4521)\ **Post date:** [September 17, 2024, 6:48pm UTC](https://devforum.okta.com/t/saml-certificate-expiration-notice-workflows-template/30523/5 "2024-09-17T18:48:36Z")
Thanks Dave & Max. I’m a new user, the forum is still not allowing me to upload a picture. Would make sense, I don’t have Google or O365 connections. Anyway, I can modify the download to remove that requirement? Also do you happen to know if it supports the SAML encryption cert expiry? That’s what we are after. ---
**Author:** ![Dave\_Okta](https://avatars.discourse-cdn.com/v4/letter/d/da6949/32.png) [@Dave\_Okta](https://devforum.okta.com/u/Dave_Okta)\ **Post date:** [September 17, 2024, 7:06pm UTC](https://devforum.okta.com/t/saml-certificate-expiration-notice-workflows-template/30523/6 "2024-09-17T19:06:07Z")
Yes, that’s what it does. Let me remove those cards and re-upload it to see if that will work for you. Give me a few minutes… ---
**Author:** ![Dave\_Okta](https://avatars.discourse-cdn.com/v4/letter/d/da6949/32.png) [@Dave\_Okta](https://devforum.okta.com/u/Dave_Okta)\ **Post date:** [September 17, 2024, 7:10pm UTC](https://devforum.okta.com/t/saml-certificate-expiration-notice-workflows-template/30523/7 "2024-09-17T19:10:53Z")
Ok, try this one - I removed the Gmail and O365 cards. You’ll just need ot come up with a way to notify someone if a cert is expiring… [dcCertificateExpirationWarningNoEmail.folder](https://devforum.okta.com/uploads/short-url/mzJrlTTKCagDDD35iwosm1hQFSu.folder) (290.6 KB) ---
**Author:** ![Mockup4521](https://avatars.discourse-cdn.com/v4/letter/m/59ef9b/32.png) [@Mockup4521](https://devforum.okta.com/u/Mockup4521)\ **Post date:** [September 18, 2024, 7:39pm UTC](https://devforum.okta.com/t/saml-certificate-expiration-notice-workflows-template/30523/8 "2024-09-18T19:39:33Z")
Imported just fine. Thanks Dave! ---
**Author:** ![Dave\_Okta](https://avatars.discourse-cdn.com/v4/letter/d/da6949/32.png) [@Dave\_Okta](https://devforum.okta.com/u/Dave_Okta)\ **Post date:** [September 18, 2024, 7:58pm UTC](https://devforum.okta.com/t/saml-certificate-expiration-notice-workflows-template/30523/9 "2024-09-18T19:58:47Z")
Great! Let me know if you have any questions. ---
**Author:** ![LFC20-25](https://avatars.discourse-cdn.com/v4/letter/l/9e8a1a/32.png) [@LFC20-25](https://devforum.okta.com/u/LFC20-25)\ **Post date:** [October 23, 2025, 4:25pm UTC](https://devforum.okta.com/t/saml-certificate-expiration-notice-workflows-template/30523/10 "2025-10-23T16:25:36Z")
Hi Dave, Great flow. It’s saved me a lot of work. It handles the SAML certificates from the Okta side, however there is one thing missing from the report. We have some SAML integrations where we use the vendor supplied SAML certificate for encryption which has it’s own expiration date. If you query an app which has a SAML encryption certificate /api/v1/apps/${appId} then search for “x5c” you will find the vendor provided certificate. The cert is missing the begin/end. Also the \r\n need characters need to be replaced with line feeds to recreate the certificate. I wondered if you or anyone in the forum had a workflow that retrieved that too? ---
**Author:** ![Dave\_Okta](https://avatars.discourse-cdn.com/v4/letter/d/da6949/32.png) [@Dave\_Okta](https://devforum.okta.com/u/Dave_Okta)\ **Post date:** [January 15, 2026, 10:15pm UTC](https://devforum.okta.com/t/saml-certificate-expiration-notice-workflows-template/30523/11 "2026-01-15T22:15:19Z")
Ok, here we are in 2026 and this flowpack needed some updating! I removed a bunch of the extraneous info collected from the apps and also implemented a streaming action instead of the old way we processed pagination. That took the whole thing down to 3 flows. Enjoy! [dcCertificateExpirationWarningV2.folder.zip](https://devforum.okta.com/uploads/short-url/hSFeTFLHXdlvFEkcupFLzRH65P5.zip) (17.4 KB)