Shibboleth with Office 365

[Ryan Larscheidt]

Yeah, I phrased that badly.  Our ECP endpoint is using the normal HTTPS certificate because it's exposed on port 443.  What I meant was that we used our SAML2 self-signed certificate when configuring the trust with Office 365 (http://technet.microsoft.com/en-us/library/jj205457.aspx) and it's working with SAML2 ECP.

Now that I read the Kent University blog post again, it's not clear if they're saying they couldn't use a self-signed certificate when running the Set-MsolDomainAuthentication command, or if they were using their self-signed SAML2 certificate on the ECP endpoint (perhaps because it was exposed on port 8443).  I'm going to guess the latter.

Apologies for any confusion.

Thanks,
Ryan

On May 21, 2013, at 16:28 , Peter Schober <peter.schober at univie.ac.at> wrote:

> * Ryan Larscheidt <larscheidt at doit.wisc.edu> [2013-05-21 23:24]:
>> This doesn't appear to be true, because we're using our IdP's
>> self-signed cert on the ECP endpoint with Office 365 (we're not in
>> production yet).
> 
> Why would you want to do that? ECP is for subject's http user agents,
> it's not a "back channel" thing?
> -peter
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 7327 bytes
Desc: not available
Url : http://shibboleth.net/pipermail/users/attachments/20130521/cb2d9c47/attachment.bin