You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/12/11 19:33:01 UTC

[jira] [Commented] (VCL-1105) Shibboleth authentication broken due to bug in getCryptKeyID

    [ https://issues.apache.org/jira/browse/VCL-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16717852#comment-16717852 ] 

ASF subversion and git services commented on VCL-1105:
------------------------------------------------------

Commit c92ffda6ca794892e65e8afdf06f8d9039c81e52 in vcl's branch refs/heads/develop from [~jfthomps]
[ https://git-wip-us.apache.org/repos/asf?p=vcl.git;h=c92ffda ]

VCL-1105 - Shibboleth authentication broken due to bug in getCryptKeyID

utils.php: modified getCryptKeyID: added preg_replace to remove /shibauth from $filebase


> Shibboleth authentication broken due to bug in getCryptKeyID
> ------------------------------------------------------------
>
>                 Key: VCL-1105
>                 URL: https://issues.apache.org/jira/browse/VCL-1105
>             Project: VCL
>          Issue Type: Bug
>          Components: web gui (frontend)
>            Reporter: Josh Thompson
>            Priority: Critical
>             Fix For: 2.5.1
>
>
> Shibboleth authentication results in a failed query due to the way the cryptkeyid file is located in getCryptKeyID in utils.php.  The function ends up getting called from vcl/shibauth/index.php.  This results in the function looking for vcl/shibauth/.ht-inc/cryptkey/cryptkeyid instead of vcl/.ht-inc/cryptkey/cryptkeyid.  An additional preg_replace should be added to strip out /shibauth if it exists in $_SERVER['SCRIPT_FILENAME'].
> function getCryptKeyID() {
>     $reg = "|" . SCRIPT . "$|";
>     $filebase = preg_replace($reg, '', $_SERVER['SCRIPT_FILENAME']);
>     $filebase = preg_replace('|/shibauth|', '', $filebase);
>     $filebase .= "/.ht-inc/cryptkey";
>     $idfile = "$filebase/cryptkeyid";



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)