From: "Justin Abrahms" <justin@abrah.ms>
To: "Thomas Fitzsimmons" <fitzsim@fitzsim.org>
Cc: 50113@debbugs.gnu.org
Subject: bug#50113: Excorporate: Communicating with domain that requires SSO?
Date: Mon, 23 Aug 2021 17:30:53 -0700 [thread overview]
Message-ID: <961bde13-0446-48f5-b3d9-d6098c767353@www.fastmail.com> (raw)
In-Reply-To: <m3tujf6f3e.fsf@fitzsim.org>
[-- Attachment #1: Type: text/plain, Size: 1857 bytes --]
I'm not able to get to the 'you created a service' page.
If I go to:
https://outlook.office365.com/EWS/Exchange.asmx
I'm prompted for a username + password. These are not my actual username + password, as those don't work. I believe if I was able to set up an application-specific password.. I'd be able to use that as the password. Unfortunately, those are disallowed per my administrator. When I abandon the attempted sign-in, I get the butter-y yellow page that I'd expect for an EWS site.
-justin
On Mon, Aug 23, 2021, at 2:11 PM, Thomas Fitzsimmons wrote:
> Hi Justin,
>
> "Justin Abrahms" <justin@abrah.ms> writes:
>
> > I'm trying to setup excorporate for my new job. In looking at the
> > outlook client that came pre-installed on my PC, I see that our EWS
> > url uses outlook365. This is the error I see in my *Messages* buffer:
> >
> > Contacting host: outlook.office365.com:443
> > error in process filter: exco--parse-xml-in-current-buffer: Server response is not an XML document
> > error in process filter: Server response is not an XML document
> >
> > When looking at *URL-DEBUG*, I see that it's being redirected to my
> > company's SSO endpoint. In looking around the docs & internet, I'm not
> > seeing how others deal with needing to do SSO, so I'm reaching out
> > here in hopes someone has ideas.
>
> Thanks for filing this issue.
>
> I haven't had to figure out single-sign-on authentication for
> Excorporate yet, but it's good to have a bug report about it so that we
> can work on solutions, assuming they exist.
>
> The first thing you can try is to access the EWS URL in Firefox. Does
> browsing to it result in you being transferred to the single-sign-on
> page? And if you authenticate, do you then see a page that says
> something like:
>
> "Service
>
> You have created a service.
>
> [...]"?
>
> Thomas
>
[-- Attachment #2: Type: text/html, Size: 2746 bytes --]
next prev parent reply other threads:[~2021-08-24 0:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 18:55 bug#50113: Excorporate: Communicating with domain that requires SSO? Justin Abrahms
2021-08-23 21:11 ` Thomas Fitzsimmons
2021-08-24 0:30 ` Justin Abrahms [this message]
2021-08-24 14:07 ` Thomas Fitzsimmons
2022-08-22 13:30 ` Lars Ingebrigtsen
2022-08-22 15:27 ` Thomas Fitzsimmons
2022-08-22 15:32 ` Lars Ingebrigtsen
2023-05-11 21:15 ` Thomas Fitzsimmons
[not found] ` <87a60gps0m.fsf@mailfence.com>
2023-03-13 16:30 ` Thomas Fitzsimmons
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: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=961bde13-0446-48f5-b3d9-d6098c767353@www.fastmail.com \
--to=justin@abrah.ms \
--cc=50113@debbugs.gnu.org \
--cc=fitzsim@fitzsim.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://git.savannah.gnu.org/cgit/emacs.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).