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 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[…]

Leverage Campus’ Security Token Service for Authentication and SSO

Many web applications provided by Campus Management have started using Custom Security Token Services (STS) for authentication. Authentication is no longer responsibility of these applications but these web apps are relying on STS to deal with authentication. Custom STS built by Campus Management are built on top of Windows Identity Foundation (WIF) and has Single Sign[…]

Skip to toolbar