Title: Datawiza Proxy Auth Plugin – SSO Author: Datawiza Team Published: 2020 年 12 月 19 日 Last modified: 2021 年 10 月 25 日 --- 搜尋外掛 這個外掛**並未在最新的 3 個 WordPress 主要版本上進行測試**。開發者可能不再對這個 外掛進行維護或提供技術支援，並可能會與更新版本的 WordPress 產生使用上的相容性問題。 ![](https://ps.w.org/reverse-proxy-auth-widget/assets/icon.svg?rev=2443145) # Datawiza Proxy Auth Plugin – SSO 由 [Datawiza Team](https://profiles.wordpress.org/fyuck1991/) 開發 [下載](https://downloads.wordpress.org/plugin/reverse-proxy-auth-widget.1.1.2.zip) * [詳細資料](https://tw.wordpress.org/plugins/reverse-proxy-auth-widget/#description) * [使用者評論](https://tw.wordpress.org/plugins/reverse-proxy-auth-widget/#reviews) * [安裝方式](https://tw.wordpress.org/plugins/reverse-proxy-auth-widget/#installation) * [開發資訊](https://tw.wordpress.org/plugins/reverse-proxy-auth-widget/#developers) [技術支援](https://wordpress.org/support/plugin/reverse-proxy-auth-widget/) ## 外掛說明 The Proxy Auth Plugin helps developers/DevOps/admins easily implement authentication and authorization for WordPress by using a [JWT (JSON Web Token)](https://en.wikipedia.org/wiki/JSON_Web_Token) provided by a reverse proxy. This could be employed to achieve SSO (OAUTH/OIDC and SAML) to a Cloud Identity Provider (e.g., Azure Active Directory, Okta, Auth0) by using an Identity-Aware Proxy, e.g., [Datawiza Access Broker](https://www.datawiza.com/) and [Google IAP](https://cloud.google.com/iap). Note that the plugin requires a reverse proxy sitting in front of the WordPress site. The reverse proxy performs authentication, and passes the user name and role in a JWT to the plugin via a HTTP header called `DW-TOKEN`. By using [Datawiza Access Broker](https://www.datawiza.com/), you get a [configuration-based](https://docs.datawiza.com/step-by-step/step1.html) [no-code solution](https://docs.datawiza.com/), following the detail instruction [here](https://docs.datawiza.com/step-by-step/step1.html). If you decide to use your own reverse proxy, please follow the instructions below. **How it works** * The plugin retrieves the user id (email) from the JWT and then checks if such a user exists. If not, the plugin creates a new user by using this email and signs him/her in. * The plugin retrieves the user role from the JWT and sets it as the user’s role in WordPress. * The plugin expects the JWT including user id and role as a HTTP header `DW-TOKEN`. For example, the payload of JWT may look like: * { “role”: “administrator”, “email”: “admin@yourwebsite.com” } **Plugin config in WordPress** In `Setting` -> `Datawiza Proxy Auth`, you need to input a private secret which is used as a Cryptography Key. Such secret is shared between the plugin and the reverse proxy which is responsible for passing the JWT to the plugin. The Signing Algorithm for the JWT is `HS256`. **!!! NOTES !!!** * **If the enabled Proxy Auth Plugin cannot retrieve the expected JWT in the HTTP header, the plugin will not work. The authentication will use the default authentication of wordpress and you will see an error banner on top of the wordpress pages.** * **MAKE SURE that clients cannot bypass the reverse proxy. This is to prevent people from sending forged malicious requests with arbitrary JWTs directly to WordPress.** * **It’s recommended that the reverse proxy in front of the WordPress site erases the incoming http request’s `DW-TOKEN` header. The `DW-TOKEN` header should be generated by the reverse proxy only.** * **If admin doesn’t assign role to the user, user’s role will be subscriber for WordPress by default.** * **If user’s role has been updated in JWT, the plugin will update the role in WordPress accordingly.** **Generate the JWT required by the plugin** If you are using openresty/lua-nginx-module, here is the code sample to generate the JWT required by the plugin: ``` jwt = require("resty.jwt") local jwt_token = jwt:sign( "jwt_secret", { header={typ="JWT", alg="HS256"}, payload={email="admin@yourwebsite.com", role="administrator"} }) ngx.req.set_header('DW-TOKEN', jwt_token) ``` The `jwt_secret` above should be the same private secret input in `Setting` -> ` Datawiza Proxy Auth`. The `role` in `payload` is optional. If it’s not specified, the default role is `subscriber`. For more details about `lua-resty-jwt`, you can visit [here](https://github.com/SkyLothar/lua-resty-jwt). ## 安裝方式 1. Activate the plugin through the “Plugins” menu in WordPress. 2. Input private secret in “Settings” -> “Datawiza Proxy Auth Plugin”. ## 使用者評論 ![](https://secure.gravatar.com/avatar/521db78664237389a812d3a33c0311012f26652834a2582cf4176218347e3c77? s=60&d=retro&r=g) ### 󠀁[A really good job.](https://wordpress.org/support/topic/a-really-good-job/)󠁿 [dblas](https://profiles.wordpress.org/dblas/) 2022 年 1 月 10 日 Hello, Good job. Works like a charm. And the JWT allows the proxy and the WP to be on separate machines without impeding security and without the need to use PKI. A few suggestions nevertheless: 1. priorizing the attributes’values coming from the directory (through the id_token) against WP own values [1]; 2. giving the possibility to fill in other profile’s attributes (firstname, lastname, social networks profiles, etc). [1] Above all the role MUST be set by the directory not by another user be it an administrator. That means there SHOULD exist a mean to override the user attributes or, at least, there exist a flag to do so. IAM is a too serious thing to be let in WP administrators’hands 🙂 db [ 閱讀全部 1 則使用者評論 ](https://wordpress.org/support/plugin/reverse-proxy-auth-widget/reviews/) ## 參與者及開發者 以下人員參與了開源軟體〈Datawiza Proxy Auth Plugin – SSO〉的開發相關工作。 參與者 * [ Datawiza Team ](https://profiles.wordpress.org/fyuck1991/) * [ Datawiza ](https://profiles.wordpress.org/datawiza/) [將〈Datawiza Proxy Auth Plugin – SSO〉外掛本地化為台灣繁體中文版](https://translate.wordpress.org/projects/wp-plugins/reverse-proxy-auth-widget) ### 對開發相關資訊感興趣？ 任何人均可[瀏覽程式碼](https://plugins.trac.wordpress.org/browser/reverse-proxy-auth-widget/)、 查看 [SVN 存放庫](https://plugins.svn.wordpress.org/reverse-proxy-auth-widget/)， 或透過 [RSS](https://plugins.trac.wordpress.org/log/reverse-proxy-auth-widget/?limit=100&mode=stop_on_copy&format=rss) 訂閱[開發記錄](https://plugins.trac.wordpress.org/log/reverse-proxy-auth-widget/)。 ## 變更記錄 #### 1.1.2 * Keep the user’s role in WordPress in sync with the role value in JWT. * Add close button to notification bar. * Add invalid jwt error message. #### 1.1.1 * Retrieves user info from encrypted DW-TOKEN instead of X-User. #### 1.1.0 * Initial release. ## 中繼資料 * 版本 **1.1.2** * 最後更新 **5 年前** * 啟用安裝數 **少於 10 次** * WordPress 版本需求 ** 3.0.1 或更新版本 ** * 已測試相容的 WordPress 版本 **5.8.13** * PHP 版本需求 ** 5.6 或更新版本 ** * 語言 * [English (US)](https://wordpress.org/plugins/reverse-proxy-auth-widget/) * 標籤: * [auth](https://tw.wordpress.org/plugins/tags/auth/)[oidc](https://tw.wordpress.org/plugins/tags/oidc/) [proxy](https://tw.wordpress.org/plugins/tags/proxy/)[SAML](https://tw.wordpress.org/plugins/tags/saml/) [sso](https://tw.wordpress.org/plugins/tags/sso/) * [進階檢視](https://tw.wordpress.org/plugins/reverse-proxy-auth-widget/advanced/) ## 評分 4 星，滿分為 5 星 * [ 0 個 5 星使用者評論 ](https://wordpress.org/support/plugin/reverse-proxy-auth-widget/reviews/?filter=5) * [ 1 個 4 星使用者評論 ](https://wordpress.org/support/plugin/reverse-proxy-auth-widget/reviews/?filter=4) * [ 0 個 3 星使用者評論 ](https://wordpress.org/support/plugin/reverse-proxy-auth-widget/reviews/?filter=3) * [ 0 個 2 星使用者評論 ](https://wordpress.org/support/plugin/reverse-proxy-auth-widget/reviews/?filter=2) * [ 0 個 1 星使用者評論 ](https://wordpress.org/support/plugin/reverse-proxy-auth-widget/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/reverse-proxy-auth-widget/reviews/#new-post) [查看全部使用者評論](https://wordpress.org/support/plugin/reverse-proxy-auth-widget/reviews/) ## 參與者 * [ Datawiza Team ](https://profiles.wordpress.org/fyuck1991/) * [ Datawiza ](https://profiles.wordpress.org/datawiza/) ## 技術支援 使用者可在技術支援論壇提出意見反應或使用問題。 [檢視技術支援論壇](https://wordpress.org/support/plugin/reverse-proxy-auth-widget/)