DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
View Events Video Library
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

Integrating PostgreSQL Databases with ANF: Join this workshop to learn how to create a PostgreSQL server using Instaclustr’s managed service

Mobile Database Essentials: Assess data needs, storage requirements, and more when leveraging databases for cloud and edge applications.

Monitoring and Observability for LLMs: Datadog and Google Cloud discuss how to achieve optimal AI model performance.

Automated Testing: The latest on architecture, TDD, and the benefits of AI and low-code tools.

Related

  • Using OKTA as Client Provider in Mulesoft
  • OWASP TOP 10 API Security Part 2 (Broken Object Level Authorization)
  • Configuring SSO Using WSO2 Identity Server
  • 10 Ways To Keep Your Java Application Safe and Secure

Trending

  • The API-Centric Revolution: Decoding Data Integration in the Age of Microservices and Cloud Computing
  • Distributed Tracing Best Practices
  • Build Quicker With Zipper: Building a Ping Pong Ranking App Using TypeScript Functions
  • How To Validate Archives and Identify Invalid Documents in Java
  1. DZone
  2. Software Design and Architecture
  3. Security
  4. Modern Authentication and Authorization: A Brief Introduction

Modern Authentication and Authorization: A Brief Introduction

Developers are plagued by more and more problems, and two of the most prominent are authorization and authentication. Here's a brief intro to authentication and authorization: what they are, biggest challenges, and current standards.

Christopher Lamb user avatar by
Christopher Lamb
·
Feb. 11, 16 · Analysis
Like (26)
Save
Tweet
Share
16.89K Views

Join the DZone community and get the full member experience.

Join For Free

One of the problems developers face today is authentication and authorization (hereafter referred to as AuthN and AuthZ, respectively, so we can be cool like that). Engineers are always called on to authenticate or authorize access to applications, systems, or apps. And if they’re not, they should be. Constantly.

We tend to think of AuthN|Z (another neat abbreviation you’ll see now that you’re in the know acronymically) as things only people do. Really, how presumptuous! How dare we deny the inconvenience of having to authenticate and authorize from computer systems or software components! Very lame of us.

The fact is that AuthN|Z should be something we do when people access our systems as well as when other systems access our systems. Sometimes we should authenticate internal system components too. And when we do, like anything else, it’s always best to use standards first before resigning yourself to writing your own AuthN|Z schemes. It’s really easy to mess these kinds of systems up. They’re complicated, they use tons of crypto, and they’re really, really, hard to get right the first time.

There're three major standards in play today in this area. These are OAuth, SAML, and Open ID. Google, Amazon, Facebook, and just about any other major internet application provider supports at least one of these standards and most support all of them. There’s a final authentication technology out there today, CAS (for Central Authentication Service), and we’ll discuss that too.

These are usually used to authenticate people to use various cloud application offerings rather than authenticating or authorizing software components or subsystems. We’ll review these three standards, and look closely at how they work to authenticate users and how they could be used to authenticate subsystems. We’ll go over the threats to these standards too. Before we get started with all that detail, let’s look at what these standards are, what they were designed for, and where they started.

SAML. OASIS started work on SAML in 2001. In 2002, they released the first specification as an OASIS standard. Currently on version 2.0, SAML addresses web browser single sign-on (SSO). The common implementations use XML data passed between various subsystems to authenticate users. OpenID addresses the same problem, and experience has shown it to be a bit more scalable.

OAuth. Blaine Cook started working on OAuth in 2006 while working on OpenID at Twitter. At the time, they were looking for a way to integrate Ma.gnolia widgets, and after a search for alternatives decided to pursue their own solution as nothing else seemed to fit their needs. Fast forward to today, where OAuth and the newer OAuth 2.0 are common protocols used to authenticate and authorize users into third-party web-based applications. Designed for HTTP, OAuth uses access tokens as the basis for user authentication, a common pattern.

OpenID. Brad Fitzpatrick started work on OpenID in 2005 while at Six Apart. By 2008, it had been supported by Sun Microsystems and Yahoo! for authentication and authorization. Today, the latest version of OpenID, OpenID Connect, builds on OAuth 2.0 as an authentication protocol. It supports signing and strong encryption.

CAS. CAS is another SSO protocol for web applications. It was initially designed and developed by Shawn Bayern at Yale. By 2004, it was a project in the Java in Administration Special Interest Group, which today manages its maintenance and ongoing development. Frequently called Jasig CAS, it’s in its third version.

With a strong understanding of these four standards and associated implementations, you’ll never need to develop your own authentication or authorization protocol, and you’ll have the information to stop anybody else who might be thinking about it, doing them a favor.

As you can tell, this is the start of what promises to be an interminably long series on authentication and authorization standards and technology. This rabbit hole’s deep, but at the end you’ll have a strong understanding of why, when, and how to use these technologies to secure your systems. Stay tuned!

authentication security application OpenID IT Protocol (object-oriented programming) Central Authentication Service Implementation

Opinions expressed by DZone contributors are their own.

Related

  • Using OKTA as Client Provider in Mulesoft
  • OWASP TOP 10 API Security Part 2 (Broken Object Level Authorization)
  • Configuring SSO Using WSO2 Identity Server
  • 10 Ways To Keep Your Java Application Safe and Secure

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 100
  • Nashville, TN 37211
  • support@dzone.com

Let's be friends: