Habr•November 20, 2026•🇷🇺Translated from Russian

Integrating OAuth 2.0 with PDP Architectures Without Modifying Core Authorization Engines

The article examines practical ways to combine OAuth 2.0 delegated access mechanisms with traditional PEP/PDP authorization architectures without altering the core PDP implementation.

OAuth 2.0 handles how applications obtain delegated access through access tokens that carry scopes, yet it does not define how resource servers should evaluate those tokens against policy-based authorization systems. Conversely, PEP/PDP engines evaluate requests according to configured policies using calls such as PDP.Check(subject, operation, resource, context) but typically lack native understanding of OAuth clients, scopes, and delegation.

The proposed solution introduces an OAuth-aware PDP that acts as an intelligent proxy. It validates access tokens, interprets their contents, and converts OAuth grants into one or more standard PDP checks. Two classes of scenarios are distinguished: tokens that do not contain scopes (grants stored in the policy system) and tokens that embed scopes directly.

Expressing OAuth Scopes as Authorization Policies

Scopes are modeled as combinations of operations, resources, and optional context filters. An op-scope represents a named set of operations (similar to a role in cloud IAM). A res-scope adds a resource filter, allowing clients to be limited to specific resource boundaries. Richer context parameters can further restrict actions such as money transfers within a budget.

Three Authorization Use Cases

UC.1 stores user-consented grants as policies attached to a synthetic subject u+c (user plus client). The token carries only sub and client_id; the OAuth-aware PDP reconstructs the synthetic subject and performs two checks: one for the grant and one for the real subject.

UC.2 extends the model with tenant-level administrative grants using another synthetic subject t+c. The authorization decision becomes a logical OR between tenant and user grants before checking the subject’s actual permissions.

UC.3 places scopes inside the token. When the PDP supports ephemeral policies (for example, OpenFGA Contextual Tuples), the OAuth-aware PDP creates a temporary synthetic subject and policy for that request only. If ephemeral policies are unavailable, the OAuth-aware PDP must emulate the logic, which is noted as an architectural compromise.

The design recommends returning distinct denial reasons so the PEP can differentiate between insufficient OAuth grants and insufficient subject permissions. An OAuth-aware PAP is suggested to limit the Authorization Server’s ability to create policies only for delegation subjects. The overall architecture supports the AuthZEN standard interface and works with both stored and token-carried grants.

Related articles

Habr•Policy & Regulation

Russian Businesses Face 50-Ruble Fee per MVD Query for Passport and Residence Checks

The Russian government has backed a proposal requiring businesses to pay 50 rubles for each completed session querying Ministry of Internal Affairs databases. The fee covers checks on Russian passport validity, residence registration, residence permits, and foreign citizen migration records. Projected annual budget revenue reaches 120 billion rubles. Companies must still perform client identification under Federal Law 115-FZ and the Law on Communications, with fines up to 0.1 percent of own funds for banks or 500,000 rubles for telecom operators. Smart Engines highlights its Sherlock anti-fraud platform as a local alternative that detects over 600 forgery indicators, including deepfakes and NFC chip tampering, without repeated paid queries. The company cites a June 2026 legal opinion from the National Council of Financial Markets confirming that such tools can satisfy compliance requirements.

Habr•Policy & Regulation

Russian Court Convicts Former IT Director for Unauthorized Access to Huawei Storage After Moving Servers Offsite

A former IT director at an Omsk manufacturing plant was found guilty under Part 3 of Article 272 of the Russian Criminal Code for blocking and modifying data on a Huawei Dorado 3000 v6 storage array after relocating the entire server infrastructure to a privately rented office. The court relied heavily on detailed logs from the Huawei system that recorded the exact sequence of disk removals, reinsertions in altered order, and the shutdown command, even after the administrator attempted to delete portions of the event journal. The incident occurred on the same day new management took over, causing immediate loss of access to corporate email, 1C systems, design software, and shared network resources. Despite the defendant's claims that he was preparing the array for cloud backup and that a script had frozen, the court rejected the explanation based on audit concealment, lack of notification to owners, and post-incident behavior. The ruling imposed a 400,000-ruble fine and a one-year ban on computer-information work involving protected secrets, while leaving a civil claim for 18.27 million rubles in recovery costs for separate proceedings. The case highlights how storage-array logs can serve as decisive forensic evidence and underscores the legal risks of retaining physical or logical access after employment ends.

AntiMalware•Policy & Regulation

False 50,000 Ruble Fine Claims Circulate About Russia's Unified Bank Card Registry

Social media posts falsely warn Russian citizens of a 50,000 ruble fine for failing to submit personal bank card data to a new unified registry. The claims have been identified as fabricated, with the project "Lapsa Media" noting that the accompanying images were likely generated by AI and contain multiple errors and typos. In reality, individual citizens are not required to take any action, as banks themselves will transmit the necessary information. The Bank of Russia has confirmed that banks must upload card numbers, card types, and owners' INN identifiers to the system operated by NSPK no later than September 1, 2027. Starting on that date, banks will begin enforcing a limit of 20 cards per client to hinder mass issuance of cards for fraudulent purposes. Previously issued cards exceeding this limit will remain valid and will not be forcibly closed.

Habr•Policy & Regulation

Webiomed AI Platform Processes Millions of Medical Records Daily on Certified RED OS Infrastructure

The Russian Webiomed platform now serves more than 4,000 medical organizations across 55 regions and supports over 300,000 physicians. Its algorithms analyze up to one million electronic health records every day, generating recommendations that physicians must review and approve. The entire server infrastructure runs on RED OS, which holds FSTEC Russia certification for use in critical information infrastructure. Legal responsibility for any harm remains with the medical organization and, in some cases, the individual physician, even when AI suggestions are involved. The article highlights risks such as incomplete data, synchronization errors that could revoke physician access via RED ADM directory services, and the need for selective recovery tools like Granulex Recovery. Joint testing by MDIS and RED SOFT confirmed that Granulex Recovery can restore specific objects and attributes without stopping the directory service. Questions remain about where liability falls when errors occur at the intersection of the algorithm, medical systems, and underlying IT infrastructure.