Campus Management GitHub Repositories

I am happy to announce that we have created a set of community-driven GitHub repositories to help share ideas, solutions and knowledge regarding CampusNexus!  We would love for you to contribute to this community as well, so please feel free to fork a project and commit your proposed changes.  Submitting a change will write to[…]

Configure CampusNexus Web Apps for SSO with AzureAD

All of the web applications provided by CampusNexus are claims aware. In other words these applications can rely upon different identity providers supporting similar protocols. Identity providers broker trust between disparate entities by allowing the trusted exchange of arbitrary claims that contain arbitrary values. The receiving party uses these claims to make authorization decisions. Example[…]

CampusNexus Single Sign-On

CampusNexus Single Sign-On Overview Application security is a top priority for Campus Management.  As part of this, we would like to inform you that CampusNexus is now utilizing Single Sign-on (SSO) across all web apps: CampusNexus CRM Web Client CampusNexus Student Web Client CampusNexus Student Portal Forms Builder (Designer & Renderer) For the user, this[…]

CampusNexus Web APIs with OAuth 2.0 Client Credentials

CampusNexus Student has started supporting OAuth 2.0 based authorization with recent 18.2 release. This change will provide ability of calling OData endpoints and other services of CampusNexus Web via passing in a JWT (JSON Web Token) based authorization token. This blog will go over few ways of getting authorization token from Staff STS 2.0 and[…]

Convert existing claims-aware app to support Azure AD

In the past I have blogged about how you can write claims-aware applications which can rely upon custom STS (Security Token Service) provided by Campus Management. When applications are relying upon standard based authentication mechanism such as Ws-Federation, OpenID, OAuth, etc and when they are delegating authentication requirements, your applications are not only more secure but many[…]

OData new query routes being introduced into Campus Nexus Student

Today, Campus Nexus Student offers the capability to perform OData queries against almost every piece of data item in the Student database model. You can perform queries against the data stored in Campus Nexus Student by performing queries structured as shown below: http://[server]/[odata prefix]/[Entity Collection Name]?[OData query parameters] For example: http://localhost/Cmc.Nexus.Web/ds/campusnexus/AcademicAdvisors?$top=10&$select=Id,Name&$orderby=Name When we break-down the[…]

Changing Workflow Composer Database Connections

The Workflow Composer application maintains three connection strings for the database(s) that it uses. Those connection strings represent the CampusNexus Student database, the durable instancing database used for workflow persistence, and the one for workflow tracking. The CampusNexus Student database refers to the main SIS database. The database for workflow persistence captures a workflow instance’s[…]

Registration-Free COM Component Activation

In order to use a Component Object Model (COM) component in an application, the binding/activation information must be made available so that the operating system can find it when a program needs the component. Typically this is accomplished by registering the COM component, which places the activation information in the Windows registry. Registration-free COM allows[…]

Skip to toolbar