Follow

Higher Logic Site Configuration (Cobalt Staff)

Higher Logic is a CMS that offers a community site, similar to a web forum, for users of that community. This CMS uses our API to read data from D365 and can include the use of our widgetized Web Elements.

Once you've determined whether the association requesting a Higher Logic configuration will be using the Widgetized Web Elements, you can take the following steps:

Before beginning: If the association is going to use the widgetized Web Elements, confirm the existence of or create a widget site and a DNS entry for that site. For steps on how to do that, see this article.

1) Create a Higher Logic Service Configuration*. For instructions on how to do this, refer to this article.

2) Fill out the the Higher Logic Tenant form, using the format below and send to Higher Logic/the organization. If you haven't been provided with the form by the org or the Higher Logic representative, request that as well as the Community URL

Membership Web Services URL
https://[ORG API URL]/Social/HigherLogic/RefreshService.asmx
Membership Web Services Security Key
Encrypted Value from Security Key Service Config Property
Activity Sync Services URL (if licensed)
https://[ORG API URL]/Social/HigherLogic/ActivityService.asmx
Activity Sync Services Security Key (if licensed)
N/A
Sign On URL
https://[ORG PORTAL URL]/Authentication/HigherLogicLogin.ashx?ReturnUrl=http%3A%2F%2[COMMUNITY URL]/%2Fhome
Sign Off URL
http://[COMMUNITY URL]/HigherLogic/security/logout.aspx?CrossSiteLogout=1&ReturnURL=https%3A%2F%2F[ORG PORTAL URL]%2FLogout.aspx%3FReturnUrl%3Dhttp%253A%252F%252F[COMMUNITY URL]%252F

If the org is using widgetized Web Elements, also provide the Web Element Designer code block for the Cobalt Portal login. For instructions on accessing and using the Web Element Designer, refer to this article.

3) Confirm that the Organization's portal web.config file contains the following lines of code. If it doesn't add, them:

  1. Under <system.webServer> 

<handlers> 

<add name="HigherLogicLogin" verb="*" path="/Authentication/HigherLogicLogin.ashx" type="Cobalt.Applications.Crm.Portal.Authentication.UserIdAuthenticationHandler" /> 
 <add name="HigherLogicLogout" verb="*" path="/Authentication/HigherLogicLogout.ashx" type="Cobalt.Applications.Crm.Portal.Authentication.UserIdAuthenticationHandler" /> 

2. Under </location> 

<location path="Authentication/HigherLogicLogin.ashx"> 
    <system.web> 
      <authorization> 
        <allow roles="Active Contacts"/> 
        <deny users="*"/> 
      </authorization> 
    </system.web> 
  </location> 

4) To test that the configuration is set up correctly, remote to the Org's portal server and do the following:

  1. Open Internet Explorer 
  2. Navigate to the following URL: http://[ORG API URL]/social/higherlogic/refreshservice.asmx (i.e. http://api.cshema.org/social/higherlogic/refreshservice.asmx)
  3. You should be taken to the Refresh Service; this is what we can use on our end to test that data is being pulled correctly 
  4. The most important services to test and verify 
    1. GetCommunityGroups 
      • This will pull Active CMS User Roles where Type = Website Group 
      • This will allow you to easily grab the groupkey for the individual groups 
    2. GetCommunityGroupMembers 
      • This will pull all members of the selected Community Group 
    3. GetSecurityGroups 
      • This will pull Active CMS User Roles Where Type = Website Role 
      • This will allow you to easily grab the groupkey for the individual groups 
    4. GetSecurityGroupmembers 
      • This will pull all members of the selected Security Group 
    5. GetEvents 
      • This will pull the meetings/classes that will be pushed to higher logic 
      • This will allow you to easily grab the eventkey for the individual meetings 
    6. GetEventInfo 
      • This will pull the information sent to higher logic about the selected meeting 
    7. GetEventRegistrants 
      • This will pull the meeting registrations that will be pushed to higher logic 
    8. GetMemberInfo 
      • This will pull the information sent to higher logic about an individual member 
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk