Session Logout link

[Farzan Qureshi]

Hi Scott,

Sorry for the confusions.
He told me in other thread that to apply Federated settings, I first have
to make Authentication "Managed" and then apply Federation settings again.
This worked.

Secondly, about the link FederationMetaDataUrl. I understand that it has
nothing to do (for this scenario at least) after the discussion had with
Rob. May be my understanding was wrong. I thought that SP needs a metadata
to process the flow and vice versa. But here, only our IdP needs metadata
file.

You are right that restarting the computer has to do nothing because
Office365 is a separate entity and uncontrolled. I removed the ADFS role
because after applying federation changes, it was overwriting the settings
I was supplying. That is why I mentioned that I restarted the system. I was
just trying to scope down the issue :-)

Sorry again for all the confusion.

On 20 August 2014 14:48, Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 8/19/14, 10:14 PM, "Farzan Qureshi" <fqureshi at rosmini.school.nz> wrote:
> >
> >Ok first thing first. I was working with ADFS to federate our domain with
> >office365. However there were several issues related to it. We planned to
> >move from it to Shibboleth. We have completely remove ADFS role from the
> >system. We have also uninstalled Microsoft
> > ADFS update  - installed under Programs and features (in control panel).
> >So now ADFS is completely gone!
>
> What does that have to do with Office 365? How would it know anything
> about what you did or didn't do on your own server? If it's been told to
> use ADFS and the only way to fix that is by doing what he has told you to
> do, then I guess that's what you have to do.
>
> >Now the issue about metadata file. I have following in our
> >relying-party.xml
> >That is the reason I am talking about SAML i.e. FederationMetaDataUrl.
>
> What does Shibboleth's own configuration have to do with a setting inside
> Office 365? The answer is nothing.
>
> >My understanding is that having FederationMetadataUrl defines which
> >metadata to read and then follow the links mentioned in it, isn't it?
>
> Apparently that isn't how Office 365 works. If it doesn't support metadata
> for SAML, then that's the reality. It sounds to me like the very fact that
> it's asking for a URL for metadata is apparently a sign that your service
> is not set up to use SAML, but WS-Federation.
>
> >I have made federation changes couple of times from Managed to federated
> >as you have suggested but that FederationMetadataUrl comes back each time
> >I federate and supply federation commands in one go. It comes
> >automatically.
>
> He told you that "federated" in their speak does not mean SAML. So you're
> essentially repeating the same error over and over again. He didn't tell
> you, ever, to change from managed to federated. Seemed like he said the
> opposite to me.
>
> >I have also restarted the system to start again after removing ADFS role
> >and dependencies (updates).
>
> How does restarting your system impact theirs? It can't.
>
> -- Scott
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>



-- 
*Farzan Qureshi* | Network Administrator & Help-desk Support | Rosmini
College | (09) 487 0 530

-- 
This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If you have received this email in error please notify the system manager (
admin at rosmini.school.nz). Please note that any views or opinions presented 
in this email are solely those of the author and do not necessarily 
represent those of the company. Finally, the recipient should check this 
email and any attachments for the presence of viruses. Rosmini College 
accepts no liability for any damage caused by any virus transmitted by this 
email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20140820/643720ae/attachment-0001.html