git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Ralph Ewig <ralph.phd@protonmail.com>
To: git@vger.kernel.org
Subject: git smart http + apache mod_auth_openidc
Date: Tue, 15 Oct 2019 15:59:03 +0000	[thread overview]
Message-ID: <4eb22ffc-77a1-4cd7-2277-bdc57d31186b@protonmail.com> (raw)

Hi Everyone, hoping you might have a solution for 
this problem:

CONTEXT

  * I'm serving git repos using "smart https" via 
apache and basic authentication; everything works 
fine.
  * We're moving to SSO via Azure AD and apache 
mod_auth_openidc; this works fine for gitweb (on 
the same server as git).

PROBLEM

When trying to clone a repo with the OIDC setup, 
git breaks on the redirect for user authentication 
with the following error message (replaced server 
ids etc with xxx):

     C:\Users\void>git clone --progress -v 
"https://git.xxx.xxx/WebApps.git"
     Cloning into 'WebApps'...
     fatal: unable to update url base from 
redirection:
       asked for: 
https://git.xxx.xxx/WebApps.git/info/refs?service=git-upload-pack
        redirect: 
https://login.microsoftonline.com/xxx/oauth2/authorize?response_type=code&scope=openid&client_id=xxx&state=xxx&redirect_uri=https%3A%2F%2Fgit.xxx.xxx%2Fredirect&nonce=xxx


Can the git client just not handle a web based 
redirect for login, or is this a configuration 
issue? Any ideas would be greatly appreciated. Thanks!

Ralph



             reply	other threads:[~2019-10-15 15:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-15 15:59 Ralph Ewig [this message]
2019-10-16 23:33 ` git smart http + apache mod_auth_openidc brian m. carlson
2019-10-17  3:00   ` Ralph Ewig
2019-10-17  6:03     ` Jeff King
2019-10-17 14:21       ` Ralph Ewig
2019-10-17 14:33       ` Ralph Ewig
2019-10-17 22:55         ` brian m. carlson
2019-10-18  1:18           ` Ralph Ewig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4eb22ffc-77a1-4cd7-2277-bdc57d31186b@protonmail.com \
    --to=ralph.phd@protonmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).