FEED Validator

for Atom and RSS and KML

Sorry

This feed does not validate.

line 26, column 28: Invalid email address: Todd O. Klindt [help]

      <author>Todd O. Klindt</author>
                            ^

In addition, interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

line 15, column 55: Image title doesn't match channel title [help]

      <title>Todd Klindt's Office 365 Admin Blog: Posts</title>
                                                       ^

line 23, column 0: description should not contain onclick attribute (4 occurrences) [help]
```
<div>Category: <a onclick="OpenPopUpPage('https:\u002f\u002fwww.toddk ...
```
line 25, column 3: description should not contain relative URL references: /PoshAddClientCreds [help]
```
]]></description>
   ^
```
line 31, column 2: Missing atom:link with rel="self" [help]
```
  </channel>
  ^
```

Source: http://www.toddklindt.com/blog/_layouts/listfeed.aspx?List=%7B56F96349-3BB6-4087-94F4-7F95FF4CA81F%7D

<?xml version="1.0" encoding="UTF-8"?>

<?xml-stylesheet type="text/xsl" href="/blog/_layouts/RssXslt.aspx?List=56f96349-3bb6-4087-94f4-7f95ff4ca81f" version="1.0"?>
<rss version="2.0">
<channel>
<title>Todd Klindt's Blog Posts</title>
<link>https://www.toddklindt.com/blog/Lists/Posts/AllPosts.aspx</link>
<description>RSS feed for the Posts list.</description>
<copyright>Todd Klindt</copyright>
<lastBuildDate>Tue, 16 Apr 2024 04:12:18 GMT</lastBuildDate>
<generator>Microsoft SharePoint Foundation RSS Generator</generator>
<ttl>60</ttl>
<language>en-US</language>
<image>
<title>Todd Klindt's Office 365 Admin Blog: Posts</title>
<url>https://www.toddklindt.com/blog/_layouts/images/homepage.gif</url>
<link>https://www.toddklindt.com/blog/Lists/Posts/AllPosts.aspx</link>
</image>
<item>
<title>Simplifying Client Credentials with PowerShell: Add-ClientCredential</title>
<link>https://www.toddklindt.com/blog/Lists/Posts/ViewPost.aspx?ID=900</link>
<description><![CDATA[<div>Body: <div class="ExternalClass9C44859E60064C07911CF10A9B954B8C">If you’ve been around the block with SharePoint or Microsoft 365 administration, you know that handling client credentials can sometimes feel like juggling with fire. When I start a new engagement with a client I generally get credentials to access their tenant. Of course they immediately go into our password management tool. I also do a lot of PowerShell scripting for my clients, so I save them to the Windows Credential store too, so that I can connect with Connect-PnPOnline without having to enter them each time. And while that’s not a lot of work, I thought I could streamline it. That’s why I’ve put together a PowerShell command, Add-ClientCredential, that makes it a little easier. <h1>What Does Add-ClientCredential do?</h1> In a nutshell, this PowerShell command is designed to streamline the process of adding client credentials in a SharePoint or Microsoft 365 environment. It stores your credential for <a href="https://tenant.sharepoint.com">https://tenant.sharepoint.com</a> and <a href="https://tenant-admin.sharepoint.com">https://tenant-admin.sharepoint.com</a>. If you don’t specify any credentials when you connect with Connect-PnPOnline it will look for them in the Windows Credential Store. If you have one assigned for the root of the tenant, <a href="https://tenant.sharepoint.com">https://tenant.sharepoint.com</a>, it will also use that for other sites in the tenant, like <a href="https://tenant.sharepoint.com/sites/ToddisTheBest">https://tenant.sharepoint.com/sites/ToddisTheBest</a>, if a credential is not saved for that specific site. Here’s a quick example: <blockquote> Add-ClientCredential -TenantName "contoso" -UserName <a href="mailto:admin@contoso.com">admin@contoso.com</a> </blockquote> I like this method because then my password will never show up in History or a Transcript if one is running. Since we didn’t pass it a password, it will prompt you for one. Then it will create credential entries for <a href="https://contoso.sharepoint.com">https://contoso.sharepoint.com</a>, <a href="http://contoso.sharepoint.com">http://contoso.sharepoint.com</a>, and <a href="https://contoso-admin.sharepoint.com">https://contoso-admin.sharepoint.com</a> To pass it a password, do it like this: <div> <blockquote> Add-ClientCredential -TenantName "contoso" -UserName <a href="mailto:admin@contoso.com">admin@contoso.com</a> -Password (ConvertTo-SecureString "YourPassword” -AsPlainText -Force) </blockquote> Keep in mind that will show up in plain text in PowerShell’s Get-History, or the Transcript file, if you have that running. I built in some smarts so that if there is already a credential stored for “Contoso” it will let you know and ask you if you want to overwrite it. If you want to get super fancy you can add the –TestCredential switch which will test the credentials you gave it by logging in with them. All of this is available if you run help Add-ClientCredential –Examples. In the background this function uses <a href="https://pnp.github.io/powershell/cmdlets/Add-PnPStoredCredential.html">Add-PnPStoredCredential</a> to store the credentials for you. It adds them for the root of the tenant, and the –admin URL. </div> <h1>How to Get Started</h1> To get your hands on this little beauty, head over to <a href="https://github.com/ToddKlindt/PowerShell">my GitHub repository</a>. You can download <a href="https://github.com/ToddKlindt/PowerShell/blob/master/addclientcreds.psm1">addclientcreds.psm1</a> itself, or clone the whole repo. Use Import-Module to import it into your PowerShell host and you’re ready to go. <h1>Wrapping Up</h1> addclientcreds.psm1 is my attempt to put a little more simplicity and sanity into the world of SharePoint and Microsoft 365 administration. I hope you find it as useful as I do. As always, I welcome your feedback and questions. Drop a comment below or shoot me a message on Twitter <a href="https://twitter.com/ToddKlindt">@ToddKlindt</a>. tk ShortURL: <a href="/PoshAddClientCreds">https://www.toddklindt.com/PoshAddClientCreds</a> </div></div>
<div>Category: <a onclick="OpenPopUpPage('https:\u002f\u002fwww.toddklindt.com\u002fblog\u002f_layouts\u002flistform.aspx?PageType=4\u0026ListId={8221A7C5-26F5-4CA7-BCD5-8B626A7C6AB8}\u0026ID=8\u0026RootFolder=*', RefreshPage); return false;" href="https://www.toddklindt.com/blog/_layouts/listform.aspx?PageType=4&ListId={8221A7C5-26F5-4CA7-BCD5-8B626A7C6AB8}&ID=8&RootFolder=*">PowerShell</a>; <a onclick="OpenPopUpPage('https:\u002f\u002fwww.toddklindt.com\u002fblog\u002f_layouts\u002flistform.aspx?PageType=4\u0026ListId={8221A7C5-26F5-4CA7-BCD5-8B626A7C6AB8}\u0026ID=24\u0026RootFolder=*', RefreshPage); return false;" href="https://www.toddklindt.com/blog/_layouts/listform.aspx?PageType=4&ListId={8221A7C5-26F5-4CA7-BCD5-8B626A7C6AB8}&ID=24&RootFolder=*">Office 365</a>; <a onclick="OpenPopUpPage('https:\u002f\u002fwww.toddklindt.com\u002fblog\u002f_layouts\u002flistform.aspx?PageType=4\u0026ListId={8221A7C5-26F5-4CA7-BCD5-8B626A7C6AB8}\u0026ID=29\u0026RootFolder=*', RefreshPage); return false;" href="https://www.toddklindt.com/blog/_layouts/listform.aspx?PageType=4&ListId={8221A7C5-26F5-4CA7-BCD5-8B626A7C6AB8}&ID=29&RootFolder=*">PnP</a></div>
<div># Comments: <a onclick="OpenPopUpPage('https:\u002f\u002fwww.toddklindt.com\u002fblog\u002f_layouts\u002flistform.aspx?PageType=4\u0026ListId={9632BBFE-1432-4B68-A96B-E6B96499F2DA}\u0026ID=0\u0026RootFolder=*', RefreshPage); return false;" href="https://www.toddklindt.com/blog/_layouts/listform.aspx?PageType=4&ListId={9632BBFE-1432-4B68-A96B-E6B96499F2DA}&ID=0&RootFolder=*"></a></div>
]]></description>
<author>Todd O. Klindt</author>
<category>PowerShell; Office 365; PnP</category>
<pubDate>Wed, 27 Sep 2023 14:36:50 GMT</pubDate>
<guid isPermaLink="true">https://www.toddklindt.com/blog/Lists/Posts/ViewPost.aspx?ID=900</guid>
</item>
</channel>
</rss>

Home · About · News · Docs · Terms