OAuth2 in 5G Core

OAuth2 is the IETF authorisation framework that 5G adopts inside the Service-Based Architecture for fine-grained, short-lived authorisation between Network Functions. The NRF acts as the OAuth2 authorisation server, issuing JWT access tokens scoped to specific NF types and operations. Each producer NF validates the token signature and claims before serving the request. Combined with mutual TLS for transport authentication, OAuth2 enforces least-privilege between NFs and is a prerequisite for any production 5G core deployment.

Categories: Radio Access NetworkCore NetworkSecurity Controls

OAuth2 in 5G Core in context

The radio access network is where mobile devices attach to the operator's infrastructure. Attacks in this layer include IMSI catching, rogue base stations and downgrade attacks; defenses rest on mutual authentication, integrity-protected signaling and Open RAN supply-chain hygiene.

The mobile core carries subscriber sessions, mobility and policy. In 4G it is the EPC (MME, HSS, S/PGW); in 5G it is the Service-Based Architecture with AMF, SMF, UPF, AUSF, UDM and the NRF.

To place OAuth2 in 5G Core in the wider telecom-security picture, review HTTP, Inter-Network Function Authentication, NRF Poisoning, SMPP, 5G SBA and Authorization: each entry cross-references back to this page so you can walk the topic in either direction.

Related terms

Related topic hubs

  • 5G Security 5G SBA, SEPP, SUCI, 5G-AKA, N32 and service-based interface security.
  • SEPP Security N32-c/N32-f, PRINS, JWE and OAuth 2.0 at the 5G roaming edge.
  • Diameter Security 4G/LTE Diameter threats across IPX/roaming and DEA defenses.
  • 5G NEF Security Network Exposure Function security in the 5G core.

More from the TelcoSec Glossary

Browse the full TelcoSec Glossary, the Ultimate Guide to Mobile Network Security, or the P1 Arsenal of telecom-security tools.