{"id":310,"date":"2011-04-18T09:28:00","date_gmt":"2011-04-18T18:28:00","guid":{"rendered":"http:\/\/www.cloudidentity.com\/blog\/2011\/04\/18\/acs-extensions-for-umbraco-part-ii-social-providers\/"},"modified":"2011-04-18T09:28:00","modified_gmt":"2011-04-18T18:28:00","slug":"acs-extensions-for-umbraco-part-ii-social-providers","status":"publish","type":"post","link":"https:\/\/www.cloudidentity.com\/blog\/2011\/04\/18\/acs-extensions-for-umbraco-part-ii-social-providers\/","title":{"rendered":"ACS Extensions for Umbraco – Part II: Social Providers"},"content":{"rendered":"

Welcome to the second installment of the series on the ACS Extensions for Umbraco, part of the big ACS launch wave!<\/p>\n

This time I am going to assume that you succesfully installed the Extensions on your Umbraco instance, and you want to start accepting members from social & web identity providers. You\u2019ll see how easy it is to stitch together the sign-up and sign-in machinery, I\u2019d estimate 3 mins max, and how we integrated the classic email verification flow into our invitation engine.<\/p>\n

As usual, I am going to paste here what we wrote in the docs. However, remember that one of the big success factors for Umbraco is its great flexibility: in the same spirit, feel free to tinker with the Extensions as well to add any extra feature you may need. Few suggestions: bulk invitations, self-registering pages, etc.<\/p>\n

Access Control Service (ACS) Extensions for Umbraco<\/h3>\n

\"social-video\"
‘Click here for a video walkthrough of this tutorial’ <\/a><\/p>\n

One of the main features of the ACS Extensions is the ability to add members to your Umbraco web site directly from social providers: people will be able to sign up to your web site without having to create a new account and remember a new password, an you will not need to maintain credentials, field calls for lost passwords and so on.<\/p>\n

The ACS Extensions accomplish this by providing you with a workflow for inviting users via a simple email verification system. The ACS Extensions also provide you some UI macro which you can use for creating sign-in and sign-up pages in just few clicks. The sign-in and sign-up mechanisms are integrated with the role-based security supported natively by Umbraco, the member groups.<\/p>\n

In the section below we will walk you through the process of enabling classic sign-in and sign-up authentication features in your web site: this will help you to understand how the various components of the ACS Extensions work, so that you will be able to devise your own flow.<\/p>\n

 <\/p>\n

<\/a><\/a><\/a> <\/p>\n

Create Some Sample Members Groups<\/h4>\n

In order to add authentication capabilities to your Umbraco web site, you need to subdivide your users in member groups.<\/p>\n

    \n
  1. Navigate to the Umbraco back-end and login as the user account you created during the configuration wizard. <\/li>\n
  2. Go to Members<\/b> section and right-click on Members->Members Groups<\/b> node and select Create<\/b>. <\/li>\n
  3. Enter the Name<\/b> of the member group and then click on Create<\/b> button. For this tutorial we will need the \u201cPower Members\u201d group.\n

    \"33698430-31ef-4fb1-a5b4-98e6f8f3f0b1\"<\/a><\/p>\n

    Figure 22<\/b> – Create Member Group popup dialog<\/i><\/p>\n<\/li>\n

  4. Repeat the process and create a new member group called \u201cCommon Members\u201d. In this tutorial we will assign \u201cCommon Members\u201d to everybody. \u201cPower Members\u201d will be reserved to those members which need access to restricted pages. <\/li>\n<\/ol>\n

    <\/a><\/a><\/a><\/a><\/a><\/a><\/a> <\/p>\n

    Create Login and Error Pages <\/h4>\n

    In order to enable members to sign in using social providers, you need to add to your web site a login page that will display the appropriate choices, that is to say the list of social providers you selected when you set up the ACS Extensions. Thanks to the macro provided by the extensions, this task is very straightforward.<\/p>\n

      \n
    1. From the Content<\/b> section of the management UI, click on the \u201cSimple Web Site\u201d (or other \u201cHomepage\u201d) node at the top of the Content<\/b> tree. <\/li>\n
    2. Right-click on the Homepage node and select Create<\/b> to add a new page in your web site. <\/li>\n
    3. Write \u201cLogin\u201d in the Name field and click on Create<\/b> button.\n

      \"06e7bf11-6cbb-4b71-b83b-ae178923d21f\"<\/a><\/p>\n

      Figure 23<\/b> – Create Content popup dialog<\/i><\/p>\n<\/li>\n

    4. Go to the right panel to edit<\/b> the page. <\/li>\n
    5. In the Content<\/b> tab add a welcome sentence (e.g. \u201cWelcome back! Please sign in with the provider you used for registering among the ones below\u201d) <\/li>\n
    6. Click on Insert Macro<\/b> button from toolbar.\n

      \"9fe4895e-dce8-48c2-9455-3ceeb2384d9a\"<\/a><\/p>\n

      Figure 24<\/b> – Insert Macro button<\/i><\/p>\n<\/li>\n

    7. Select the acsExtensions.loginMacro<\/b>. That macro contains the necessary logic for rendering links to all the social providers (and other identity providers, more about that later), so that the user can click on the provider of choice and be redirected to authenticate there. acsExtensions.LoginMacro<\/b> provides username and password fields as well, in case you want to support the traditional Umbraco member management side by side with the new federated authentication features.\n

      \"47f9d404-3c42-4c2e-a1d2-090558fb0f12\"<\/a><\/p>\n

      Figure 25<\/b> – Insert macro popup dialog<\/i><\/p>\n<\/li>\n

    8. Go to the properties tab and check Hide in navigation<\/b>, to prevent the page from appearing in the navigation bar. <\/li>\n
    9. Click on the Save<\/b>and<\/b>Publish<\/b> button.\n

      \"5ff7968a-9391-4732-9d88-0975d085dbd4\"<\/a><\/p>\n

      Figure 26<\/b> – Login Page Created<\/i><\/p>\n<\/li>\n

    10. Now that you have a login page, you need an error page to display in case something goes wrong. Right-click on the Homepage node and select Create<\/b> once again. <\/li>\n
    11. Enter \u201cUnauthorized\u201d in the Name<\/b> field and click on Create<\/b>. <\/li>\n
    12. Go to the right panel to edit<\/b> the page. <\/li>\n
    13. In the Content<\/b> tab add a suitable error message (e.g. \u201cYou are not authorized to access the page you requested.\u201d) <\/li>\n
    14. Go to the properties tab and check Hide in navigation<\/b>. <\/li>\n
    15. Click on the Save<\/b>and<\/b>Publish<\/b> button.\n

      You now have all the necessary assets to authenticate members: the next step is to wire them up to the content you want to protect.<\/p>\n<\/li>\n<\/ol>\n

      <\/a><\/a> <\/p>\n

      Restrict Access to Content<\/h4>\n

      Umbraco supports role-based authorization as the access control method for its content pages. When you elect to use role-based security with a given page, Umbraco will ask you to specify one login and one error page. The ACS Extensions snap in that mechanism by using a login page containing its macro, just like the page you created in the former task. In the steps below we will restrict access to one page in order to demonstrate the process.<\/p>\n

        \n
      1. From the Content<\/b> section right-click on the area (or page) that you want to secure and select Public Access<\/b>. In this tutorial we are protecting the page \u201cGo Further\u201d.\n

        \"7ddff6b6-4af9-461d-a892-139b0ab1e29a\"<\/a><\/p>\n

        Figure 27<\/b> – Public access menu item<\/i><\/p>\n<\/li>\n

      2. Choose the Role based protection<\/b> option and click on Select<\/b> button.\n

        \"489c2c18-014d-4cab-87cc-06515c0d5f51\"<\/a><\/p>\n

        Figure 28<\/b> – Public access popup dialog | Choose how to restrict access to this page <\/i><\/p>\n<\/li>\n

      3. You\u2019ll be presented with a dialog which allow you to choose which members group should have access to this page. Select the Power members<\/b> and use the right arrow button to move it to the list on the right. <\/li>\n
      4. In the Login Page<\/b> area click Choose\u2026<\/b> to specify the page that Umbraco will display in case one unauthenticated user attempts to access the specified page. Pick the Login page you created earlier.\n

        \"24dc3124-142d-4cb4-9fda-92aa4d88ec15\"<\/a><\/p>\n

        Figure 29<\/b> – Public access popup dialog | Role based protection<\/i><\/p>\n<\/li>\n

      5. Repeat the process Error Page area. This time, pick the Unauthorized page created earlier.\n

        \"6df61418-4fbb-443c-a8b1-7818260bb417\"<\/a><\/p>\n

        Figure 30<\/b> – The end result in the public access popup dialog | Role based protection<\/i><\/p>\n<\/li>\n

      6. Click Update<\/b> and close the dialog <\/li>\n
      7. At this point we are ready to test the sign-in page. Navigate to your Umbraco web site\n

        \"b8b21e2e-1690-4d14-8877-51b4a91519c2\"<\/a><\/p>\n

        Figure 31<\/b> – The Umbraco web site home page<\/i><\/p>\n<\/li>\n

      8. Click on Go further<\/b> in the navigation bar. You will be redirected to the login page, as shown below. The list of the social providers is automatically obtained from ACS; the username and password fields are provided for compatibility with the native Umbraco membership management system\n

        \"fe68d691-e998-4d7b-865f-b75b09ae689e\"<\/a><\/p>\n

        Figure 32<\/b> – The login page<\/i><\/p>\n

        The login mechanism works, but at this point you don\u2019t have any registered members yet. In the next task you will create the activation page that invited members will use for signing up to your Umbraco instance.<\/p>\n<\/li>\n<\/ol>\n

        <\/a><\/a><\/a> <\/p>\n

        Create Activation Pages for Signing Up Social Members<\/h4>\n

        In order to register new members from social providers, you need to create some pages that will allow them to sign up to your web site using their account of choice. In a later task you will learn how to invite users; in the steps below you will see how to build the assets that will support the member activation experience.<\/p>\n

        The infrastructure is pretty simple: you need one Activation page, which constitutes the landing page for new members who have been just invited to join the site; and one Signup page, which they will use to associate their account from their social provider of choice with the account on your web site.<\/p>\n

          \n
        1. Using the procedure you have learned in the former tasks, add a new page in the content tree and call it Sign Up<\/b>. <\/li>\n
        2. Go to the right panel to edit<\/b> the page. <\/li>\n
        3. In the Content<\/b> tab add a sentence which will clarify the purpose of the page (e.g. \u201cPlease choose from the list below which social provider account you want to use for registering with this web site\u201d) <\/li>\n
        4. Click on Insert Macro<\/b> button from toolbar. <\/li>\n
        5. Select the acsExtensions.federatedloginMacro<\/b>. This macro behaves in the same way as the acsExtension.loginMacro<\/b> you used when creating the sign in page, with the only difference that the username and password UI elements are omitted: in order to sign up with a social provider account, those elements would not be needed.\n

          \"8fc20176-3c85-4e7b-9597-1c5e5d67c6a4\"<\/a><\/p>\n

          Figure 33<\/b> – Insert the federated login macro to list all configured social providers login links<\/i><\/p>\n<\/li>\n

        6. Go to the properties tab and check Hide in navigation<\/b>, to avoid the page from appearing in the navigation bar. <\/li>\n
        7. Click on the Save<\/b>and<\/b>Publish<\/b> button. <\/li>\n
        8. The Sign Up page will be used to secure the invitations landing page. Create a new page and call it activation<\/b>.\n

          \"note\"<\/a>Note:<\/em><\/p>\n

          The default name and path for the activation page is \u201c~\/activation\u201d<\/b>. If you keep all the defaults it is important that you call the page \u201cactivation\u201d, or the invitation mechanism will fail (see the next task).
          If you want to change the page name you use here to toehr than \u201cactivation\u201d, you need to update the web.config file of your Umbraco web site (appSettings -> ActivationPage).<\/em><\/p>\n<\/li>\n

        9. Go to the right panel to edit<\/b> the page. <\/li>\n
        10. In the Content<\/b> tab write an activation confirmation text like: \u201cYour account was activated successfully!\u201d<\/i>\n

          \"0f2f2870-1566-469e-a8e7-58641e9df6b6\"<\/a><\/p>\n

          Figure 34<\/b> – Edit activation page<\/i><\/p>\n<\/li>\n

        11. Go to the properties tab and check Hide in navigation<\/b>, to avoid the page from appearing in the navigation bar. <\/li>\n
        12. Click on the Save<\/b>and<\/b>Publish<\/b> button. <\/li>\n
        13. Using the procedure you\u2019ve learned in the Restrict Access to Content task, set the public access for the activation<\/b> page to Role based protection. Assing Common Members<\/b> as the member group authorized to see the page, set the Sign Up<\/b> page as the login page and the Unauthorized<\/b> page as the Error page.\n

          \"3d3ad8ae-f5a6-44e5-b9cc-ba0a623adcce\"<\/a><\/p>\n

          Figure 35<\/b> – Permissions for the activation page<\/i><\/p>\n<\/li>\n

        14. Click on Save<\/b> or Publish<\/b> button.\n

          At this point you have everything you need to start inviting members from social providers.<\/p>\n<\/li>\n<\/ol>\n

          <\/a><\/a> <\/p>\n

          Add and Manage Social Members<\/h4>\n

          With the ACS Extensions<\/b> you can add members directly from social providers such as Facebook, Windows Live ID, Google and Yahoo. The sign in and sign up pages you created in the two former steps provide the user experience elements to support the registration and authentication flow. In this task you will learn how to use the administrative features of the ACS Extensions to invite one new member. You will discover that the process is practically the same of creating traditional members, minus the pain of managing credentials.<\/p>\n

            \n
          1. Go to Members<\/b> section and right-click on Members->Members<\/b> node and select Create<\/b>.\n

            \"cf183863-a85b-4a1c-b09a-abac13340083\"<\/a><\/p>\n

            Figure 36<\/b> – Create Member<\/i><\/p>\n<\/li>\n

          2. Choose the Social Member<\/b> type, a special type added by the ACS Extensions. Complete the login name and the email fields and click on Create<\/b> button. Make sure to use an working, actual email address as the member will need access to it in order to sign up.\n

            \"1f721859-7ec0-42fd-85be-83cee4da6386\"<\/a><\/p>\n

            Figure 37<\/b> – The Create Member popup dialog<\/i><\/p>\n

            \"note[1]\"<\/a>Note:<\/em><\/p>\n

            Note<\/b>: As soon as you hit the Create button, the ACS Extensions create one invitation mail and send it to the user (using the SMTP you configured in the setup). That invitation contains a specially crafted activation link, which the member can use to associate his social account of choice with your web site using the activation assets you created in the former step.
            If you want to modify the template of the invitation email, you can do when creating a member from within the Create Member Dialog.
            The newly created member has some extra properties in respect to the default Umbraco member: one flag reporting if the invitation was sent, another if the account has been activated (false at the beginning, it flips when the user successfully signs up) and from which identity provider he is coming from (gets a value at activation time, according to the member\u2019s choice).<\/em><\/p>\n<\/li>\n

          3. In the right panel you can assign the newly created member to the web site\u2019s member groups. For the purposes of this tutorial, add the member to the Common Members<\/b> group.\n

            \"bf576385-6166-403c-abae-f768ea959cbf\"<\/a><\/p>\n

            Figure 38<\/b> – Edit Member panel <\/i><\/p>\n<\/li>\n

          4. Save the changes. <\/li>\n<\/ol>\n

            Let\u2019s step for a moment in the shoes of the new member and see how the invitation and sign up experience looks like.<\/p>\n

            The flow begins when the prospect member receives the invitation mail, as shown below.<\/p>\n

            <\/a><\/p>\n

            \"4cd1f742-5aec-4bcc-93ee-132db2617fee\"<\/a><\/p>\n

            Figure 39<\/b> – The default invitation mail <\/i><\/p>\n

            As mentioned above, the invitation email template can be configured to fit your preferences.<\/p>\n

            The URL has been constructed to trigger the activation process; the ticketnumber<\/b> parameter is used for associating the member defined in Umbraco with this specific email verification transaction. <\/p>\n

            Following the link, the prospect member will land on the activation page, which in turn will redirect to the Sign Up page.<\/p>\n

            Figure 40<\/b> – The Sign UpPage<\/i><\/p>\n

            There the user can select the Identity Provider he wants to use for signing in the web site. That account will be mapped to the Social Member created in Umbraco, with all its properties (including the assigned roles). For the purpose of this tutorial, let\u2019s assume that the use picks Windows Live ID and successfully authenticates.<\/p>\n

            \"cbbebbaf-84a8-4a7d-acce-d2ac59712cf7\"<\/a><\/p>\n

            Figure 41<\/b> – Activation Completed<\/i><\/p>\n

            As a result, Umbraco can finally serve the activation page.<\/p>\n

            Now, you may remember from the earlier steps that the current member has been assigned to the Common Members group; that\u2019s not enough for accessing the Go further<\/b> page, which you configure to be visible only to Power Members<\/b>. If you click on Go further at this point, you will get redirected to the error page.<\/p>\n

            \"b8d27ba5-094a-45f5-8fa9-e1965264e4a9\"<\/a><\/p>\n

            Figure 42<\/b> – Unauthorized <\/i><\/p>\n

              \n
            1. Let\u2019s change the member groups settings for the member so that he can access the Go further page. Go back to the Member details in the backend and refresh the page. Notice that the Is Activated<\/b> and Identity Provider<\/b> fields have been updated.\n

              \"c4d23abf-1fdf-4f65-9234-c19ef0e62c98\"<\/a><\/p>\n

              Figure 43<\/b> – Updated Member Details<\/i><\/p>\n<\/li>\n

            2. Add the user to the Power Members<\/b> group, Save the changes and hit F5: now access to the restricted page will be granted.\n

              \"9a1cc911-468f-44dd-b544-2dd3007271a8\"<\/a><\/p>\n

              Figure 44<\/b> – Access Granted.<\/i><\/p>\n<\/li>\n<\/ol>\n

              There you have it: your Umbraco web site is now integrated with Windows Live ID, Facebook, Google, Yahoo and any other social provider the Access Control Service will support in the future! It takes much longer to explain how to do it than to do it: the average time for walking through this tutorial is consistently under the 20 minutes.<\/p>\n

              <\/div>\n","protected":false},"excerpt":{"rendered":"

              Welcome to the second installment of the series on the ACS Extensions for Umbraco, part of the big ACS launch wave! This time I am going to assume that you succesfully installed the Extensions on your Umbraco instance, and you want to start accepting members from social & web identity providers. You\u2019ll see…<\/p>\n","protected":false},"author":1,"featured_media":1343,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"footnotes":""},"categories":[7,8,38,9,43],"tags":[],"class_list":["post-310","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-access-control-service","category-acs","category-appfabric","category-identity","category-umbraco"],"_links":{"self":[{"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/posts\/310","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/comments?post=310"}],"version-history":[{"count":0,"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/posts\/310\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/media\/1343"}],"wp:attachment":[{"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/media?parent=310"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/categories?post=310"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/tags?post=310"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}