Title: Shibboleth With LDAP Authorization
Author: warren.brown
Published: <strong>2011 年 9 月 28 日</strong>
Last modified: 2018 年 5 月 2 日

---

搜尋外掛

這個外掛**並未在最新的 3 個 WordPress 主要版本上進行測試**。開發者可能不再對這個
外掛進行維護或提供技術支援，並可能會與更新版本的 WordPress 產生使用上的相容性問題。

![](https://s.w.org/plugins/geopattern-icon/ugrm.svg)

# Shibboleth With LDAP Authorization

 由 [warren.brown](https://profiles.wordpress.org/warrenbrown-1/) 開發

[下載](https://downloads.wordpress.org/plugin/ugrm.2.0.zip)

 * [詳細資料](https://tw.wordpress.org/plugins/ugrm/#description)
 * [使用者評論](https://tw.wordpress.org/plugins/ugrm/#reviews)
 *  [安裝方式](https://tw.wordpress.org/plugins/ugrm/#installation)
 * [開發資訊](https://tw.wordpress.org/plugins/ugrm/#developers)

 [技術支援](https://wordpress.org/support/plugin/ugrm/)

## 外掛說明

Since this plugin extends the Shibboleth plugin, you must first have the Shibboleth
plugin, available from https://wordpress.org/extend/plugins/shibboleth/
 installed
and activated. Otherwise, the plugin will fail to activate as the shibboleth_user_role
filter hook will not be registered.

To use this plugin, you must already have the following setup on your server:
 1.
The above Shibbleth plugin. 2. A UFAD group created for each of the WordPress roles(
administrator, editor, author, contributor, and subscriber).

## 螢幕擷圖

 * [[
 * Plugin Screenshot
 * [[
 * Plugin Config Options

## 安裝方式

 1. Install, activate, configure and test the Shibbloeth plugin. When it is working,
    procede.
 2. Create a UGRM directory in `/wp-content/plugins/` directory
 3. Extract the contents of the UGRM.tar.gz plugin archive to the `/wp-content/plugins/
    UGRM` directory
 4. Populate UgrmLdapConfig::$configuration attribute located at `/wp-content/plugins/
    UGRM/ldap-config.php`. Options are:
     a. binddn – The Distinguished Name (DN) of
    the user or service account that will query LDAP server for group membership. b.
    pw – The password for the user or service account connecting to ldap. (binddn user)
    c. basedn – The base DN for the LDAP directory. d. ldapUri – The URI of the ldap
    server.
 5. Activate the plugin through the ‘Plugins’ menu in WordPress
 6. Populate the ‘UFAD Groups to Roles’ options page under the ‘Settings’ menu in WordPress.

## 常見問題集

  It’s not working. What should I check?

Check for typos on the options page and ensure you’ve spelled your UFAD groups correctly.

    ```
    If $_SERVER['glid'] for Apache or `$_SERVER['HTTP_glid']` for IIS is not present, then complete
    ```

the correct application to have glid included in UF Shibboleth URN.

Verify that you can make a connection to the ldap server specified in ldapUri set
in the options file. You may do this by launching ldp.ext
 in Windows and inputting
the binddn and password from the options file. You could also use any of the various
ldap modules for any programming language to test.

  What if I’ve done all that and it still doesn’t work?

Contact the plugin author(s), who will respond in a vague and unspecified amount
of time.

## 使用者評論

這個外掛目前沒有任何使用者評論。

## 參與者及開發者

以下人員參與了開源軟體〈Shibboleth With LDAP Authorization〉的開發相關工作。

參與者

 *   [ warren.brown ](https://profiles.wordpress.org/warrenbrown-1/)
 *   [ taylorwilson ](https://profiles.wordpress.org/taylorwilson/)

[將〈Shibboleth With LDAP Authorization〉外掛本地化為台灣繁體中文版](https://translate.wordpress.org/projects/wp-plugins/ugrm)

### 對開發相關資訊感興趣？

任何人均可[瀏覽程式碼](https://plugins.trac.wordpress.org/browser/ugrm/)、查看 [SVN 存放庫](https://plugins.svn.wordpress.org/ugrm/)，
或透過 [RSS](https://plugins.trac.wordpress.org/log/ugrm/?limit=100&mode=stop_on_copy&format=rss)
訂閱[開發記錄](https://plugins.trac.wordpress.org/log/ugrm/)。

## 變更記錄

#### 2.0.1

 * Updates ldap.php with ternary to elimiate options index notice for logpath

#### 2.0

 * Updates UGRM.php to use UgrmLdap class from ldap.php to query UFAD LDAP server
   to get group membership by shibboleth provided `glid` apache server variable.
 * Adds ldap-config.php containing LDAP connection parameters.
 * Corrects bug in options.php where $_SERVER superglobal array keys were not quoted,
   emitting an error for undeclared constant.

#### 1.7.1

 * Corrected typo in code. Minor fix, but very large impact.

#### 1.7

 * Discovered that with multisite enabled, the server variables will sometimes present
   as prepended with REDIRCT_ when in a subsite. E.G. UFADGroupsDN will sometimes
   appear
    REDIRECT_UFADGroupsDN. The code has been extended to accomdate this. *
   As a side note, the Shibboleth plugin UGRM extends appears to have been abandoned.
   As we’ve already made code changes to enable the Shibboleth plugin to work with
   the new WordPress enabled for multisite, and we had to graft on further changes
   for the REDIRECT_ behavior, we plan to release a fork of the Shibboleth plugin.

#### 1.6

 * Fixed a glaring bug in when “Force Shibboleth return target to HTTPS” was checked
   and return target was already https the target would be munged to httpss.
 * Discovered Shibboleth on IIS prepends all Shibboleth server variables with a 
   HTTP_ prefix because the variables are populated via CGI as IIS does not support
   
   environment variables (for details, check out: https://wiki.shibboleth.net/confluence/
   display/SHIB2/NativeSPAttributeAccess). Plugin now inspects SERVER_SOFTWARE variable
   and adjusts accordingly.

#### 1.5

 * Fixed header in UGRM.php to resolve current version display on WordPress site.

#### 1.4

 * Attempting to correct WordPress SVN tagging for current

#### 1.3

 * Still working on SVN versioning

#### 1.2

 * New version number to resolve wonkyness with WordPress SVN.

#### 1.1

 * Added a configuration option for requiring HTTPS on the return target. This hooks
   into the Shibboleth provided shibboleth_seesion_initiator_url filter and ensures
   
   the return target uses HTTPS. This allows you seemless provide a Shibboleth integrated
   WordPress site where the content side is delivered via HTTP and the admin side
   is delivered VIA HTTPS. The default Shibboleth plugin behavior is to construct
   the return target using the current protocol, e.g. if you click the login link
   from HTTP, your return target would be for HTTP. UGRM now allows you to overide
   this behavior and alwasy use a HTTPS return target.

#### 1.0

 * Initial Release

## 中繼資料

 *  版本 **2.0.1**
 *  最後更新 **8 年前**
 *  啟用安裝數 **10+**
 *  WordPress 版本需求 ** 3.2.1 或更新版本 **
 *  已測試相容的 WordPress 版本 **4.9.29**
 *  語言
 * [English (US)](https://wordpress.org/plugins/ugrm/)
 * 標籤
 * [login](https://tw.wordpress.org/plugins/tags/login/)[SAML](https://tw.wordpress.org/plugins/tags/saml/)
   [shibboleth](https://tw.wordpress.org/plugins/tags/shibboleth/)[UF](https://tw.wordpress.org/plugins/tags/uf/)
 *  [進階檢視](https://tw.wordpress.org/plugins/ugrm/advanced/)

## 評分

這個項目尚無任何評論記錄。

[Your review](https://wordpress.org/support/plugin/ugrm/reviews/#new-post)

[查看全部使用者評論](https://wordpress.org/support/plugin/ugrm/reviews/)

## 參與者

 *   [ warren.brown ](https://profiles.wordpress.org/warrenbrown-1/)
 *   [ taylorwilson ](https://profiles.wordpress.org/taylorwilson/)

## 技術支援

使用者可在技術支援論壇提出意見反應或使用問題。

 [檢視技術支援論壇](https://wordpress.org/support/plugin/ugrm/)

## 贊助

想要支援這個外掛的發展嗎？

 [ 贊助這個外掛 ](http://www.flmnh.ufl.edu/)