This post was most recently updated on August 13th, 2018.
So, you have a Client Id and a Client Secret, but don’t know if they work anymore? Maybe they are expired? Maybe someone removed them? No worries! We can use PowerShell to validate them easily!
By using PowerShell, it’s fairly straightforward to verify, that your Client Id and Client Secret work. See the snippets below for 2 different steps:
- First we validate, that the values work.
- If they don’t, let’s run another script to see if the Client Id exists but has expired.
Validate your Client Id by trying to connect with it
We can validate the Client Id and Secret, by using Connect-PnPOnline to connect to SharePoint Online.
In other words, in the example, I’m using the PnP PowerShell commandlets to authenticate against a SharePoint Online site, using a Client Id (called AppId) and a Client Secret (called App Secret).
# First, we install the PnP cmdlets in case we don't have them already Install-Module SharePointPnPPowerShellOnline # If you have them, let's import the module! Import-Module SharePointPnPPowerShellOnline # After this, we can run Connect-PnPOnline Connect-PnPOnline -Url [your_sharepoint_site_url] -AppId [clientId] -AppSecret [clientSecret]
This shouldn’t return anything. If it doesn’t, it means it works 🙂
In case that didn’t work, your principal might have expired, or your values are simply not valid. This should lead to an authentication error!
Check your Client Id’s expiration date
To verify that the Client Id hasn’t expired, but rather is still valid, we’ll query the service principals in PowerShell using some of the available cmdlets. See below for different options…
Azure AD v1 (MSOnline)
You can run this in SharePoint Online Management Shell or Windows PowerShell:
# First, we install the cmdlets in case we don't have them already Install-Module MSOnline # If you have them already, let's import the module! Import-Module MSOnline # Then connect Connect-MSOLService (Get-MsolServicePrincipalCredential -AppPrincipalId [clientId] -ReturnKeyValues $true).EndDate.ToShortDateString() | select -first 1
This (almost) one-liner will get all valid entries with your clientId (it’ll probably return 3 service principals), then fish out their end dates, and pick the first one.
You should get just a short date in response.
But wait! What if you don’t have MSOnline (Azure AD v1 cmdlets) installed? What if you hate legacy technology, and want to only use the coolest new commandlets? I actually got a question about this on Twitter – how to query the end date with Azure AD v2 cmdlets?
Azure AD v2 (AzureAD)
It’s not that difficult, luckily! See below for a script sample:
# This is only needed, if you don't have AzureAD (v2) cmdlets installed already Install-Module AzureAD # If you have them already, we'll import the package Import-Module AzureAD # Then we connect, and query for the service principals Connect-AzureAD (Get-AzureADServicePrincipal -All $true -Filter "appId eq '[clientId]'").KeyCredentials.EndDate.ToShortDateString() | select -first 1
Not that complicated either! You should get just a short date in response.
Note that you’ll need to use single quotes for the filter statement – otherwise PowerShell will fail miserably at parsing your filter!
- See the documentation for Connect-PnPOnline here.
- Check out the docs for
- See more information about SharePoint PnP commandlets here.
Latest posts by Antti K. Koskela (see all)
- Subsite creation in SharePoint fails with error 0x80070005 for any user (even global/farm admins!) - December 4, 2018
- New-PnPSite fails with “SiteStatus” : 3 - November 29, 2018
- Issues with User Profile Property visibility in Search-powered functionalities - November 27, 2018
- “PictureThumbnailURL” always null in SharePoint Online Search results - November 21, 2018