<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Authorization on PlumePHP</title><link>https://plumephp.com/tags/authorization/</link><description>Recent content in Authorization on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Sat, 29 Nov 2025 10:00:00 +0800</lastBuildDate><atom:link href="https://plumephp.com/tags/authorization/index.xml" rel="self" type="application/rss+xml"/><item><title>后端安全架构：OAuth2.1、JWT认证与零信任网络实战指南</title><link>https://plumephp.com/backend-security-authentication-authorization/</link><pubDate>Sat, 29 Nov 2025 10:00:00 +0800</pubDate><guid>https://plumephp.com/backend-security-authentication-authorization/</guid><description>&lt;blockquote&gt;
&lt;p&gt;安全不是事后补丁，而是架构设计时的第一约束。&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;后端系统的安全性，往往在&amp;quot;出事后&amp;quot;才被重视。但真正成熟的安全体系，必须从设计阶段就开始构建——&lt;strong&gt;认证、授权、传输加密、密钥管理、审计合规&lt;/strong&gt;，每一层都不能缺。&lt;/p&gt;</description></item></channel></rss>