Skip Ribbon Commands
Skip to main content

Using Google to Authenticate with SharePoint 2013

Collaborate with External Partners using Google Accounts

Brian Jones

05/06/2015


​​Having an on-premise SharePoint extranet is a great first step towards external collaboration, but giving out Windows credentials isn't a long term solution to managing external accounts. Active Directory federation isn't within the capabilities of many small businesses. One solution is to allow partners to login with their own cloud credentials, in this instance managed by Google, enabled by Azure.​

Step 1: Create Google Account

  • ​Go to the Google developers console  ​
  • Sign in if you have an account, otherwise create an account and log in
  • Click on Create Project
  • Enter a name for your project e.g. SharePoint Authentication and click Create
The project will now be created it will take a few seconds and then you will be taken into the app.
  • Click on APIs & auth
  • Click on Consent Screen
  • Enter a name for your project and click Save
  • Click on Credentials
  • Click on Create new Client ID
  • Select Web application and click on Create Client ID
  • Copy the Client ID and Client secret from the screen that is displayed
Step 2: Create Windows Azure Access Control Namespace
  • Select App Services, Active Directory and finally Access Control
  • Enter a name for your access control namespace, select the region you are in and click Create
  • Click on Active Directory from the navigation menu on the left
  • Click on Access Control Namespaces
  • Select the namespace that you have just created and click on Manage
Step 3: Configure Access Control Service
  • Click on Identity providers
  • Click on Add
  • Select Google and click on Next
  • Enter the Client ID and Client secret that you copied from your Google app in step 1 and click Save
  • Click Relying party applications
  • Click on Add
  • Enter a name for the replying party application in the name field
  • In Realm enter the URL of your SharePoint web application
  • In return URL enter the URL of your SharePoint web application followed by /_trust
  • In the token format select SAML 1.1
  • Change the token lifetime (secs) to 700 and click Save
  • Click on Rule Groups
  • Click on Add
  • Enter a name for the rule group and click Save
  • Click on Generate
  • Select     Google     and click on Generate
  • Click Save
Step 4: Certificates and Keys
  • Click on Certificates and Keys
  • Click on Save
  • Select your relying party application from the drop down list (You created it in step 3)
  • On the page copy the MakeCert command
  • On your client machine you will need to generate a certificate to be used for the trust. Launch a command prompt as administrator, navigate to the directory where makecert is installed and run the copied command.
  • If you don't have makecert you can get it from here: makecert
  • The certificate will be deployed to your certificate store, you will need to export a .CER and .PFX.
  • Click on start > run, enter MMC and click OK
  • In the console click on File > Add/Remove Snap-in
  • Select certificates and click Add
  • Select My user account and click finish
  • Click Ok
  • Expand Certificates – Current User
  • Expand Personal
  • Select Certificates
  • In the certificates list you should see your new certificate
  • Right click on the certificate, select All tasks > Export
  • Click next
  • Select No, do not export the private key and click next
  • Click next leaving the defaults
  • Click browse, enter a suitable name for the certificate e.g. Auth and save the file somewhere suitable.
  • Click Save
  • Click Next
  • Click Finish
  • Click OK on the success message
  • Right click on the certificate, select All tasks > Export
  • Click next
  • Select Yes, export the private key and click next
  • Click next leaving the defaults
  • Select Password and enter a password (remember this you will need it) and click next.
  • Click browse, enter a suitable name for the certificate e.g. Auth and save the file somewhere suitable.
  • Click Save
  • Click Next
  • Click Finish
  • Click OK on the success message
  • Return to your access control service browser window.
  • Click on Browse
  • Browse to the .pfx file you created in the previous step and click open
  • Enter the password and click Save
Step 5: SharePoint Configuration
  • Logon to your SharePoint server
  • Copy the .cer file you created in a previous step to the server
  • Open the SharePoint Management Shell as administrator
  • Run the following PowerShell commands

    $realm="http://my.sharepoint.com"

  • Where the url is the url of your SharePoint web application

    $signinurl="https://mysharepointlogin.accesscontrol.windows.net:443/v2/wsfederation?wa=wsignin1.0&wtrealm=https://my.sharepoint.com/"

     
  • Replacing the highlighted sections with your access control service URL and your web application URL

    $certlocation="C:\Certificates\auth.cer"

  • Replacing the path with the location of your .cer file

    $rootcertificate=Get-PfxCertificate$certlocation

    New-SPTrustedRootAuthority"MyGoogleSharePointLogin"-Certificate$rootcertificate

    $certificate=New-ObjectSystem.Security.Cryptography.X509Certificates.X509Certificate2($certlocation)

    $ClaimTypingMapping=New-SPClaimTypeMapping-IncomingClaimType"http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress"-IncomingClaimTypeDisplayName"Email"-SameAsIncoming

    New-SPTrustedIdentityTokenIssuer-Name"Google Authentication"-Description"Google Authentication"-Realm$realm-ImportTrustCertificate$certificate-ClaimsMappings$ClaimTypingMapping-SignInUrl$signinurl-IdentifierClaim"http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress"

 
  • Once you have run the PowerShell commands you will need to add the identity provider to your web application.
  • Open SharePoint Central Administration
  • Click on Application Management
  • Click on Manage Web Applications
  • Select the Web Application that will be using Google for authentication
  • Click on authenticationproviders in the toolbar
  • Select the relevant zone, this will be default if you only have one zone.​​
  • Scroll down the window, select Trusted Identity provider and select Google Authentication

Step 6: Testing

  • Open a web browser and navigate to your root site collection on the web application. You should get a drop down list showing the logon options.
  • Select Google Authentication and you should get the Google authentication page.
  • ​​​Enter your google credentials and click sign in.
  • You should be returned to your SharePoint page. You will probably be given an access denied message because the account has not been given any rights to your site. Just grant rights as you would normally.
  • When granting rights to Google users you will need to use the full email address. People picker will not resolve the name unless the user is already added but you will still be able to add new users.

Top Blog Posts From Fuse

 

 

Migrating Server Environments to Azure – without using PowerShell https://www.fusecollaboration.com/blog/migrating-server-environments-to-azure-without-using-powershellMigrating Server Environments to Azure – without using PowerShell
Recovering Workflow History after 60 dayshttps://www.fusecollaboration.com/blog/recovering-workflow-history-after-60-daysRecovering Workflow History after 60 days
Simple Incoming Email with On Premises SharePoint and Exchangehttps://www.fusecollaboration.com/blog/simple-incoming-email-with-on-premises-sharepoint-and-exchangeSimple Incoming Email with On Premises SharePoint and Exchange
Dynamic Page Layouts in SharePoint 2013 - Part 1https://www.fusecollaboration.com/blog/dynamic-page-layouts-in-sharepoint-2013-part-1Dynamic Page Layouts in SharePoint 2013 - Part 1
Using Google to Authenticate with SharePoint 2013https://www.fusecollaboration.com/blog/using-google-to-authenticate-with-sharepoint-2013Using Google to Authenticate with SharePoint 2013

Recommended Pages

 

 

Skype for Businesshttps://www.fusecollaboration.com/technologies/skype-for-businessSkype for Business
About Fuse Collaboration Serviceshttps://www.fusecollaboration.com/fuse-home/aboutAbout Fuse Collaboration Services
Privacy Policyhttps://www.fusecollaboration.com/fuse-home/privacy-policyPrivacy Policy
Hosted Skype for Businesshttps://www.fusecollaboration.com/technologies/skype-for-business/hosted-skype-for-businessHosted Skype for Business
SharePoint Consulting, Design and Developmenthttps://www.fusecollaboration.com/technologies/sharepointSharePoint Consulting, Design and Development

 About us

Fuse Collaboration Services is a Cloud Solution Provider and Microsoft Gold Partner specialising in delivering SharePoint, Skype for Business, and Azure cloud-based solutions. Based in Northampton, UK.

Microsoft Gold Partner Logo showing 5 competencies

Read more

 Latest Tweets

 Latest Blog

 

 

‘We’d love you to stick around’. But stick around where?3728<p class="lead">Here at Fuse Collaboration Services both our personal and professional email inboxes are receiving a steady flow of emails from companies asking us to stay on their mailing lists. This is the most obvious and public aspect of the new GDPR that is currently being implemented.</p><p>There are a couple of positive side-effects from these new regulations, not least that by forcing you to opt in to mailing lists to make sure you are only receiving what you want to receive a company will really know how engaged you are, making your email address all the more valuable when it comes to marketing.</p><p>Companies have been responding to the GDPR changes by re-working their data management policies, but how much time is being put into how these policies can be enacted day-to-day, especially away from the aforementioned marketing email lists?</p><p>For example, if you have written a policy that says that emails are going to be stored for one year before deletion, how are you going to store them away from an active email server (thereby reducing the burden on a day-to-day server), or keep hold of them once a member of staff leaves? Or what happens if data is accidentally deleted by a member of staff?</p><p>Furthermore, data security is made all the more important as more and more companies opt for a flexible working approach where their staff can work from remote locations, such as home or (dare we say it) a high street coffee chain with its free Wi-Fi access.</p><p>Domestic or public internet access networks are unlikely to have the same levels of security as a company's, which makes it all the more important that any data transfer between a central hub and remote laptop is encrypted and has the latest security.</p><p>Chris Evans of Computer Weekly has highlighted <a href="https&#58;//www.computerweekly.com/feature/GDPR-brings-serious-implications-for-data-storage" target="_blank"> <span style="text-decoration&#58;underline;">five areas</span></a>&#160;which will impact the day-to-day work of the data storage manager under GDPR, including&#58;</p><ul><li>encryption; </li><li>detailed application-to-storage mapping;</li><li>security and audit; </li><li>validation of test and development requirements;</li><li>and collaborating closely with colleagues.</li></ul><p>Ultimately, you need to be able to give all your customers, clients, stakeholders and staff the confidence that their data and documents are stored securely, but also in a way that allows you to respond to data requests quickly and efficiently without having to wade through a mound of irrelevant information.</p><p>You also need to have the peace of mind that any deleted information can be recovered within your policy timetables, whether they be one year, five years, or longer than that.</p><p>There is also a danger that you could be sucked into a one-size-fits-all approach using policy and storage templates that have been designed for organisations that are in a different sector or are of a vastly different size to your own.</p><p>Fuse's data back-up and storage solutions tick all of the boxes you need to have that peace of mind to concentrate on your main business, namely growing as a company, while also being tailored to your specific needs.</p><p>Fuse uses a mixture of cloud-based packages to meet your requirements and allow your staff to access their relevant information <em>securely </em>regardless of where they are working. Our solutions are also easy to monitor by your in-house IT team, so that in the unlikely event of a data breach it can be identified, resolved and reported quickly.</p><div class="well well-lg"><p class="lead">Give us a call on 01604 797979 and we can have a chat about how you can make sure your data policy matches your day-to-day operations and requirements.</p></div> | Chris Wearmouth | 693A30232E777C6675736563735C632E776561726D6F757468 i:0#.w|fusecs\c.wearmouth16/05/2018 23:00:002018-05-16T23:00:00ZData security and rentention in a cloud based infrastructureData security in a cloud based infrastructure14/06/2018 09:56:102550htmlFalseaspx

 Contact us

Our address
12 Brookfield, Duncan Close
Moulton Park, Northampton
NN3 6WL
P: +44(0)1604 797979
Contact Us